Receive an incident from PagerDuty
Called by PagerDuty only. A triggered incident is investigated; a resolved one becomes a postmortem draft.
POST
/
employees
/
devops
/
webhooks
/
pagerduty
/
{credential_id}
Receive an incident from PagerDuty
curl --request POST \
--url https://app.mithunai.com/mithunai/api/v1/employees/devops/webhooks/pagerduty/{credential_id} \
--header 'Authorization: Bearer <token>'import requests
url = "https://app.mithunai.com/mithunai/api/v1/employees/devops/webhooks/pagerduty/{credential_id}"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.mithunai.com/mithunai/api/v1/employees/devops/webhooks/pagerduty/{credential_id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"results": [
{}
]
}This is the URL of a PagerDuty Generic Webhook (v3) subscription. You do not call it yourself:
the DevOps page shows the exact address beside your attached PagerDuty connection.
It takes no API key. PagerDuty signs every request with the subscription’s signing secret, and
From
X-PagerDuty-Signature (v1=<hex>, several while PagerDuty rotates the secret) is checked over the
exact bytes before anything in the body is read. The secret is the one saved with the PagerDuty
connection the address names; without one nothing is accepted. A request that does not verify is
401. It acts as the person who attached the connection, checked again on every request.
AI employees are in beta. This answers
404 unless your deployment has switched on the beta
and picking up work by itself, and for an address no DevOps attachment holds. Not yet run against
a real PagerDuty account. See DevOps.string
required
The saved PagerDuty connection attached to the DevOps employee.
What is read
event.event_type | Becomes |
|---|---|
incident.triggered | An alert on the incident (pagerduty-<incident id>), investigated |
incident.resolved | A postmortem to draft for the same incident |
| anything else | Nothing: answered 200 |
event.data it reads the incident’s id, title, urgency and service name (as a slug:
“Checkout API” is checkout-api). Nothing here can resolve an incident.
Response
object[]
required
One per item filed, with
service, title, status and task_id; empty when nothing was.Last modified on November 7, 2026
Receive an incident from PagerDuty
curl --request POST \
--url https://app.mithunai.com/mithunai/api/v1/employees/devops/webhooks/pagerduty/{credential_id} \
--header 'Authorization: Bearer <token>'import requests
url = "https://app.mithunai.com/mithunai/api/v1/employees/devops/webhooks/pagerduty/{credential_id}"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.mithunai.com/mithunai/api/v1/employees/devops/webhooks/pagerduty/{credential_id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"results": [
{}
]
}