# /incidents/custom_fields is deprecated

PagerDuty REST API deprecated /incidents/custom_fields* without giving a shutdown date yet.

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.

## What to use instead

Manage custom fields per incident type using /incidents/types/{type_id_or_name}/custom_fields and its field_options endpoints instead.

- API: PagerDuty REST API (api.pagerduty.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/incidents/custom_fields*`
- Source: [Announcement](https://raw.githubusercontent.com/PagerDuty/api-schema/main/reference/REST/openapiv3.json)
- Verified: October 26, 2026, against PagerDuty REST API's own pages
- Page: https://www.okapi.bot/providers/pagerduty-rest-api/breaking-changes/incidents-custom-fields-is-deprecated/

## PagerDuty REST API's words

> This endpoint is deprecated and only works for fields on the Base Incident Type.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent