Jira Issue Search API
Search for issues using JQL (Jira Query Language).
Jira Issue Search API is one of 12 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 Search. 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 2 operations across 1 path, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 3.
Requests are made against a single base URL, https://{domain}.atlassian.net/rest/api/3.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Jira Issue Search API declares
3 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).
By default, every request must be authenticated.
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.
Paths & Operations 2
Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Search for issues using JQL (Jira Query Language).
Schemas 32
The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are IssueFields (27 properties), IssueBean (10 properties), Worklog (10 properties), Comment (10 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Jira 11
Other APIs Jira publishes across the network.
This is an independent, third-party profile of Jira Issue Search 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.