![]()
api.pagerduty.com · Developer toolsSubscribeShare
PagerDuty REST API breaking changes
The breaking changes PagerDuty REST API announced that Okapi tracks: 2 in all.
Do you run the PagerDuty REST API? Make sure your users call it right →
At a glance
- API host
api.pagerduty.com- Kind
- Developer tools
- Breaking changes tracked
- 2 breaking changes with no date yet
- Last updated
Deprecated, no date yet 2
-
No date
/incidents/custom_fields*Endpoint removal Deprecated, no date -
No date
/users/{id}/sessions*Endpoint removal Deprecated, no date
Where Okapi reads it
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub