Skip to main content
GET
Get template message status

Autorizaciones

X-API-Key
string
header
requerido

Merchant API key for authentication

Parámetros de ruta

event_id
string
requerido

The event_id sent when the message was requested

Pattern: ^[A-Za-z0-9._-]{8,128}$

Respuesta

Successful Response

event_id
string
requerido

The event_id sent in the request

status
enum<string>
requerido

Current status of the send. A send that was taken answers accepted; poll the status endpoint for what became of it. sent, delivered, read and failed come from delivery receipts, and discarded means it was never sent

Opciones disponibles:
accepted,
in_progress,
sent,
delivered,
read,
failed,
discarded
updated_at
string<date-time>
requerido

When this send's record last changed (UTC) — not when you asked. Polling never moves it, but a delivery write that leaves status unchanged does, so it is not a watermark: reconcile on event_id

status_detail
string | null

Reason behind a failed or discarded status, or the delivery_not_observable note on an accepted one. Not a closed set, and may be absent. stale, paused, account_not_eligible, no_sender_number, send_failed, send_cancelled and delivery_not_observable are ours and stable — the last one means the send went to a store this deployment cannot read, so the status will not settle here; when the provider refused the delivery it carries provider_error_<code> with the provider's own numeric code (for example provider_error_131049), and that catalogue changes without notice. Branch on status, log this, and treat an unrecognised or missing value as a generic failure

Ejemplo:

"stale"