GET /v1/status/:tracking_id
Purpose
Section titled “Purpose”Return delivery metadata for a previously queued notification.
Auth requirement
Section titled “Auth requirement”Bearer API key (Authorization: Bearer <key>).
Request schema
Section titled “Request schema”Path parameter:
tracking_id(UUID)
No request body.
Response schema
Section titled “Response schema”200 OK
{ "tracking_id": "uuid", "user_id": "string", "priority": 0, "status": "queued|delivering|delivered|retrying|blocked|failed|unlinked", "attempts": 0, "created_at": "ISO-8601", "updated_at": "ISO-8601", "telegram_message_id": "string|null", "last_error_code": 0, "last_error_message": "string|null"}Error cases
Section titled “Error cases”401 unauthorized: invalid/inactive API key.404 not_found: unknown tracking ID for your tenant.
Curl example
Section titled “Curl example”curl -H "Authorization: Bearer $ETN_API_KEY" \ "$GATEWAY_BASE_URL/v1/status/$TRACKING_ID"Notes and limits
Section titled “Notes and limits”- Response is metadata-only and does not include message body.
- Tenant-scoped lookup enforces isolation.