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 Status API

This resource represents statuses. Use it to search, get, create, delete, and change statuses.

Jira Status API is one of 132 APIs that Jira publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Status. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and an API reference.

This API exposes 9 operations across 6 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df.

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

9 operations 6 paths 17 schemas 1 DELETE6 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df
Base URL
https://your-domain.atlassian.net/rest/api/2
Authentication
OAuth 2.0, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Jira Status API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 186 scopes. It accepts HTTP basic authentication (basicAuth).

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

Paths & Operations 9

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

Status 9

This resource represents statuses. Use it to search, get, create, delete, and change statuses.

DELETE
/rest/api/3/statuses
Bulk delete Statuses
deleteStatusesById 1 param → 204400401
GET
/rest/api/3/statuses
Bulk get statuses
getStatusesById 1 param → 200400401
POST
/rest/api/3/statuses
Bulk create statuses
createStatuses body → 200400401409
PUT
/rest/api/3/statuses
Bulk update statuses
updateStatuses body → 204400401409
GET
/rest/api/3/statuses/byNames
Bulk get statuses by name
getStatusesByName 2 params → 200400401
GET
/rest/api/3/statuses/search
Search statuses paginated
search 6 params → 200400401
GET
/rest/api/3/statuses/{statusId}/project/{projectId}/issueTypeUsages
Get issue type usages by status and project
getProjectIssueTypeUsagesForStatus 4 params → 200400401404
GET
/rest/api/3/statuses/{statusId}/projectUsages
Get project usages by status
getProjectUsagesForStatus 3 params → 200400401404
GET
/rest/api/3/statuses/{statusId}/workflowUsages
Get workflow usages by status
getWorkflowUsagesForStatus 3 params → 200400401404

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are PageOfStatuses (7 properties), JiraStatus (5 properties), StatusUpdate (4 properties), StatusCreate (3 properties). Each schema is shown below with its type and property counts.

StatusWorkflowUsagePage
object
A page of workflows.
2 properties
StatusProjectIssueTypeUsage
object
The list of issue types.
1 property
StatusCreateRequest
object
Details of the statuses being created and their scope.
2 properties 2 required
StatusProjectIssueTypeUsagePage
object
A page of issue types.
2 properties
StatusProjectUsage
object
The project.
1 property
StatusUpdateRequest
object
The list of statuses that will be updated.
1 property 1 required
StatusProjectIssueTypeUsageDTO
object
The issue types using this status in a project.
3 properties
StatusCreate
object
Details of the status being created.
3 properties 2 required
StatusProjectUsagePage
object
A page of projects.
2 properties
PageOfStatuses
object
7 properties
StatusScope
object
The scope of the status.
2 properties 1 required
StatusWorkflowUsageWorkflow
object
The worflow.
1 property
StatusProjectUsageDTO
object
The projects using this status.
2 properties
ProjectId
objectnull
Project ID details.
1 property 1 required
StatusUpdate
object
Details of the status being updated.
4 properties 3 required
JiraStatus
object
Details of a status.
5 properties
StatusWorkflowUsageDTO
object
Workflows using the status.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jira-status-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 Issue Types API
Jira Issues API
Jira Projects API
Where this information came from

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