HYBRID-CHAINDEVELOPERS
DOCUMENTATIONv2
POST

Tenant and brand management

Publish revision

/api/v2/admin/tenants/{tenant_uuid}/configuration-revisions/{revision_uuid}/publications
AUTHENTICATIONBearer token · admin:tenants:writeAUTHORITATIVE OWNERtenant-configuration-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

Atomically publish a current tenant configuration draft.

WHEN THIS CALL IS USEFUL

Use only after inspecting a current DRAFT and confirming that its complete configuration should become effective atomically.

OUTCOME · Create or advance

What changes

Publishes the selected DRAFT and atomically replaces effective identity, brand, domains, entitlements, and settings. It does not configure external DNS, TLS, ingress, infrastructure, traffic, or trading authority.

WHY IT MATTERS

  • Gives people and agents a contract-backed way to advance publish revision.
  • 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), revision_uuid (path), expected_configuration_version (body) exactly as defined by the live contract.
  • Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.
  • 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

  • Re-read tenant detail and confirm the published configuration head, domains, branding, navigation, and entitlements now match the approved revision.
  • Reconcile dependent domain services separately; publication cannot activate authority or frozen product controls outside tenant configuration.

AGENT GUIDANCE

  • Use publish revision 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), revision_uuid (path), expected_configuration_version (body) 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.
  • After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.
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:write authority.EXAMPLEBearer hc_live_…

tenant_uuidpathRequired

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

revision_uuidpathRequired

identifierCanonical revision uuid. It selects the exact revision uuid addressed by this route.EXAMPLErevision-uuid-01

Idempotency-KeyheaderRequired

ASCII string · 1–128Caller-generated stable key reused for retries of the same logical mutation.EXAMPLEpost-api-v2-admin-tenants-tenant-uuid-configuration-revisions-revision-uuid-publications-request-001

X-Request-IDheaderOptional

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

Content-DigestheaderRequired

stringRFC 9530 sha-256 digest of the exact transmitted request-body bytes.

Signature-InputheaderRequired

stringRFC 9421 sig1 input covering @method, @path, content-digest, content-type, and idempotency-key, with created, expires, nonce, keyid, and alg=ed25519.

SignatureheaderRequired

stringRFC 9421 sig1 Ed25519 signature made by an active key registered to the bearer client.

expected_configuration_versionbodyRequired

integer · ≥1Current published tenant configuration version. The selected DRAFT must branch from this exact version.Schema range: 0 to unboundedEXAMPLE3

REQUEST

JSON body example

{
  "expected_configuration_version": 0
}

RESPONSES

Status and payload examples

200Selected current DRAFT published atomically; identity, brand, domains, entitlements, and settings now reflect that exact revision.Mutation completed · JSON RESPONSE+
{
  "administrators": [
    "example-administrator"
  ],
  "assignment": "example-assignment",
  "assignment_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "change_summary": "example-change-summary",
  "changes": [
    "example-change"
  ],
  "configuration": "example-configuration",
  "configuration_hash": "example-configuration-hash",
  "configuration_version": 1,
  "event_type": "example-event-type",
  "replayed": true,
  "revision": 1,
  "revision_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "status": "example-status",
  "tenant_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB"
}
INTEGRATION DECISION
CALLER ACTION
Accept the returned representation or receipt, then re-read tenant detail and confirm the published configuration head, domains, branding, navigation, and entitlements now match the approved revision.
RETRY SAFETY
Do not repeat a successful mutation merely to confirm it. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION
Persist returned identifiers, versions, commitments, and receipts. Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.
400An identifier, expected version, signature, or Idempotency-Key is malformed.Request must change · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY
Do not retry the same invalid request. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION
Compare the submitted values with the documented constraints before another call. Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.
ESCALATE WHEN
Escalate when tenant identity, domain ownership, brand version, entitlement, or last-administrator safety cannot be proven.
401The administrator bearer is missing or invalid.Authentication required · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY
Retry only with a newly valid credential and fresh replay-protection values. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION
Assume the outcome is unknown only when the connection failed after transmission; otherwise authentication failed before domain work. Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.
ESCALATE WHEN
Escalate when tenant identity, domain ownership, brand version, entitlement, or last-administrator safety cannot be proven.
403The bearer lacks admin:tenants:write or the RFC 9421 signature is invalid.Authority or policy denied · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY
Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION
Confirm the caller and resource resolve to the same authority boundary for tenant identity, brand, domain, configuration, entitlement, administrator, and lifecycle projections.
ESCALATE WHEN
Escalate when tenant identity, domain ownership, brand version, entitlement, or last-administrator safety cannot be proven.
404The tenant or tenant-owned revision does not exist.Resource not visible · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Verify the canonical identifier and authenticated owner boundary. A 404 may intentionally conceal a resource outside the caller's authority.
RETRY SAFETY
Do not retry the unchanged identifier repeatedly. Refresh the relevant collection or lookup before choosing another identifier.
STATE RECONCILIATION
Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.
ESCALATE WHEN
Escalate when tenant identity, domain ownership, brand version, entitlement, or last-administrator safety cannot be proven.
409The expected version, draft base, lifecycle, uniqueness constraint, or Idempotency-Key conflicts.State reconciliation required · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Stop the mutation sequence and fetch the latest authoritative resource, lifecycle state, version, ETag, reservation, or existing idempotency result.
RETRY SAFETY
Retry only after reconciling the conflict. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION
Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.
ESCALATE WHEN
Escalate when tenant identity, domain ownership, brand version, entitlement, or last-administrator safety cannot be proven.
422Core tenant policy rejected publication.Request must change · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY
Do not retry the same invalid request. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION
Compare the submitted values with the documented constraints before another call. Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.
ESCALATE WHEN
Escalate when tenant identity, domain ownership, brand version, entitlement, or last-administrator safety cannot be proven.
503The authoritative tenant control plane is unavailable; the effective configuration is unchanged.Dependency unavailable or outcome uncertain · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Preserve the exact request and treat the outcome as uncertain until authoritative state proves whether it committed.
RETRY SAFETY
Reconcile before retrying. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions. Use bounded backoff with jitter.
STATE RECONCILIATION
Refresh the tenant and brand revisions, domain verification, entitlement and administrator state, and any dependent workspace or application bindings.
ESCALATE WHEN
Escalate when tenant identity, domain ownership, brand version, entitlement, or last-administrator safety cannot be proven.

OPERATIONAL NOTES

Security and lifecycle guarantees

  • Publishes one current DRAFT and atomically replaces the canonical identity projection, brand, full domain intent, and entitlement policies. Stale drafts fail with 409. Publication does not verify DNS/TLS, grant credentials, or authorize frozen trading and traffic domains.
  • The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
  • Mutations are retry-safe only when the same Idempotency-Key and canonical request body are reused.
  • The tables and examples are derived from the current gateway source OpenAPI. Re-fetch the deployed OpenAPI before execution; deployment status is shown separately on this page.
  • Only parameters present in the OpenAPI operation are accepted; undocumented query keys fail closed with HTTP 422.
DOCUMENTATION STATUS

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-09-11T06:35:11.572Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation ↗Return to the V2 directory ↗