HYBRID-CHAINDEVELOPERS
DOCUMENTATIONv2
POST

Tenant and brand management

Assign authority

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

PURPOSE + BUSINESS CONTEXT

Assign TENANT_ADMIN or TENANT_MODERATOR authority with retained actor attribution and rationale.

WHEN THIS CALL IS USEFUL

Use when a known profile should receive TENANT_ADMIN or TENANT_MODERATOR authority for one tenant.

OUTCOME · Create or advance

What changes

Creates a tenant-local authority assignment and retained audit event. It does not grant platform infrastructure, traffic, publisher, market, matching, or trading authority.

WHY IT MATTERS

  • Gives people and agents a contract-backed way to advance assign 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), profile_uuid (body), role_code (body), 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 assign 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 assign 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), profile_uuid (body), role_code (body), 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.
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

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-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.

profile_uuidbodyRequired

32-character lowercase hexadecimal identifierExisting administrator profile receiving tenant-local authority.EXAMPLE9d9dd75d5072462ba35e5529f1f4f09e

reasonbodyRequired

string · 8–320Retained attributed rationale for the assignment.EXAMPLEAssign content operations moderator.

role_codebodyRequired

TENANT_ADMIN | TENANT_MODERATORExact tenant-local administrative role. It grants no infrastructure, traffic, or trading authority.EXAMPLETENANT_MODERATOR

REQUEST

JSON body example

{
  "profile_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "reason": "example-reason",
  "role_code": "example-role-code"
}

RESPONSES

Status and payload examples

200Tenant-local TENANT_ADMIN or TENANT_MODERATOR assignment retained with trusted actor attribution and current administrator projection.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 assign 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, role, reason, signature, or Idempotency-Key are 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 proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN
Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.
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 proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN
Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.
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 workspace governance proposals, approvals, signing handoffs, policy versions, and execution evidence.
ESCALATE WHEN
Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.
404The tenant or target profile 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 proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN
Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.
409The assignment or Idempotency-Key conflicts with retained state.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 proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN
Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.
422Core authority or lockout policy rejected the assignment.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 proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN
Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.
503The authoritative tenant control plane is unavailable; no authority is assigned.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 proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN
Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

OPERATIONAL NOTES

Security and lifecycle guarantees

  • Assigns TENANT_ADMIN or TENANT_MODERATOR to one canonical profile and records the before/after state in the tenant hash chain. OWNER is protected and cannot be assigned through this operation. Actor identity comes only from the bearer.
  • 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 ↗