Retry Delivery
POST/api/v1/transactions/:transaction_id/retry
Deliver a failed or retrying outbound transaction again โ the SAME transaction, the same stored document, the same message id.
This is the retry a person reaches for when the receiver's Access Point was
unreachable or the registry blinked. It never rebuilds anything, and it works for
a document sent as raw UBL. /resend instead rebuilds the document from the
stored invoice data: a rebuild that keeps the document identifier (the same
seller, type, number, issue date and tax totals โ an Oman invoice resent with its
date kept) queues the existing transaction again, as this route does; one with a
new issue date is sent as a new transaction.
Requirements:
- Transaction must be outbound (sent) and in 'failed' or 'retrying' status
- The document must still be in storage
Two calls for the same transaction at once queue it once: the other answers
409 ALREADY_QUEUED.
Requestโ
Responsesโ
- 200
- 422
Successful Response
Validation Error