Custom Event Transformers <a href="">Custom Event Transformers (CETs)</a> let you send data to PagerDuty in any format, and have our event processor transform the data into a format we can work with. For example, if you want to send webhooks from a system that doesn’t support our Events API format, a CET can be used to transform the webhook data into <a href="">PD-CEF</a> event, or a generic incident or alert. Get help writing transforms, or share yours with others here! Webhook Extensions <a href="">PagerDuty webhooks</a> give you near real-time updates whenever incidents and alerts are triggered or updated. Use this space to share and discuss your projects that process PagerDuty webhooks, or get help building apps that can process webhooks. Events APIs The Events APIs (<a href="">v2</a> and <a href="">v1</a>) are designed for monitoring, deployment, ticketing, and other systems to feed data to PagerDuty that can be used to trigger, ack and resolve incidents and alerts. Looking to create a new integration or customize an existing one? This is the place to let us know what you're working on and what you need help with. REST APIs PagerDuty's REST APIs (<a href="">v2</a> and <a href="">v1</a>) can be used to create, read, update and delete just about anything in your account, so it's great for auto-provisioning integrations, building custom dashboards, and more. So, tell us what you're building, get answers on specific API calls, or let our community help with your coding issues!
About the Developer category [Developer] (2)
Filtering Fields on the v2 API [REST APIs] (3)
Missing API endpoint in the Docs [REST APIs] (5)
Create Responder API Call Failing [REST APIs] (7)
Get custom details from incident [REST APIs] (4)
Powershell - Invoke-RestMethod error [Developer] (3)
To get notified when PD incident is resolved [REST APIs] (2)
Create Incidents from SMS and display them on a wallboard [Developer] (2)
sort_by resolved_at in rest API [REST APIs] (2)
Alerts with same dedup_key are not grouped into one incident [Events APIs] (3)
Webhook v2: Incident Id uniquness [Webhook Extensions] (2)
No Postmortem API? [Developer] (2)
Custom PagerDuty Incident Kiosk / Console (Javascript) [REST APIs] (1)
unrecognized object in json [Developer] (2)
Can you update the title of an Incident using v2 API in a PowerShell Script [Developer] (2)
Efficient REST API calls in Python via persistent HTTP connections [REST APIs] (4)
Get the on-call user [REST APIs] (7)
API Documentation for Service Event Rules [REST APIs] (5)
Pagerduty + FitbitOS? [Developer] (3)
Events API v2 resolve by incident_key [Events APIs] (7)
Alert Body [Developer] (2)
AlertsAPI Endpoint [REST APIs] (5)
New webhook for On Call rotation event [Webhook Extensions] (5)
Accessing JIRA Ticket Information [REST APIs] (5)
Linked account field via API [REST APIs] (2)
Adding priority to events created with the Events API V2 [Events APIs] (2)
Node.js PagerDuty Client Recommendation [REST APIs] (2)
Send a request URL with token [REST APIs] (2)
Creating a CET for Zabbix [Custom Event Transformers] (3)
PowerShell (Invoke-RestMethod) - ERROR "team ids must be a array" [REST APIs] (4)