Events API alerts, routed to the right on-call engineer

How the Events API integration works

1. Create a Events API integration in EvoHub On-Call and pick the escalation policy it should notify.
2. EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into Events API using the steps below.
3. Each Events API alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
4. Resolve by sending event_action "resolve" with the same dedup_key.

Set up Events API

Create the integration in EvoHub first — it shows your personal integration URL to paste below.

curl -X POST '<your EvoHub integration URL>' \
  -H 'Content-Type: application/json' \
  -d '{
    "summary": "DB down",       // must
    "severity": "critical",     // optional — critical|error|warning|info (default: medium)
    "source": "db-prod-01",     // optional
    "description": "details",   // optional
    "dedup_key": "db-down",     // optional — groups repeats, returned in response
    "event_action": "trigger"   // optional — trigger|acknowledge|resolve (default: trigger)
  }'

# Key can also go in the body ("routing_key": "<INTEGRATION_KEY>")
# or in a header (Authorization: Bearer <INTEGRATION_KEY>)

Events API + EvoHub — FAQ

How do I connect Events API to EvoHub?

In EvoHub, go to On-Call → Integrations, add Events API, and choose an escalation policy. Then configure Events API with the integration URL EvoHub shows you — the exact steps are on this page.

Do Events API alerts resolve automatically in EvoHub?

Resolve by sending event_action "resolve" with the same dedup_key.

How is the Events API integration priced?

Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.