---
title: "Update a Field"
method: PUT
path: "/incidents/custom_fields/{field_id}"
tags: ["Incident Custom Fields"]
deprecated: true
---

# Update a Field

`PUT /incidents/custom_fields/{field_id}`

> **Deprecated.**

<!-- theme: warning -->
> ### Deprecated
> This endpoint is deprecated and only works for fields on the Base Incident Type. \
> For more flexibility, we recommend using the Incident Types endpoint: \
> [/incidents/types/{type_id_or_name}/custom_fields/{field_id}](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields~1{field_id}/put)

Update a Custom Field on the Base Incident Type.

Scoped OAuth requires: `custom_fields.write`

## Path parameters

- `field_id` string, required

## Request body

- object
  - `field` CustomFieldsEditableField, required
    - `display_name` DisplayName — unresolved $ref
    - `description` Description — unresolved $ref
    - `default_value` DefaultValue — unresolved $ref
    - `enabled` true | false — Whether the field is enabled.

## Response `200`

The field object updated.

- object
  - `field` CustomFieldsField, required
    - `created_at` string, date-time, required — The date/time the object was created at.
    - `data_type` DataType, required — unresolved $ref
    - `default_value` DefaultValue — unresolved $ref
    - `description` Description — unresolved $ref
    - `display_name` DisplayName, required — unresolved $ref
    - `field_type` FieldType, required — unresolved $ref
    - `id` string, required — The ID of the resource.
    - `name` Name, required — unresolved $ref
    - `self` string, url, nullable, required — The API show URL at which the object is accessible
    - `summary` string, nullable, required — A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to `display_name`.
    - `type` 'field', required
    - `updated_at` string, date-time, required — The date/time the object was last updated.

## Other responses

- `400` — Caller provided invalid arguments. Please review the response for error details. Retrying with the same arguments will *not* work.
- `403` — Caller is not authorized to view the requested resource. While your authentication is valid, the authenticated user or token does not have permission to perform this action.
- `404` — The requested resource was not found.
- `500` — Internal Server Error the PagerDuty server experienced an error.

---

[API](https://skmtc.net/pagerduty/apis/rest-api.md) · [All operations](https://skmtc.net/pagerduty/apis/rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pagerduty/rest-api/revisions/b679a8f3f02c/schema)