On-chain Operations
Replace a Transaction
Replace a submitted transaction on a supported chain, if it doesn’t already have an active replacement.
Request example
Response example
POST
/api/external/transactions/replace_transaction/
Replacement is accepted only for a SUBMITTED transaction on a chain that supports replacement and when no active replacement already exists.
Request body
string
required
The ID of the transaction to replace.
Response
Returns the replacement Transaction. Itsstatus is the lifecycle source of truth.
string
Transaction ID. Use it with Retrieve Transaction to track status.
string
Organization that owns the transaction.
string
Vault the transaction runs from.
string
Lifecycle status. Track it until
COMPLETED, FAILED, or DECLINED. See TransactionStatus.string
See TransactionType.
string
For example
TRANSFER or CONTRACT_CALL. See TransactionCategory.string
string
Creation timestamp (ISO 8601).
string
Last update timestamp (ISO 8601).
boolean
Whether the transaction is deleted.
string
Your own reference, if you set one.
string
Memo you attached, if any.
TransferPartyData
Where the funds come from. Which fields are present depends on
type. See TransferPartyData.TransferPartyData
Where the funds go. Same fields as
source. See TransferPartyData.string
Chain the transaction runs on.
string
Asset moved.
string
Amount as a decimal string.
number
Chain nonce of the transaction.
Approve the transaction
New transactions returnstatus: "PENDING" and wait for approval. Get the approval message for the transaction id, sign it with your API user’s key, then submit the approval. See Approvals.
With the SDK, call approveChangeRequest({ entityId: transaction.id, action: "approve" }) after this call.
Request example
Response example