POST

MPC wallet lifecycle

Submit customer asset document proposal

/api/v2/wallets/asset-document-proposals

AUTHENTICATIONBearer token · wallets:assets:submitService ownercustody-serviceContract sourceOpenAPISTATUSAwaiting deployment · not callable

Purpose and usage

What this endpoint does

Any authenticated Wallets user may submit a private unapproved token document under narrow proposal authority and current tenant/workspace policy. Retains the original import UUIDs; never grants approval, decoder, wallet-management or signing authority.

When to use it

Call this when a wallet, treasury, custody, or governed agent workflow needs to apply the documented submit customer asset document proposal transition after re-reading the current authoritative state so it can make a custody decision inside the correct owner, workspace, network, and policy boundary.

OUTCOME · Create or advance

What changes

Creates or advances only the submit customer asset document proposal resource described by this contract after authorization, validation, policy, and idempotency gates pass.

WHY IT MATTERS

Gives people and agents a contract-backed way to advance submit customer asset document proposal.
Makes custody state understandable without exposing seeds, shares, nonces, private keys, or other reusable signing material.

ISOLATION + AUTHORITY

The authenticated owner, workspace, network, and wallet policy remain authoritative. A wallet record, policy result, approval, ceremony, or balance never grants another lifecycle stage and cannot substitute for threshold signing or separately owned funding, settlement, publisher, matching, or trading authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Supply the required chain_uuid (body), asset_uuid (body), inspection_uuid (body), import_idempotency_key (body), document_format (body), document (body) exactly as defined by the live contract.
Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.
Resolve the active workspace, network, wallet lifecycle, and applicable custody policy before relying on this result.

WHAT TO DO NEXT

Re-read submit customer asset document proposal using the canonical identifier returned by this operation.
Reconcile an ambiguous response with the same idempotency key before attempting another mutation.
Re-read the wallet and policy state before the next governed action, especially after an ambiguous or concurrent result.

AGENT GUIDANCE

Use submit customer asset document proposal only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required chain_uuid (body), asset_uuid (body), inspection_uuid (body), import_idempotency_key (body), document_format (body), document (body) exactly as defined by the live contract.
Keep enrollment, activation, policy evaluation, approval, ceremony, signing, submission, confirmation, and settlement as distinct states.
After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.

Contract reference

This source-implemented operation is not listed in the recorded production contract. Use this page to prepare, not execute, your integration.

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 wallets:assets:submit authority.EXAMPLEBearer hc_live_…

Idempotency-KeyheaderRequired

ASCII string · 8–128 · letters, digits or ._:-Caller-generated stable key reused for retries of the same logical mutation.EXAMPLEpost-api-v2-wallets-asset-document-proposals-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.

asset_uuidbodyRequired

canonical lowercase UUIDv4Exact asset deployment on that chain. It is validated as part of the request body before any operation is attempted.EXAMPLEaaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa

chain_uuidbodyRequired

canonical lowercase UUIDv4Exact registered chain identity; never a ticker.EXAMPLEaaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa

documentbodyRequired

bounded JSONMaximum 65536 serialized bytes, depth 24, 8192 nodes and 256 members per container. Duplicate keys and fractional numbers are rejected; Core validates the format-specific subset.EXAMPLE[object Object]

document_formatbodyRequired

AssetDocumentFormatInert proposal format, not decoder authorization.Allowed: DISPLAY_METADATA_V1 | SOLIDITY_ABI_JSON_V1EXAMPLEDISPLAY_METADATA_V1

import_idempotency_keybodyRequired

ASCII string · 8–128Original import key; letters, digits or ._:- only.EXAMPLEimport-idempotency-key-01

inspection_uuidbodyRequired

canonical lowercase UUIDv4Inspection retained by the same owner-scoped import.EXAMPLEaaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa

supersedes_uuidbodyOptional

canonical lowercase UUIDv4 | nullPrevious receipt in this exact owner/import scope; corrections never overwrite it.Explicit null acceptedEXAMPLEaaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa

REQUEST

JSON body example

{
  "asset_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "chain_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "document": "example-document",
  "document_format": "DISPLAY_METADATA_V1",
  "import_idempotency_key": "example-import-idempotency-key",
  "inspection_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
  "supersedes_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB"
}

RESPONSES

Status and payload examples

200Owner-scoped immutable receipt read or matching retry; no authority granted.Mutation completed · JSON RESPONSE+

"example-value"

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then re-read submit customer asset document proposal 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. Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.

201Private unapproved proposal; no decoder, publication or custody authorityMutation completed · JSON RESPONSE+

"example-value"

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then re-read submit customer asset document proposal 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. Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.

400Malformed UUID, JSON, bounds, query or retry key.Request must change · JSON RESPONSE+

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