Alert delivery log API
Alerts
Alert delivery log API
The delivery history for one alert — what was sent, when, and whether your endpoint accepted it. Free.
GET
Alert delivery log API
Frequently asked questions
What does truncated mean on a delivery?
What does truncated mean on a delivery?
More events matched than the 100-per-delivery cap. Truncation is pagination: the remainder arrives on the next sweep, because the watermark stopped at the cut. On an
hourly alert that is an hour later; on a daily alert it is roughly 24 hours later, so a scope producing more than 100 events a day will only ever drain 100 a day. If you see persistent truncation, either switch to hourly or narrow the scope.Why would response_status be null?
Why would response_status be null?
The request never got a response — a timeout, a DNS failure or a connection refusal. The
error field carries the detail. Failures like these keep the watermark in place, so the same window is re-delivered on the next sweep.How long is history kept?
How long is history kept?
Deliveries older than 30 days are pruned daily, but the newest 20 per alert are always retained regardless of age.
How do I see the actual events that were sent?
How do I see the actual events that were sent?
Pass
include_events=true. It is opt-in because an events payload can reach roughly 30KB per delivery.Authorizations
API key in format tapi_live_[32-char] (live) or tapi_test_[32-char] (test)
Path Parameters
The alert id.
Example:
"alrt_9f2c4a1e"
Query Parameters
Deliveries returned. Maximum 100.
Required range:
x <= 100Pagination offset.
Embed the delivered event rows in each record. Opt-in because the payload can reach roughly 30KB per delivery.