PUT /incidents/types/{type_id_or_name}/custom_fields/{field_id}
Update a custom field for an incident type. Field Options can also be updated within the same call.
Custom Fields (CF) are a feature which will allow customers to extend Incidents with their own custom data, to provide additional context and support features such as customized filtering, search and analytics. Custom Fields can be applied to different incident types.
Scoped OAuth requires: custom_fields.write
Servers
- https://api.pagerduty.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
type_id_or_name |
String | Yes |
The ID or name of the Incident Type. |
field_id |
String | Yes |
The ID of the field. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Accept |
String | Yes |
The Default value: "application/vnd.pagerduty+json;version=2" |
Content-Type |
String | Yes |
Possible values:
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
field |
Object | Yes |
Details of the custom field to be updated. |
field.default_value |
String | No |
The default value of the custom field. |
field.description |
String | No |
The description of the custom field. |
field.field_options[] |
Array | No |
List of options to upsert on the custom field. Can only be applied to fields with a |
field.display_name |
String | No |
The display name of the Incident Type. |
field.enabled |
Boolean | No |
Whether the Incident Type is enabled. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.