Requeue a failed notification
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Body
Takes no parameters, and an empty body is expected. The row goes back to pending with attempts reset and is due immediately; the response is that row. USE A FRESH Idempotency-Key ON EVERY CALL. A replayed key returns the stored response without re-running anything, so a second retry on the same key answers with the first result and queues nothing. 409 not_retryable on a row that is not failed: a pending one is already on its way, and a sent one would deliver the same message to the shopper twice.
Response
Success
