/incidents/custom_fields* → endpoint removal
PagerDuty REST API
Deprecated, no date
PagerDuty has deprecated the /incidents/custom_fields* endpoints without announcing a shutdown date. These routes only work for fields on the Base Incident Type and will eventually fail. The change applies to all requests targeting the legacy incident custom fields path.
Calls it hits
/incidents/custom_fields*
What to use instead of these calls
Manage custom fields per incident type using /incidents/types/{type_id_or_name}/custom_fields and its field_options endpoints instead.
In PagerDuty REST API's words
This endpoint is deprecated and only works for fields on the Base Incident Type.
Facts
- API
- PagerDuty REST API
api.pagerduty.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against PagerDuty REST API's own pages
Questions
When does this change take effect?
PagerDuty REST API deprecated /incidents/custom_fields* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: PagerDuty REST API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from PagerDuty REST API 1
-
No date
/users/{}/sessions*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.