GET

Digital assets

List asset proofs

/api/v2/assets/{asset_uuid}/proofs

AUTHENTICATIONNone · publicService ownerasset-registry-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Return the retained public proof chain for one published asset.

When to use it

Use when an integration must verify retained public commitments for one published asset rather than trusting display metadata or lifecycle labels.

OUTCOME · Verify

What changes

Read-only public evidence. A proof signature is not a bearer, signing credential, mint key, custody key, or permission to perform the evidenced action.

WHY IT MATTERS

Gives people and agents a contract-backed way to verify asset proofs.
Lets clients verify asset identity and provenance without treating display metadata or portfolio visibility as issuance or trading authority.

ISOLATION + AUTHORITY

Issuer, collection, asset, mint, proof, owner, network, supply, metadata, custody, marketplace, and trading boundaries remain distinct. Reading an asset or proof cannot issue, mint, transfer, list, value, or trade it; current trading and matching controls remain frozen unless separately approved.

BEFORE YOU CALL

No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
Supply the required asset_uuid (path) exactly as defined by the live contract.
Resolve the canonical asset or collection identifier, issuer, network, lifecycle, supply, and required proof freshness.

WHAT TO DO NEXT

Compare the returned commitment, signer, policy, lifecycle, and freshness fields with the caller's acceptance rules.
Verify issuer, network, collection, supply, mint, proof, and lifecycle commitments together before presenting or acting on the asset.

AGENT GUIDANCE

Use asset proofs only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required asset_uuid (path) exactly as defined by the live contract.
Distinguish declared metadata, issuer identity, collection membership, mint evidence, supply state, ownership or custody, market listing, price, transfer, and finality.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

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

asset_uuidpathRequired

identifierCanonical 32-character lowercase hexadecimal asset identifierEXAMPLEasset-uuid-01

X-Request-IDheaderOptional

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

RESPONSES

Status and payload examples

200Canonical resource projection.Read completed · JSON RESPONSE+

{
  "asset_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "proofs": [
    {
      "collection_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
      "created_at": "2026-09-02T18:30:00Z",
      "event_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
      "issued_at": "2026-09-02T18:30:00Z",
      "ledger": "example-ledger",
      "network": "example-network",
      "payload_hash": "example-payload-hash",
      "previous_proof_hash": "example-previous-proof-hash",
      "proof_type": "example-proof-type",
      "proof_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
      "signature": "example-signature",
      "signature_algorithm": "example-signature-algorithm",
      "signature_key_id": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
      "status": "example-status",
      "subject_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB"
    }
  ]
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then compare the returned commitment, signer, policy, lifecycle, and freshness fields with the caller's acceptance rules.
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 market status, owner-scoped order or position state, Core collateral reservation, and settlement receipt; never treat shadow NXG evidence as authority.

404No published asset exists for the identifierResource 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 market status, owner-scoped order or position state, Core collateral reservation, and settlement receipt; never treat shadow NXG evidence as authority.
ESCALATE WHEN: Escalate any ambiguous order or settlement outcome while preserving suspension and Python authority; never enable ingress, publishing, allowlists, markets, or traffic as recovery.

422Path, query, or body validation failed.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 market status, owner-scoped order or position state, Core collateral reservation, and settlement receipt; never treat shadow NXG evidence as authority.
ESCALATE WHEN: Escalate any ambiguous order or settlement outcome while preserving suspension and Python authority; never enable ingress, publishing, allowlists, markets, or traffic as recovery.

502Core returned invalid proof evidenceDependency 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 market status, owner-scoped order or position state, Core collateral reservation, and settlement receipt; never treat shadow NXG evidence as authority.
ESCALATE WHEN: Escalate any ambiguous order or settlement outcome while preserving suspension and Python authority; never enable ingress, publishing, allowlists, markets, or traffic as recovery.

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 market status, owner-scoped order or position state, Core collateral reservation, and settlement receipt; never treat shadow NXG evidence as authority.
ESCALATE WHEN: Escalate any ambiguous order or settlement outcome while preserving suspension and Python authority; never enable ingress, publishing, allowlists, markets, or traffic as recovery.

OPERATIONAL NOTES

Security and lifecycle guarantees

Returns the signed, commitment-linked proof chain retained for one published asset. Verify payload hashes, previous-proof links, key identifiers, algorithms, and status rather than trusting a display field or screenshot.
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.

Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory