Developer


Custom Event Transformers <a href="https://v2.developer.pagerduty.com/docs/creating-an-integration-inline">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="https://support.pagerduty.com/hc/en-us/articles/219822127-PagerDuty-Common-Event-Format-PD-CEF-">PD-CEF</a> event, or a generic incident or alert. Get help writing transforms, or share yours with others here!
Events APIs The Events APIs (<a href="https://v2.developer.pagerduty.com/docs/events-api-v2">v2</a> and <a href="https://v1.developer.pagerduty.com/documentation/events">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.
Webhook Extensions <a href="https://v2.developer.pagerduty.com/docs/webhooks-overview">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.
REST APIs PagerDuty's REST APIs (<a href="https://v2.developer.pagerduty.com">v2</a> and <a href="https://v1.developer.pagerduty.com">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)
v2 REST API - Incident pagination issue [REST APIs] (3)
PagerDuty REST API curl shorthand: a secure bash alias [REST APIs] (1)
How to get log_entry id knowing id of the incident [REST APIs] (5)
api documentation mismatch for get schedule [Developer] (2)
Response Play API Endpoint [REST APIs] (4)
Date range format for API [REST APIs] (3)
Pagerduty + FitbitOS? [Developer] (1)
Incident duration [Developer] (3)
PagerDuty Solarwinds API [REST APIs] (4)
Get Metrics via API [REST APIs] (4)
Developing an extension similar to HipChat or Jira [Webhook Extensions] (3)
Add HTML table via API [Events APIs] (2)
Statistics and Counts in v2 [REST APIs] (8)
API Documentation for Service Event Rules [REST APIs] (4)
Setting Incidents: incident_key in EventsV2 API [Events APIs] (6)
Get the on-call user [REST APIs] (4)
Get custom details from incident [REST APIs] (2)
Query users by team id [REST APIs] (5)
Scripting Random Incidents for Testing [Custom Event Transformers] (1)
Why are Google Chart images not showing on incidents? [Events APIs] (4)
Incidents acknowledged by users in a timeframe [REST APIs] (4)
API v2 Feedback [Events APIs] (5)
Separate alerts for custom integration [Events APIs] (5)
how to get from address through webhook in email integration? [Webhook Extensions] (4)
HttpClient in C# "application/vnd.pagerduty+json;version=2" format wrong [REST APIs] (2)
v2 API - Create New Incident [REST APIs] (2)
Make a public, embeddable calendar view of an on-call schedule [Developer] (5)
Max and available user count API? [REST APIs] (7)
Building a custom webhook handler: tips and suggestions [Webhook Extensions] (1)