POST

Tenant and brand management

Revoke authority

/api/v2/admin/tenants/{tenant_uuid}/authorities/{assignment_uuid}/revocations

AUTHENTICATIONBearer token · admin:tenants:writeService ownertenant-configuration-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Revoke an eligible tenant administrator assignment while protecting owner authority.

When to use it

Use when an active tenant-local assignment should be revoked and owner-lockout policy permits the change.

OUTCOME · Create or advance

What changes

Revokes the selected tenant-local assignment and retains actor attribution and rationale. Historical authority evidence remains immutable.

WHY IT MATTERS

Gives people and agents a contract-backed way to advance authority.
Keeps deliberation, approval evidence, authority assignment, and threshold-signing participation explicit and auditable.

ISOLATION + AUTHORITY

Tenant, workspace, proposal, voter, authority assignment, quorum, custody participant, and signing-session boundaries remain separate. A proposal, recorded decision, assigned role, or ceremony request does not by itself activate a contract, produce a threshold signature, move value, or grant publisher, matching, or trading authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Supply the required tenant_uuid (path), assignment_uuid (path), reason (body) exactly as defined by the live contract.
Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.
Resolve the current proposal or assignment version, eligible authority, quorum rule, and purpose-bound policy before relying on this result.

WHAT TO DO NEXT

Re-read authority using the canonical identifier returned by this operation.
Reconcile an ambiguous response with the same idempotency key before attempting another mutation.
Re-read the proposal, assignment, quorum, or ceremony state and verify its version and commitments before advancing the governed action.

AGENT GUIDANCE

Use authority 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), assignment_uuid (path), reason (body) exactly as defined by the live contract.
Keep proposal creation, review, decision recording, quorum satisfaction, authority assignment, ceremony request, participant signing, execution, and finality as separate lifecycle facts.
After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.

Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

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

assignment_uuidpathRequired

identifierCanonical assignment uuid. It selects the exact assignment uuid addressed by this route.EXAMPLEassignment-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-authorities-assignment-uuid-revocations-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.

reasonbodyRequired

string · 8–320Retained attributed rationale for revocation. Owner-lockout protection remains authoritative in Core.EXAMPLEOperator no longer administers this tenant.

REQUEST

JSON body example

{
  "reason": "example-reason"
}

RESPONSES

Status and payload examples

200Eligible tenant-local authority revoked with retained actor attribution; owner-lockout protections remain authoritative.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 authority using the canonical identifier returned by this operation.
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 proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.

400The identifiers, reason, signature, or Idempotency-Key are malformed.Request must change · JSON RESPONSE+

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