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.
  • Newest first. limit is 1–100 and defaults to 20; pass a response’s next_cursor back as cursor for the next page.
  • occurred_at is when the occurrence happened. fired_at is when Tako fired for it. They differ by however long the source took to report — see the type’s description in List monitor types.
  • occurrence_key is what Tako dedupes on: one firing per key, so a source that reposts the same occurrence doesn’t fire twice.
  • payload is the body Tako delivered to your channels. Its field set is the type’s contract — a key added there reaches subscribers, and one removed breaks them.
  • deliveries records what happened on each channel. Two consecutive failures pause the channel; see Pause or resume a notification channel.
  • Firings older than the monitor type’s lookback_seconds may have been removed, so this isn’t an indefinite archive.

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