List revisions

/api/v2/admin/tenants/{tenant_uuid}/configuration-revisions

AUTHENTICATIONBearer token · admin:tenants:readAUTHORITATIVE OWNERtenant-configuration-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

List draft, reviewed, published, superseded, and reverted configuration revisions.

WHEN THIS CALL IS USEFUL

Use to audit immutable configuration history, select a draft for publication, or select historical state for a new reversion draft.

OUTCOME · Discover

What changes

Read-only revision collection. It does not validate, review, publish, or revert anything.

WHY IT MATTERS

Gives people and agents a contract-backed way to discover revisions.
Separates draft configuration work from effective tenant behavior so changes can be reviewed, audited, published atomically, and reverted through a new draft.

ISOLATION + AUTHORITY

Platform administrator, tenant, domain, certificate, brand, navigation, feature declaration, entitlement source, configuration revision, review, publication, and application-domain authority remain distinct. A tenant configuration or entitlement cannot enable frozen trading controls, matching, prediction execution, ingress, publisher activity, market status, traffic, wallet signing, or settlement authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Supply the required tenant_uuid (path) exactly as defined by the live contract.
Resolve the tenant UUID, current published configuration version, complete desired configuration, administrator authority, and any domain-owned policy that cannot be granted by tenant settings.

WHAT TO DO NEXT

Use the returned tenant and revision identifiers to inspect the exact effective or candidate configuration relevant to the task.
Refresh tenant detail after any publication or reversion and resolve domain-owned authorization separately from displayed entitlements.

AGENT GUIDANCE

Use revisions only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required tenant_uuid (path) exactly as defined by the live contract.
Distinguish tenant creation, draft revision, validation, review, publication, supersession, reversion draft, domain verification, certificate readiness, entitlement visibility, and domain-owned authorization.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

MACHINE CONTRACT

The exact deployed parameters, schemas, responses, security requirements, and Hybrid-Chain agent metadata are authoritative at this operation's production OpenAPI JSON Pointer. The readable tables below add integration guidance; the deployed OpenAPI controls if guidance and the machine contract ever differ.

Open the authoritative production contract ↗

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing admin:tenants:read authority.EXAMPLEBearer hc_live_…

tenant_uuidpathRequired

identifierStable tenant uuid selecting the exact resource addressed by this route.EXAMPLEtenant-uuid-01

X-Request-IDheaderOptional

stringOptional caller correlation identifier. The gateway emits the effective value on the response.

RESPONSES

Status and payload examples

200All immutable tenant configuration revisions with UUID, numeric version, base version, lifecycle, complete configuration, lineage, actor, and timestamps.Read completed · JSON RESPONSE+

{
  "configuration_version": 0,
  "revisions": [
    {
      "base_configuration_version": 0,
      "change_summary": "example-change-summary",
      "configuration": {
        "brand": "example-brand",
        "domains": [
          "example-domain"
        ],
        "entitlements": [
          "example-entitlement"
        ],
        "identity": "example-tenantidentityconfiguration",
        "settings": "example-settings"
      },
      "configuration_hash": "example-configuration-hash",
      "created": "example-created",
      "previous_configuration_hash": "example-previous-configuration-hash",
      "published_at": "2026-09-02T18:30:00Z",
      "published_by": "example-published-by",
      "reverted_from_revision": 1,
      "revision": 0,
      "revision_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
      "saved_by": "example-saved-by",
      "status": "example-status"
    }
  ],
  "tenant_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB"
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then use the returned tenant and revision identifiers to inspect the exact effective or candidate configuration relevant to the task.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.

401The administrator bearer is missing or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}