API reference / Admin

post/v1/admin/notifications/{id}/requeue

Put one message back in the worker’s path

Operation
adminRequeueNotification
Authentication
API key

Resets the row to `failed` with no attempts, so the next sweep picks it up and re-sends through exactly the same code as the first attempt — including the consent re-read. A message abandoned because the recipient replied STOP stays abandoned.

Request

Parameters

idpathrequiredstring

Responses

200Queued.
idstringrequired
statusstringrequired
400The request body or query failed validation.
errorobjectrequired
401No key, an unknown key, a revoked key, or a key whose tenant is not active. All four return an identical body on purpose: distinguishing them would let a caller discover which partners we have.
errorobjectrequired
403`projects:write` is required. No partner key is ever issued this scope.
errorobjectrequired
404Not found, or not yours. A resource belonging to another tenant answers 404 rather than 403, because 403 would confirm the record exists.
errorobjectrequired

Example

curl
curl -X POST https://api.haavisa.com/v1/admin/notifications/<id>/requeue \
  -H "Authorization: Bearer $HAAVISA_API_KEY"

More in Admin

Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.