> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# 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](https://docs.scalekit.com/agentkit/reference/triggers/look-up-a-delivery/).

**Response (200)**

| Name | Type | Description |
| --- | --- | --- |
| `counts` | object | 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. |
| `degraded` | boolean | 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_path` | string | 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_events` | boolean | Always false. Trigger events are not stored individually, so no endpoint can explain what happened to one specific event. |
| `signature_banner` | boolean | 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_hours` | integer | How many hours back the counts reach, ending now. |

**Errors**

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

**Request**

```bash
curl -sS -X GET \
  "$SCALEKIT_ENVIRONMENT_URL/api/v1/trigger-activity" \
  -H "Authorization: Bearer $TOKEN"
```

**Response**

```json
{
  "window_hours": 24,
  "counts": {
    "received": "45",
    "filtered": "6",
    "unresolved": "0",
    "delivered": "39",
    "delivery_failed": "0",
    "duplicate": "2",
    "signature_failed": "0",
    "discarded": "0"
  },
  "signature_banner": false,
  "degraded": false,
  "explains_individual_events": false,
  "delivery_details_path": "/trigger-delivery"
}
```

**Python SDK:** `scalekit_client.actions.triggers.get_activity`

Count what happened to this environment's trigger events recently.

```python
scalekit_client.actions.triggers.get_activity() -> GetTriggerActivityResponse
```

Example:

```python
result = scalekit_client.actions.triggers.get_activity()
```

Returns `GetTriggerActivityResponse`: Counts per outcome over `window`, plus signature and degraded flags.


Part of [Triggers](https://docs.scalekit.com/agentkit/reference/triggers/) in the [AgentKit API reference](https://docs.scalekit.com/agentkit/reference/). Authentication: https://docs.scalekit.com/agentkit/reference/authentication.md. Errors and rate limits: https://docs.scalekit.com/agentkit/reference/errors.md. Pagination: https://docs.scalekit.com/agentkit/reference/pagination.md


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |