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

Jira Issue Types API

Retrieve and manage issue types for projects.

Jira Issue Types API is one of 132 APIs that Jira publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Issue Types. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, authentication docs, rate-limit docs, and a changelog.

This API exposes 9 operations across 6 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://{domain}.atlassian.net/rest/api/3, https://your-domain.atlassian.net.

9 operations 6 paths 12 schemas 1 DELETE5 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://your-domain.atlassian.net/rest/api/3
Authentication
HTTP Basic, OAuth 2.0, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 4

Jira Issue Types API declares 4 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 5 scopes. It accepts HTTP bearer tokens (bearerAuth). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 186 scopes.

  • basicAuth — Basic authentication using an Atlassian account email and API token. Format: email:apitoken, Base64 encoded. Generate API tokens at https://id.atlassian.com/ma…
  • oauth2 — OAuth 2.0 authorization code grant (3LO) for Jira Cloud apps.
  • bearerAuth — Bearer token authentication using a personal access token (PAT) or OAuth 2.0 access token.
  • OAuth2 — OAuth2 scopes for Jira

Paths & Operations 9

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

Issue Types 9

Retrieve and manage issue types for projects.

GET
/issuetype
Jira Get All Issue Types for User
getIssueAllTypes → 200401
GET
/rest/api/3/issuetype
Get all issue types for user
getRestApi3Issuetype → 200
POST
/rest/api/3/issuetype
Create issue type
createIssueType body → 201400401403409
GET
/rest/api/3/issuetype/project
Get issue types for project
getIssueTypesForProject 2 params → 200400404
DELETE
/rest/api/3/issuetype/{id}
Delete issue type
deleteIssueType 2 params → 204400401403404409423
GET
/rest/api/3/issuetype/{id}
Get issue type
getIssueType 1 param → 200400404
PUT
/rest/api/3/issuetype/{id}
Update issue type
updateIssueType 1 param body → 200400401403404409
GET
/rest/api/3/issuetype/{id}/alternatives
Get alternative issue types
getAlternativeIssueTypes 1 param → 200404
POST
/rest/api/3/issuetype/{id}/avatar2
Load issue type avatar
createIssueTypeAvatar 4 params body → 201400401403404

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are IssueTypeDetails_2 (10 properties), IssueTypeDetails (9 properties), ProjectDetails (8 properties), Avatar (7 properties). Each schema is shown below with its type and property counts.

Scope
object
The scope of the issue type (project or global).
2 properties
IssueTypeDetails
object
Details of an issue type.
9 properties
ProjectRef
object
A reference to a Jira project.
6 properties
AvatarUrls
object
Avatar URLs in multiple sizes.
4 properties
IssueTypeUpdateBean
object
3 properties
IssueTypeCreateBean
object
4 properties 1 required
AvatarUrlsBean
object
4 properties
ProjectDetails
object
Details about a project.
8 properties
Scope_2
object
The projects the item is associated with. Indicated for items associated with [next-gen projects](https://confluence.atlassian.com/x/loMyO).
2 properties
IssueTypeDetails_2
object
Details about an issue type.
10 properties
UpdatedProjectCategory
object
A project category.
4 properties
Avatar
object
Details of an avatar.
7 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jira-issue-types-api-openapi.yml Raw ↑

Other APIs Jira publishes across the network.

Jira Cloud Platform REST API v2
Jira Service Management Operations REST API
Jira Align REST API
Jira Customer Service Management REST API
Jira Issue Comments API
Jira Issue Priorities API
Jira Issue Search API
Jira Issue Statuses API
Jira Issue Transitions API
Jira Issues API
Jira Projects API
Atlassian Remote MCP Server
Where this information came from

This is an independent, third-party profile of Jira Issue Types 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.