Jira

Atlassian Jira Issue Search API

Search issues using JQL.

GitHub OpenAPI

Operations 9

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /search Search issues with JQL via /search GET · Jira Search for Issues Using Jql (get) #
Ask an LLM
“Can I run a JQL search as a GET on the unversioned /search path?”
“Which issues match a short JQL query like open bugs in one project?”
Tell an agent
Search the unversioned /search path with GET for issues matching {jql}.
Run JQL {jql} as a GET on /search and return only fields {fields}.
POST /search Search issues with JQL via /search POST · Jira Search for Issues Using Jql (post) #
Ask an LLM
“What if my JQL is too long for a query string on the unversioned /search path?”
“Can I post a large JQL expression to /search in the request body?”
Tell an agent
POST JQL {jql} in the body to the unversioned /search path.
Send long JQL {jql} to /search by POST, {maxResults} results per page.
GET /rest/api/3/issue/picker Suggest issues for autocomplete · Get issue picker suggestions #
Ask an LLM
“How can I build issue autocomplete as a user types a word?”
“Can I get issue suggestions from both history and the current search?”
Tell an agent
Suggest issues matching the text {query}.
Give autocomplete suggestions for {query} within project {currentProjectId}.
POST /rest/api/3/jql/match Check which issues match JQL queries · Check issues against JQL #
Ask an LLM
“Can I test whether specific issues would be returned by a JQL query?”
“Is there a way to check several issue IDs against several JQL filters at once?”
Tell an agent
Check whether issues {issueIds} match JQL {jqls}.
Tell me which of issues {issueIds} each of these queries {jqls} would return.
GET /rest/api/3/search Search issues with the retiring JQL GET · Currently being removed. Search for issues using JQL (GET) #
Ask an LLM
“Is the old /rest/api/3/search GET endpoint still usable while it's being removed?”
“Can the legacy v3 search GET fail fast when fields can't be loaded?”
Tell an agent
Search issues matching {jql} with the legacy v3 search GET that is being removed.
Run {jql} on the retiring /rest/api/3/search GET starting at result {startAt}.
POST /rest/api/3/search Search issues with the retiring JQL POST · Currently being removed. Search for issues using JQL (POST) #
Ask an LLM
“Does the legacy v3 search POST endpoint still take startAt offsets?”
“What replaces the /rest/api/3/search POST that's being removed?”
Tell an agent
POST {jql} to the retiring /rest/api/3/search endpoint.
Use the legacy v3 search POST to fetch {maxResults} issues matching {jql}.
POST /rest/api/3/search/approximate-count Estimate how many issues match JQL · Count issues using JQL #
Ask an LLM
“Roughly how many issues match a bounded JQL query?”
“Can I get an issue count without fetching the issues themselves?”
Tell an agent
Estimate how many issues match {jql}.
Give me an approximate count of issues for query {jql}.
GET /rest/api/3/search/jql Search issues with enhanced JQL GET · Search for issues using JQL enhanced search (GET) #
Ask an LLM
“Which search endpoint uses nextPageToken paging and can include archived projects?”
“Can I get read-after-write consistent JQL results by reconciling recently edited issues?”
Tell an agent
Search issues matching {jql} with the enhanced JQL search GET.
Fetch the next page of enhanced search results for {jql} using token {nextPageToken}.
POST /rest/api/3/search/jql Search issues with enhanced JQL POST · Search for issues using JQL enhanced search (POST) #
Ask an LLM
“Can I send an enhanced token-paged JQL search in a POST body?”
“Is there a POST version of the new JQL search that reconciles specific issue IDs?”
Tell an agent
POST {jql} to the enhanced JQL search, returning fields {fields}.
Run enhanced search by POST for {jql}, reconciling issues {reconcileIssues}.

Documentation

📖
Documentation
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/
📖
Authentication
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#authentication
📖
Documentation
https://developer.atlassian.com/cloud/jira/software/rest/intro/
📖
Documentation
https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-issue-search-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/jira:atlassian-jira-issue-search-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

jira-issue-search-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Jira Issue Search API
  x-refined-note:
  - x-atlassian-api-version differs across the merged source definitions and was not carried
  version: '1.0'
  description: 'Operations tagged Issue Search across 2 of this provider''s published API definitions: jira-cloud-platform-rest-api-openapi.yml, jira-platform-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://{domain}.atlassian.net/rest/api/3
  description: Jira Cloud instance
  variables:
    domain:
      description: Your Jira Cloud site subdomain (e.g., your-company).
      default: your-domain
- url: https://your-domain.atlassian.net
tags:


# --- truncated at 32 KB (135 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-issue-search-api-openapi.yml