Webhooks allow you to receive HTTP callbacks when incidents are triggered and updated on a service. Details surrounding the event will be sent to a URL that you specify, such as Slack, HipChat, or your own custom PagerDuty webhook processor.
Add a webhook
Go to the Configuration menu and select Services, then click the name of the service you want to add a webhook to.
By default, you will be directed to Incidents tab for the service. To add a webhook, switch over to the Integrations tab.
Click Add an extension.
- For the Extension Type select your webhook type or Generic Webhook.
Enter a unique Extension Name.
Enter your Endpoint URL.
If you'd like to verify your webhook configuration to make sure it's working as expected, trigger a test incident by clicking New Incident on your service, and then check your endpoint service for updates. For example, if you use a service like RequestBin, you can view the POST request sent by PagerDuty after triggering an incident.
HTTP Authentication and Web Server Access
Webhooks can be sent to any publicly accessible web server, on any port, with or without encryption, and can include a username and password for HTTP basic authentication.
Specify a username and password
If your web server uses HTTP basic authentication, you can add the username and password to the URL before the host address. Special characters such as
@ in the password should be percent-encoded.
If you specify
http:// in your Endpoint URL, we will try to initiate a standard HTTP connection on port 80. Likewise, entering
https:// means we will attempt to make a secure connection on port 443. To override the default port, simply add a colon (
:) after the host address with the desired port number, just like you would enter in your web browser.
Restrict access to just PagerDuty IPs
You can view our list of IPs to whitelist here.
Can I use a self-signed certificate for webhooks?
Yes. Web servers presenting self-signed or expired certificates will still receive webhooks.
Temporary Blocks and Blacklisting
When a site goes down, it is a generally expected behavior that events can't be received to your webhook, or that it will become completely disabled.
When events are sent to your webhook endpoints, PagerDuty expects a 200 response within 5 seconds. If there is no response, or if there is any response other than a 200, PagerDuty will periodically retry sending the webhook call until it receives a 200.
For example, if a 500 response is received, it is considered a transient issue and regular retry logic is applied. First the event is rescheduled for delivery 50 seconds in the future. If it continues to 500, the PagerDuty will back off by a multiple of 1.25^N for 7 more tries (8 retries total). This takes about 20 minutes.
After these retries are exhausted, the endpoint will be temporarily disabled for 30 minutes. PagerDuty will continue to accumulate events for the endpoint while it is temporarily disabled, but they are all scheduled for after the disable has expired. If the payload can't be sent after this, the endpoint will be disabled for exponentially longer periods of time (again, 1.25^N), up to 6 retries total (about 7.5 hours).
If PagerDuty still can't deliver a webhook event at that point, it will blacklist the endpoint and show that the webhook is disabled in the web app. This means that it will discard any queued events and no longer send events to this endpoint until the user manually unblocks it via the user interface.