Skip to main content
GET
Alert delivery log API

Frequently asked questions

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.
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.
Deliveries older than 30 days are pruned daily, but the newest 20 per alert are always retained regardless of age.
Pass include_events=true. It is opt-in because an events payload can reach roughly 30KB per delivery.

Authorizations

Authorization
string
header
required

API key in format tapi_live_[32-char] (live) or tapi_test_[32-char] (test)

Path Parameters

id
string
required

The alert id.

Example:

"alrt_9f2c4a1e"

Query Parameters

limit
integer
default:20

Deliveries returned. Maximum 100.

Required range: x <= 100
offset
integer
default:0

Pagination offset.

include_events
boolean
default:false

Embed the delivered event rows in each record. Opt-in because the payload can reach roughly 30KB per delivery.

Response

Delivery records, newest first

success
boolean
Example:

true

data
object