Skip to content
Scalekit Docs
Talk to an Engineer Dashboard

Get trigger activity Beta

GET/api/v1/trigger-activity

This endpoint is in beta. Its request and response may change.

Counts what happened to the environment's trigger events in the last 24 hours, by outcome, across every connection. Use it to find why a trigger didn't fire: the counts tell apart events that never arrived, events that matched no subscription, and events that failed signature verification. They're totals only; to follow one event, look up its delivery.

This page as markdownTriggers overview

Authorization

Authorization: Bearer $TOKEN, an access token from the client credentials grant. See Authentication.

Response 200

countsobject
Event counts over the window, keyed by outcome. Every key is always present, zeroes included. received — events that arrived at one of the environment's webhook URLs, including those that then failed signature verification. filtered — verified events that no subscription's filter or account matched. unresolved — verified events for a provider workspace that no connected account holds. delivered — events handed off for delivery to your endpoints; this does not confirm that your endpoint received them. delivery_failed — events whose handoff for delivery failed. duplicate — repeated deliveries of an event already received, such as provider retries, which are ignored. signature_failed — events that failed signature verification. discarded — events received while Triggers wasn't turned on for your environment, and dropped.
degradedboolean
True when some counts could not be read, so the counts are incomplete. Do not read zero counts as "nothing arrived" while this is true.
delivery_details_pathstring
Path, relative to the Scalekit dashboard, of the trigger delivery page. That page shows each delivery attempt to your endpoints, including failures after an event was handed off for delivery.
explains_individual_eventsboolean
Always false. Trigger events are not stored individually, so no endpoint can explain what happened to one specific event.
signature_bannerboolean
True when at least 5 events in the window failed signature verification and they make up at least half of the events received. This usually means the signing secret set on a connection does not match the provider's. Show it prominently: a provider can disable a webhook URL that keeps failing, and re-enabling it is a manual step in the provider's app configuration.
window_hoursinteger
How many hours back the counts reach, ending now.

Errors

Every error has the same body: code, message and details. See Errors and rate limits.

404Not found - Triggers isn't turned on for your environment
500Internal error - the activity counts could not be read; retry the request