Retry Outbox Failures
POST/api/ledger/outbox/failures/retry
Re-queue terminally-failed outbox rows for another drain pass: reset them to pending, clear the attempt counter (a fresh max-attempts budget — otherwise the next failure would immediately re-terminate them), make them claimable now, and kick the drain.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Authentication: Requires Bearer token. Requires the accounting.sync permission.
Body: { "ids": [9182, 9183] } retries the given failed rows; omit ids or pass [] to retry EVERY terminally-failed row.
Response: data.requeued — the number of rows re-queued (0 if there were no failures to retry).
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.