By route
Submissions and redemptions answer an identical repeat with a
2xx, the existing resource, and replayed: true, except a redemption restart. A first acceptance carries replayed: false, on 202 for a submission and 201 for a redemption.
Batch order intake is the exception. An order is accepted once, and intake never returns an existing order as a success, so a 201 always means a new order and a new capacity reservation. A repeat answers 409 with code DUPLICATE_ORDER, and details.orderId lets you read the accepted order.
After a timeout or a 503
- Signed transactions or a signed payload are resubmitted unchanged. Sending the same request to
POST /v1/submissionsagain returns the same submissions, withreplayed: truefor each one the first request stored, including when the first broadcast reached the network and the transaction already landed. Signing a new transaction instead creates a different submission, and both could land. A503with codeNETWORK_NOT_ACTIVEis not retried: the API does not serve the network, and nothing was read or broadcast. - A redemption is resubmitted with the same signed fields. A different signature for the same nonce is a new payload: before settlement starts it replaces the earlier redemption, which fails with
SUPERSEDED, and after settlement starts it is rejected withNONCE_IN_USE. - A batch order is resubmitted with the same
orderand signature.DUPLICATE_ORDERmeans the first attempt was accepted. - Any other request that changes state, after a
408, is retried only after you read the current state, because the first attempt may have taken effect.
Restarting a failed redemption
Posting the same signed redemption again after it failed restarts it when itsfailure.resubmittable is true, and returns 200 with replayed: false. Fix the cause first, such as approving more $TSY; no new signature is needed. Lifecycle describes when a failure is resubmittable.
Related
Rate limits
How long to wait before a retry.
Errors
Which codes you can retry.