PagerDuty
Hotpot competes with PagerDuty, but not everyone is ready to switch directly to Hotpot to deliver pages. In the meantime, you can use the Hotpot PagerDuty integration to collect paging information from PagerDuty!
Hotpot supports two methods to integrate with PagerDuty. If you need narrowly scoped permissions, use the OAuth method. A simpler method is to create an API key under Integrations > API Access Keys. Name the key well and do not select the read-only option.
Hotpot uses these API endpoints in PagerDuty.
| Endpoint | Notes |
|---|---|
| GET /escalation_policies | Include targets in the request, required to determine schedules and users involved in the escalation policy. |
| POST /escalation_policies | Used for creating an escalation policy that Hotpot can manage. |
| GET /escalation_policies/:id | |
| PUT /escalation_policies/:id | |
| GET /schedules | Includes schedule_layers. |
| POST /schedules | |
| DELETE /schedules/:id | Deletes outdated schedules that have drifted (caused by changes made in PagerDuty but not in Hotpot). It only deletes schedules that are part of the escalation policy that Hotpot manages. |
| PUT /schedules/:id | Used to update a Hotpot-managed schedule. |
| GET /users | Maps PagerDuty users to Hotpot users. It also includes contact_methods for additional email address mapping. Optional, only necessary if Hotpot manages PagerDuty’s notification endpoints. |
Hotpot also manages webhook subscriptions that create moments for relevant PagerDuty events:
It's important that the PagerDuty sign-in email address is the same as the address in Hotpot. Hotpot uses that email address to map Hotpot users to PagerDuty users.