Skip to main content
GET
List a monitor's firings

Notes

  • To authenticate, you’ll need a Tako API key. It’s best practice to store it as an environment variable to avoid hardcoding sensitive credentials in your code.
  • Returns firings newest first. limit is 1–100 and defaults to 20. To get the next page, pass a response’s next_cursor back as cursor.
  • occurred_at is when the occurrence happened, and fired_at is when Tako fired for it. The gap between them is however long the source took to report the occurrence. For each type’s reporting delay, see its description in List monitor types.
  • occurrence_key is what Tako deduplicates on. Tako records one firing per key, so a source that reposts the same occurrence doesn’t fire twice.
  • payload holds the values that caused the firing. Tako sends the same object to your channels under payload, and its fields depend on the monitor type. For the fields each type sends, see Webhook deliveries.
  • deliveries records what happened on each channel. After 2 consecutive failed deliveries, Tako pauses the channel. See Pause or resume a notification channel.
  • A delivery’s state is channel_paused when the channel was paused, so Tako didn’t send a request. failed means the delivery ended without a 2xx, including a delivery that expired before Tako sent it. Read attempts and last_status_code to tell them apart.
  • deliveries covers the last 30 days. An older firing lists none.
  • Tako removes firings older than the monitor type’s lookback_seconds.

Authorizations

X-API-Key
string
header
required

Path Parameters

id
string<uuid>
required

Resource id

Query Parameters

cursor
string

Opaque pagination cursor from a previous response's next_cursor.

limit
integer

Max items to return (default 20, max 100).

Required range: 1 <= x <= 100

Response

The monitor's firings, newest first

items
FiringResponse · object[]
required
next_cursor
string | null