PagerDuty Events API v2 inbound

Many tools can send PagerDuty Events API v2 events. Point them at Squasher instead, and a trigger opens a Squasher incident, acknowledge acknowledges it, and resolve resolves it. To send Squasher incidents to PagerDuty, see the PagerDuty destination.

What you need

A tool or script that sends Events API v2 events and lets you change the URL.
The Squasher CLI, signed in with write access to the project. See Alert sources.

Connect a sender

Create the connector

squasher alert-connectors create \
  --project "$SQUASHER_PROJECT_ID" \
  --provider pagerduty_events_v2 \
  --display-name "Legacy paging events"

Save setup.endpoint and setup.routing_key from the output. The routing key is the connector secret, not a key from PagerDuty.

Send events to Squasher

Set the sender’s events URL to setup.endpoint, and its routing key to setup.routing_key. To test with curl, put the two values in SQUASHER_ALERT_ENDPOINT and SQUASHER_ALERT_SECRET first:

curl --fail-with-body "$SQUASHER_ALERT_ENDPOINT" \
  -H "Content-Type: application/json" \
  -d '{
    "routing_key": "'"$SQUASHER_ALERT_SECRET"'",
    "event_action": "trigger",
    "dedup_key": "database-primary-unavailable",
    "payload": {
      "summary": "Primary database is unavailable",
      "source": "database-primary",
      "severity": "critical",
      "timestamp": "2026-09-25T08:00:00Z"
    }
  }'

Resolve the test incident

Send the same dedup_key with "event_action": "resolve", a full payload, and a later timestamp. Check that the same incident resolves.

Squasher also accepts the secret in an Authorization: Bearer header instead of routing_key.

How Squasher reads an event

Events API v2 field	Squasher incident
`dedup_key`	Alert key. Required on every event, also on `trigger`.
`event_action: trigger`	Opens the incident, or updates it if it is open.
`event_action: acknowledge`	Marks the incident as acknowledged.
`event_action: resolve`	Resolves the incident.
`payload.summary`	Title and summary. Required on `trigger`.
`payload.severity`	Severity: `critical` and `error` are `sev-1`, `warning` is `sev-2`, `info` is `sev-3`. Required on `trigger`.
`payload.source`	Required on `trigger`. Added to the message on the incident timeline.
`payload.timestamp`	Event time, and part of the event key.
`payload.component`, `group`, `class`, `custom_details`	Added to the message on the incident timeline.
`client_url`, `links[].href`	Added to the message as links. The first is the link back to the alert on the incident.

Limits

Squasher does not create a dedup_key for you. A trigger without one gets 422.
Send payload.timestamp on every event, also on acknowledge and resolve. Without it, Squasher builds the event key from the dedup key, the action, and the content. A second event with the same values within 90 days is then treated as a repeat and ignored.
When you send a payload with acknowledge or resolve, it must have summary, source, and severity, as on trigger.
Squasher does not support the PagerDuty change events API or the older Events API v1.

Get started

Guides

PagerDuty Events API v2 inbound

What you need

Connect a sender

How Squasher reads an event

Limits

Next steps

Alert sources

Route incidents

​What you need

​Connect a sender

​How Squasher reads an event

​Limits

​Next steps

Alert sources

Route incidents

What you need

Connect a sender

How Squasher reads an event

Limits

Next steps