The API Report CardAPI Index
Atlassian Jira

Atlassian Jira API

Project Management / Issue Tracking / Agile Software Development · atlassian.com

Jira Cloud has a comprehensive self-serve REST API (v3) on every tier including Free, with API tokens, OAuth 2.0, Connect, and Forge as auth paths. The search migration to nextPageToken broke parallel pagination, and points-based hourly rate limits land for apps in March 2026.

Last verified: July 2026Software & Data Tools
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODJira Cloud REST API v3 documented at developer.atlassian.com, with JQL search exposed as a first-class endpoint.
AccessGOODSelf-serve on every tier including Free: user API tokens need no approval; Forge and Connect open the app platform.
CoverageGOODIssues, projects, boards, sprints, workflows, users, permissions, and audit records, with bulk issue endpoints.
AuthGOODChoice of user API tokens, OAuth 2.0 (3LO) with scopes, Connect JWT, or Forge scoped permissions.
Docs & DXGOODExtensive reference docs, first-class webhooks, and a marketplace of 5,000+ apps built on the same APIs.
StabilityGOODv2 stays supported through deprecation windows; points-based hourly rate limits arrive for apps in March 2026.
MORE FROM THE REPORT CARD
Supergood: Atlassian Jira shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Atlassian Jira scores A on the API Report Card. Jira Cloud has a comprehensive self-serve REST API (v3) on every tier including Free, with API tokens, OAuth 2.0, Connect, and Forge as auth paths. The search migration to nextPageToken broke parallel pagination, and points-based hourly rate limits land for apps in March 2026.

Tried to integrate with Atlassian Jira?
SOURCES
New /rest/api/3/search/jql endpoint uses opaque nextPageToken instead of startAt, eliminating random page access and parallel pagination, fetches are now strictly sequential and dramatically slower community.developer.atlassian.com
Community reports that pagination on the new search/jql endpoint is broken, isLast never returns true, nextPageToken chains endlessly, and the same first page is returned repeatedly community.atlassian.com
New search/jql endpoint dropped the totalIssues field, breaking any consumer that paginated based on total count or showed progress to users community.developer.atlassian.com
Points-based hourly rate limits enforced March 2, 2026 for Forge, Connect, and OAuth 2.0 (3LO) apps, Tier 1 global pool is 65,000 points/hour shared across all tenants, with per-tenant quotas requiring Atlassian review community.developer.atlassian.com
Per-endpoint burst limits (100 req/s GET/POST, 50 req/s PUT/DELETE) throttle large bulk sync workloads developer.atlassian.com
Per-issue write throttling restricts how frequently a single issue can be modified, breaking high-frequency bidirectional sync use cases developer.atlassian.com
Jira Cloud now strictly enforces valid JQL syntax, queries with previously-tolerated syntax return zero results instead of partial matches, silently breaking existing dashboards and integrations docs.adaptavist.com
Python pycontribs/jira and other major community SDKs broke on the v2/v3 search deprecation, open issues remain on GitHub github.com
Bulk-fetch performance is poor: pulling 10k issues in 100-issue pages takes 100 sequential requests with no random access reintech.io
API token-based traffic remains governed only by burst limits (not points), but Atlassian has signaled this asymmetry is temporary and apps should migrate to OAuth/Forge/Connect atlassian.com
Interface is slow, overconfigured, and bloated, teams switching to Linear cite Jira's UI sluggishness and ceremony overhead as the primary trigger cotera.co
Per-user pricing scales painfully; Standard is $7.91/user/month, Premium $14.54/user/month, and Enterprise requires annual contracts with custom pricing tech.co
Free tier capped at 10 users, Standard/Premium capped at 300 users on monthly billing, forcing Enterprise contracts at scale atlassian.com
Workflow customization is powerful but configuration debt accumulates, large Jira instances become unmaintainable without a dedicated admin atono.io
Cross-project reporting, plans, and roadmaps require Premium tier, teams on Standard hit feature walls quickly atlassian.com
JQL is powerful but the learning curve is steep; non-engineers struggle to build meaningful saved filters community.atlassian.com
Atlassian Marketplace apps that fill core gaps add significant per-user costs on top of Jira licensing ones.com
Server / Data Center → Cloud migration has been painful for enterprises; feature parity gaps, scripting differences (ScriptRunner), and app-compatibility issues persist community.atlassian.com
Engineering-team UX complaints continue to drive churn to Linear and Shortcut, particularly at 20-80 engineer teams cotera.co