Traces and proof
Apian Labs Relay records a trace timeline for every message so you can prove how delivery decisions were made. This page explains the trace model and how to use proof artifacts during incident reviews.
Trace timeline
A trace is an ordered list of attempts, receipts, and policy decisions. Each entry includes provider metadata, timestamps, and normalized error categories.
{
"messageId": "msg_1234",
"attempts": [
{
"provider": "twilio",
"status": "failed",
"errorCategory": "timeout",
"timestamp": "2025-01-05T18:11:52Z"
},
{
"provider": "telnyx",
"status": "delivered",
"timestamp": "2025-01-05T18:12:14Z"
}
]
}
Proof artifacts
Apian Labs Relay stores receipts and provider responses so your team can audit outcomes later. These artifacts help explain failovers to customers, compliance teams, and internal stakeholders.
Using traces in operations
Traces are useful for incident retrospectives, provider comparisons, and debugging. They provide a single source of truth for the routing path a message took.