---
title: "Create a Field Option"
method: POST
path: "/incidents/custom_fields/{field_id}/field_options"
tags: ["Incident Custom Fields"]
deprecated: true
---

# Create a Field Option

`POST /incidents/custom_fields/{field_id}/field_options`

> **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}/field_options](openapiv3.json/paths/~1incidents~1types~1{type_id_or_name}~1custom_fields~1{field_id}~1field_options/post)

Create a new Field Option for a Custom Field on the Base Incident Type. Field Options may only be created for Fields that have `field_options`. A Field may have no more than 10 enabled options.

Scoped OAuth requires: `custom_fields.write`

## Path parameters

- `field_id` string, required

## Request body

- object
  - `field_option` CustomFieldsFieldOption, required
    - `data` object, required
      - `data_type` 'string', required — The kind of data represented by this option. Must match the Field's `data_type`.
      - `value` string, required
    - `id` string, required — The ID of the resource.
    - `type` 'field_option', required
    - `updated_at` string, date-time, required — The date/time the object was last updated.
    - `created_at` string, date-time, required — The date/time the object was created at.

## Response `201`

The field option created.

- object
  - `field_option` CustomFieldsFieldOption, required
    - `data` object, required
      - `data_type` 'string', required — The kind of data represented by this option. Must match the Field's `data_type`.
      - `value` string, required
    - `id` string, required — The ID of the resource.
    - `type` 'field_option', required
    - `updated_at` string, date-time, required — The date/time the object was last updated.
    - `created_at` string, date-time, required — The date/time the object was created at.

## 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)