How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Atlassian Issue Field Configurations API

The Issue Field Configurations API from Atlassian — 9 operation(s) for issue field configurations.

Atlassian Issue Field Configurations API is one of 183 APIs that Atlassian publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 17 JSON Schema definitions.

Tagged areas include Issue Field Configurations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 17 JSON Schemas.

This API exposes 15 operations across 9 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1001.0.0-SNAPSHOT-67b5c6e5f3598d7ec1649016d026468ab2838a77.

Requests are made against a single base URL, https://your-domain.atlassian.net.

15 operations 9 paths 18 schemas 2 DELETE5 GET3 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1001.0.0-SNAPSHOT-67b5c6e5f3598d7ec1649016d026468ab2838a77
Server
https://your-domain.atlassian.net
Authentication
OAuth 2.0, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Atlassian Issue Field Configurations API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 183 scopes. It accepts HTTP basic authentication (basicAuth).

  • OAuth2 — OAuth2 scopes for Jira
  • basicAuth — You can access this resource via basic auth.

Paths & Operations 15

Across 9 paths, the API surfaces 15 operations — 2 DELETE, 5 GET, 3 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

Issue Field Configurations 15
GET
/rest/api/3/fieldconfiguration
Atlassian Get All Field Configurations
atlassianGetallfieldconfigurations 5 params → 200401403
POST
/rest/api/3/fieldconfiguration
Atlassian Create Field Configuration
atlassianCreatefieldconfiguration body → 200400401403
DELETE
/rest/api/3/fieldconfiguration/{id}
Atlassian Delete Field Configuration
atlassianDeletefieldconfiguration 1 param → 204400401403404
PUT
/rest/api/3/fieldconfiguration/{id}
Atlassian Update Field Configuration
atlassianUpdatefieldconfiguration 1 param body → 204400401403404
GET
/rest/api/3/fieldconfiguration/{id}/fields
Atlassian Get Field Configuration Items
atlassianGetfieldconfigurationitems 3 params → 200401403404
PUT
/rest/api/3/fieldconfiguration/{id}/fields
Atlassian Update Field Configuration Items
atlassianUpdatefieldconfigurationitems 1 param body → 204400401403404
GET
/rest/api/3/fieldconfigurationscheme
Atlassian Get All Field Configuration Schemes
atlassianGetallfieldconfigurationschemes 3 params → 200400401403
POST
/rest/api/3/fieldconfigurationscheme
Atlassian Create Field Configuration Scheme
atlassianCreatefieldconfigurationscheme body → 201400401403
GET
/rest/api/3/fieldconfigurationscheme/mapping
Atlassian Get Field Configuration Issue Type Items
atlassianGetfieldconfigurationschememappings 3 params → 200400401403404
GET
/rest/api/3/fieldconfigurationscheme/project
Atlassian Get Field Configuration Schemes For Projects
atlassianGetfieldconfigurationschemeprojectmapping 3 params → 200400401403
PUT
/rest/api/3/fieldconfigurationscheme/project
Atlassian Assign Field Configuration Scheme To Project
atlassianAssignfieldconfigurationschemetoproject body → 204400401403404
DELETE
/rest/api/3/fieldconfigurationscheme/{id}
Atlassian Delete Field Configuration Scheme
atlassianDeletefieldconfigurationscheme 1 param → 204400401403404
PUT
/rest/api/3/fieldconfigurationscheme/{id}
Atlassian Update Field Configuration Scheme
atlassianUpdatefieldconfigurationscheme 1 param body → 204400401403404
PUT
/rest/api/3/fieldconfigurationscheme/{id}/mapping
Atlassian Assign Issue Types To Field Configurations
atlassianSetfieldconfigurationschememapping 1 param body → 204400401403404
POST
/rest/api/3/fieldconfigurationscheme/{id}/mapping/delete
Atlassian Remove Issue Types From Field Configuration Scheme
atlassianRemoveissuetypesfromglobalfieldconfigurationscheme 1 param body → 204400401403404

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are PageBeanFieldConfigurationSchemeProjects (7 properties), PageBeanFieldConfigurationIssueTypeItem (7 properties), PageBeanFieldConfigurationScheme (7 properties), PageBeanFieldConfigurationItem (7 properties). Each schema is shown below with its type and property counts.

PageBeanFieldConfigurationIssueTypeItem
object
A page of items.
7 properties
FieldConfigurationItemsDetails
object
Details of field configuration items.
1 property 1 required
PageBeanFieldConfigurationSchemeProjects
object
A page of items.
7 properties
FieldConfigurationScheme
object
Details of a field configuration scheme.
3 properties 2 required
PageBeanFieldConfigurationScheme
object
A page of items.
7 properties
FieldConfigurationItem
object
A field within a field configuration.
5 properties 1 required
FieldConfiguration
object
Details of a field configuration.
4 properties 3 required
AssociateFieldConfigurationsWithIssueTypesRequest
object
Details of a field configuration to issue type mappings.
1 property 1 required
ErrorCollection
object
Error messages from an operation.
3 properties
FieldConfigurationToIssueTypeMapping
object
The field configuration to issue type mapping.
2 properties 2 required
IssueTypeIdsToRemove
object
The list of issue type IDs to be removed from the field configuration scheme.
1 property 1 required
FieldConfigurationSchemeProjects
object
Project list with assigned field configuration schema.
2 properties 1 required
FieldConfigurationDetails
object
Details of a field configuration.
2 properties 1 required
FieldConfigurationIssueTypeItem
object
The field configuration for an issue type.
3 properties 3 required
UpdateFieldConfigurationSchemeDetails
object
The details of the field configuration scheme.
2 properties 1 required
PageBeanFieldConfigurationDetails
object
A page of items.
7 properties
PageBeanFieldConfigurationItem
object
A page of items.
7 properties
FieldConfigurationSchemeProjectAssociation
object
Associated field configuration scheme and project.
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

atlassian-issue-field-configurations-api-openapi.yml Raw ↑

Other APIs Atlassian publishes across the network.

Atlassian Jira Software Backlog API
Atlassian Jira Software Board API
Atlassian Jira Software Epic API
Atlassian Jira Software Sprint API
Atlassian Jira Software Development Information API
Atlassian Jira Software Feature Flags API
Atlassian Jira Software Deployments API
Atlassian Jira Software Builds API
Atlassian Jira Software Remote Links API
Atlassian Jira Software Security Information API
Atlassian Jira Service Management Customer API
Atlassian Jira Service Management Info API
Where this information came from

This is an independent, third-party profile of Atlassian Issue Field Configurations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.