SCscalekit
Triggers

Get trigger event counts for the environment

Changed on

Returns counts of what happened to the environment's trigger events over the last 24 hours, grouped by outcome. Use this endpoint to diagnose a trigger that did not fire: the counts tell apart events that never arrived, events that arrived and matched no subscription filter, events for a provider workspace that no connected account holds, events that failed signature verification, and events whose handoff for delivery failed. The endpoint takes no parameters and covers every connection in the environment. Counts are aggregates only: no record of an individual event is kept, so no endpoint can explain what happened to one specific event. Returns the counts, the window they cover in hours, whether most recent arrivals failed signature verification, whether the counts are incomplete, and the dashboard path where delivery attempts can be inspected.

get/api/v1/trigger-activity

Request

Response

Event counts per outcome for the last 24 hours, with the signature-failure and incomplete-data indicators

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 was not enabled for the 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. Show this limitation to the user rather than hiding it.

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.

Example response

{
  "counts": {
    "delivered": 88,
    "delivery_failed": 0,
    "discarded": 0,
    "duplicate": 5,
    "filtered": 30,
    "received": 120,
    "signature_failed": 0,
    "unresolved": 2
  },
  "delivery_details_path": "/trigger-delivery",
  "window_hours": 24
}

Changes