672b1916ba61
Prepare metadata-URI follow-up transaction
Follow-up step for the non-custodial deploy flow. When prepareDeploy returns metadataUriFollowUp.required (the inline URI overflowed the create transaction), the client calls this after deploy/confirm to fetch an unsigned transaction that sets the metadata URI on-chain. Returns a null transaction when the on-chain URI already matches.
Path parameters
Token identifier.
Token identifier.
Headers
Selects the active project for this request. Required for session/dashboard callers. Ignored when authenticating with an API key, whose scope is fixed to the key's project.
Selects the active project for this request. Required for session/dashboard callers. Ignored when authenticating with an API key, whose scope is fixed to the key's project.
Response
Prepared metadata-URI follow-up transaction (or no-op)
Example response
{
"data": {
"transaction": {
"serialized": "AQID",
"blockhash": "blockhash_example",
"lastValidBlockHeight": "123456"
},
"uri": "https://api.example.com/v1/issuance/tokens/tok_123/metadata.json",
"simulation": {
"success": true,
"logs": [
"Program log: success"
],
"error": "Insufficient funds"
}
},
"meta": {
"requestId": "req_example",
"timestamp": "2025-01-01T00:00:00.000Z"
}
}