Skip to main content
Use this procedure when intent creation returns approval_mechanism: "broadcast".

Fund the intent

  1. Read approval_mechanism from the intent response.
  2. Sign and broadcast the transaction in deposit_tx_data. For RGB, pay deposit_tx_data.RgbLock.witness_invoice with an RGB wallet instead.
  3. Save the transaction hash.
For Solana transactions, preserve the existing signatures and message. Changing the blockhash invalidates existing signatures. For RGB wallet details, see Fund an RGB intent. For EVM and Tron, deposit_tx_data.EvmLike.transaction contains contract calldata, not a complete transaction. Submit that calldata to the source network’s configured Utexo router. The response does not include the router address, gas settings, or transaction value. Those settings come from your network configuration. resolver_deposit_address is not the router address.

Report the transaction

For a standard swap, submit the hash with your affiliate API key:
A successful response returns HTTP 200 with a Unix timestamp in seconds:
For an optimized single-chain swap, report the hash to POST /affiliate/v1/intents/{intent_id}/add-swap instead. The body has the same tx_hash field. Success returns HTTP 200 with an empty body.

Track the result

Poll the intent status until the swap completes or enters a refund path. For an RGB deposit, the API returns HTTP 200 with the fulfillment deadline once it accepts the transaction hash. The consignment is then verified in the background; follow the result through the intent status. If the API returns HTTP 500, wait briefly and submit the same transaction hash again.