Submit a prepared Avalanche transaction

Submits a signed Avalanche transaction returned by /avalanche/transactions/prepare. CDAO decodes the signed
transaction, verifies it matches the stored unsigned transaction and account context, reruns final freshness and
policy checks, and either dry-runs the submission or broadcasts it.

When dryRun is true, CDAO performs the same pre-submit checks but does not call any Avalanche issueTx method.
No network transaction is created and no real txHash should be returned. When dryRun is false, CDAO routes the
transaction to the correct chain API: C-Chain atomic export transactions go to the C-Chain atomic API, while
P-Chain stake, delegate, and import transactions go to the P-Chain API.

RPC acceptance only means the network accepted the transaction for processing. Use /avalanche/transactions/status
to track finality: C-Chain atomic export transactions become final when ACCEPTED; P-Chain transactions become
final when COMMITTED.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
uuid
required

The UUID of the account that owns the prepared Avalanche transaction.

string
required
^0x[0-9a-fA-F]+$

The canonical signed transaction bytes returned by /prepare, to be dry-run or broadcast.

boolean
required

true runs CDAO pre-submit checks without broadcasting (the intent stays READY_TO_SUBMIT and no txHash
is created). false runs the same checks and broadcasts the signed transaction to the correct Avalanche chain API.

Responses

401

Access token or App Id is missing or invalid

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json