REST API endpoints for issue fields
Use the REST API to create and manage issue fields for the authenticated user.
List issue fields
Lists all issue fields for the authenticated user. OAuth app tokens and personal access tokens (classic) need the read:user scope to use this endpoint.
Tokens de acceso granulares para "List issue fields"
Este punto de conexión funciona con los siguientes tipos de token pormenorizados:
El token pormenorizado debe tener el siguiente conjunto de permisos:
- "Issue Fields" user permissions (read)
Códigos de estado de respuesta HTTP para "List issue fields"
| código de estado | Descripción |
|---|---|
200 | OK |
404 | Resource not found |
Ejemplos de código para "List issue fields"
Ejemplo de solicitud
curl -L \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/user/issue-fieldsResponse
Status: 200[
{
"id": 1,
"node_id": "IFT_kwDNAd3NAZo",
"name": "Text field",
"description": "DRI",
"data_type": "text",
"created_at": "2024-12-11T14:39:09Z",
"updated_at": "2024-12-11T14:39:09Z"
},
{
"id": 2,
"node_id": "IFSS_kwDNAd3NAZs",
"name": "Priority",
"description": "Level of importance",
"data_type": "single_select",
"options": [
{
"id": 1,
"name": "High",
"color": "red"
},
{
"id": 2,
"name": "Medium",
"color": "yellow"
},
{
"id": 3,
"name": "Low",
"color": "green"
}
],
"created_at": "2024-12-11T14:39:09Z",
"updated_at": "2024-12-11T14:39:09Z"
},
{
"id": 3,
"node_id": "IFMS_kwDNAd3NAZt",
"name": "Categories",
"description": "Issue categories",
"data_type": "multi_select",
"options": [
{
"id": 4,
"name": "Frontend",
"color": "blue"
},
{
"id": 5,
"name": "Backend",
"color": "green"
},
{
"id": 6,
"name": "Infrastructure",
"color": "purple"
}
],
"created_at": "2024-12-11T14:39:09Z",
"updated_at": "2024-12-11T14:39:09Z"
}
]Create an issue field
Creates a new issue field for the authenticated user's personal account.
OAuth app tokens and personal access tokens (classic) need the user scope to use this endpoint.
Tokens de acceso granulares para "Create an issue field"
Este punto de conexión funciona con los siguientes tipos de token pormenorizados:
El token pormenorizado debe tener el siguiente conjunto de permisos:
- "Issue Fields" user permissions (write)
Parámetros para "Create an issue field"
| Nombre, Tipo, Descripción |
|---|
accept string Setting to |
| Nombre, Tipo, Descripción | |||||
|---|---|---|---|---|---|
name string ObligatorioName of the issue field. | |||||
description string or null Description of the issue field. | |||||
data_type string ObligatorioThe data type of the issue field. Puede ser uno de los siguientes: | |||||
visibility string The visibility of the issue field. Can be Puede ser uno de los siguientes: | |||||
options array of objects or null Options for select fields. Required when data_type is 'single_select' or 'multi_select'. | |||||
Properties of |
| Nombre, Tipo, Descripción |
|---|
name string ObligatorioName of the option. |
description string or null Description of the option. |
color string ObligatorioColor for the option. Puede ser uno de los siguientes: |
priority integer ObligatorioPriority of the option for ordering. |
Códigos de estado de respuesta HTTP para "Create an issue field"
| código de estado | Descripción |
|---|---|
200 | OK |
404 | Resource not found |
422 | Validation failed, or the endpoint has been spammed. |
Ejemplos de código para "Create an issue field"
Ejemplo de solicitud
curl -L \
-X POST \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/user/issue-fields \
-d '{"name":"Priority","description":"Level of importance for the issue","data_type":"single_select","visibility":"restricted","options":[{"name":"High","description":"High priority","color":"red","priority":1},{"name":"Medium","description":"Medium priority","color":"yellow","priority":2},{"name":"Low","description":"Low priority","color":"green","priority":3}]}'Response
Status: 200{
"id": 512,
"node_id": "IF_kwDNAd3NAZr",
"name": "Priority",
"description": "Level of importance for the issue",
"data_type": "single_select",
"options": [
{
"id": 1,
"name": "High",
"description": "High priority",
"color": "red",
"priority": 1,
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
},
{
"id": 2,
"name": "Medium",
"description": "Medium priority",
"color": "yellow",
"priority": 2,
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
},
{
"id": 3,
"name": "Low",
"description": "Low priority",
"color": "green",
"priority": 3,
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
}
],
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
}Update an issue field
Updates an issue field for the authenticated user.
The authenticated user must own the issue field. OAuth app tokens and personal access tokens (classic)
need the user scope to use this endpoint.
Tokens de acceso granulares para "Update an issue field"
Este punto de conexión funciona con los siguientes tipos de token pormenorizados:
El token pormenorizado debe tener el siguiente conjunto de permisos:
- "Issue Fields" user permissions (write)
Parámetros para "Update an issue field"
| Nombre, Tipo, Descripción |
|---|
accept string Setting to |
| Nombre, Tipo, Descripción |
|---|
issue_field_id integer ObligatorioThe unique identifier of the issue field. |
| Nombre, Tipo, Descripción | ||||||
|---|---|---|---|---|---|---|
name string Name of the issue field. | ||||||
description string or null Description of the issue field. | ||||||
visibility string The visibility of the issue field. Can be Puede ser uno de los siguientes: | ||||||
options array of objects Options for select fields. Only applicable when updating single_select or multi_select fields. When provided, this array replaces the entire existing set of options rather than adding to or updating individual options. To retain or update an existing option, include it in the array with its | ||||||
Properties of |
| Nombre, Tipo, Descripción |
|---|
id integer The id of an existing option to retain or update. Omit this when creating a new option. |
name string ObligatorioName of the option. |
description string or null Description of the option. |
color string ObligatorioColor for the option. Puede ser uno de los siguientes: |
priority integer ObligatorioPriority of the option for ordering. |
Códigos de estado de respuesta HTTP para "Update an issue field"
| código de estado | Descripción |
|---|---|
200 | OK |
404 | Resource not found |
422 | Validation failed, or the endpoint has been spammed. |
Ejemplos de código para "Update an issue field"
Ejemplo de solicitud
curl -L \
-X PATCH \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/user/issue-fields/ISSUE_FIELD_ID \
-d '{"name":"Priority","description":"Level of importance for the issue"}'Response
Status: 200{
"id": 512,
"node_id": "IF_kwDNAd3NAZr",
"name": "Priority",
"description": "Level of importance for the issue",
"data_type": "single_select",
"options": [
{
"id": 1,
"name": "High",
"description": "High priority",
"color": "red",
"priority": 1,
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
},
{
"id": 2,
"name": "Medium",
"description": "Medium priority",
"color": "yellow",
"priority": 2,
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
},
{
"id": 3,
"name": "Low",
"description": "Low priority",
"color": "green",
"priority": 3,
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
}
],
"created_at": "2025-01-15T10:30:15Z",
"updated_at": "2025-01-15T10:30:15Z"
}Delete an issue field
Deletes an issue field for the authenticated user.
The authenticated user must own the issue field. OAuth app tokens and personal access tokens (classic)
need the user scope to use this endpoint.
Tokens de acceso granulares para "Delete an issue field"
Este punto de conexión funciona con los siguientes tipos de token pormenorizados:
El token pormenorizado debe tener el siguiente conjunto de permisos:
- "Issue Fields" user permissions (write)
Parámetros para "Delete an issue field"
| Nombre, Tipo, Descripción |
|---|
accept string Setting to |
| Nombre, Tipo, Descripción |
|---|
issue_field_id integer ObligatorioThe unique identifier of the issue field. |
Códigos de estado de respuesta HTTP para "Delete an issue field"
| código de estado | Descripción |
|---|---|
204 | A header with no content is returned. |
404 | Resource not found |
422 | Validation failed, or the endpoint has been spammed. |
Ejemplos de código para "Delete an issue field"
Ejemplo de solicitud
curl -L \
-X DELETE \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer <YOUR-TOKEN>" \
-H "X-GitHub-Api-Version: 2026-03-10" \
https://api.github.com/user/issue-fields/ISSUE_FIELD_IDA header with no content is returned.
Status: 204