Skip to main content
GET
Message Status
Answers the question your customer actually asks: “why didn’t it arrive?” Make this your tier-1 support screen.

Endpoint

  • Method: GET
  • Path: /api/messages/{messageId}/journey
  • Auth: Authorization: Bearer tuco_xxxxxxxxxxxxx (workspace key)

Response

Not a status string — a timeline. Each step records when it happened, how serious it is, which system reported it, and copy you can show a human as-is.
meta describes where the timeline was assembled from (source, env) and how many steps it holds. Render copy directly. Branch on key. The timeline includes retries, the fallback ladder (iMessage → SMS → email) and the reason for any failure, so a message that fell back shows both legs rather than just the final state.

Error responses