DOCUMENTATIONv2

GET

Explorer · transfers

Get transfer compliance MPC authorization

/api/v2/explorer/transfers/mpc-authorizations/{authorization_uuid}

AUTHENTICATIONNone · publicAUTHORITATIVE OWNERtransfer-compliance-read-modelCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

Return transfer compliance mpc authorization from the public Explorer read model, with the identifiers and verification metadata defined by the live contract.

WHEN THIS CALL IS USEFUL

Call this when an explorer, wallet, indexer, auditor, or research agent needs to inspect one specific transfer compliance mpc authorization before presenting it or making a dependent decision so it can resolve public network state from a machine-readable projection.

OUTCOME · Inspect

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to inspect transfer compliance mpc authorization.
Keeps website presentation separate from the stable public contract that wallets, indexers, and agents can ingest.

ISOLATION + AUTHORITY

This is a public, read-only Explorer projection. It exposes only fields admitted by the live OpenAPI schema; it grants no owner, wallet, signing, settlement, publisher, matching, or trading authority. Indexed observation time is not the same as chain finality.

BEFORE YOU CALL

No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
Supply the required authorization_uuid (path) exactly as defined by the live contract.
Account for projection freshness, indexing position, and chain or domain finality in the consuming decision.

WHAT TO DO NEXT

Follow the returned canonical identifiers and proof or related-resource links when independent verification is required.
Refresh transfer compliance mpc authorization when its observation time, version, or lifecycle state is no longer adequate for the decision.

AGENT GUIDANCE

Use transfer compliance mpc authorization only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required authorization_uuid (path) exactly as defined by the live contract.
Treat observation timestamps, indexing position, proof state, and finality as separate facts; do not infer final settlement or authority from presence in an Explorer result.
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

authorization_uuidpathRequired

identifierCanonical authorization uuid. It selects the exact authorization uuid addressed by this route.EXAMPLEauthorization-uuid-01

X-Request-IDheaderOptional

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

RESPONSES

Status and payload examples

200Canonical public Explorer projection.Read completed · JSON RESPONSE+

{
  "meta": {
    "limit": 50
  },
  "response": [
    {
      "created": "2026-08-23T12:00:00Z",
      "status": "ACTIVE",
      "uuid": "8d4f3b7f5c8a4b918ec68fe4e6884231"
    }
  ],
  "success": true
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then follow the returned canonical identifiers and proof or related-resource links when independent verification is required.
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. Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.

404The public Explorer resource was not found.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: Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

422A path or query parameter is invalid or undocumented.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. A corrected read may be sent as a new attempt.
STATE RECONCILIATION: Compare the submitted values with the documented constraints before another call. Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

503The authoritative service or read model is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

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

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

OPERATIONAL NOTES

Security and lifecycle guarantees

EXPLORER: Transfer compliance mpc authorization through the canonical Hybrid-Chain V2 interface. This is a public, read-only projection; no trading or settlement mutation is performed.
The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
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 ↗