Jira APIConnect Jira without building on its API
Jira has a REST API. Self-serve for any developer with an Atlassian account; calls act with the permissions of the authorizing user on a Jira Cloud site. If you're reading the docs because you need Jira to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Jira and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
What the Jira API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (3LO) apps, Forge apps (OAuth 2.0 scopes), Connect apps, or basic auth with email + API token
- Who can get access
- Self-serve for any developer with an Atlassian account; calls act with the permissions of the authorizing user on a Jira Cloud site.
- What it covers
- Issues, projects, JQL search, workflows, users/groups, comments, attachments, fields, and other Jira configuration.
- Limits
- Points-based hourly quota (65,000 points/hour for most apps in the global pool), plus per-second burst limits (100 req/s for GET/POST, 50 for PUT/DELETE) and per-issue write limits (20 writes per 2s, 100 per 30s).
Official docs: developer.atlassian.com. Checked September 2026. Vendors change access terms, so confirm with Jira before you build.
Building on the Jira API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Jira credentials, and manage tokens and refreshes. | Connect your Jira account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Jira task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Jira work off someone's desk, the build is the slow part.
What teams usually want the Jira API for
Email-to-Jira
Caddi reads inbound support email, opens the right Jira issue with priority and labels, and confirms back to the requester.
CRM-issue link
When a CRM record requests work, Caddi opens the matching Jira issue and writes status back to the original record.
Status notifications
On Jira state changes, Caddi notifies stakeholders in Slack or Teams with full context from the upstream record.
Jira API questions
Does Jira have an API?
Yes. Jira has a REST API, authenticated with OAuth 2.0 (3LO) apps, Forge apps (OAuth 2.0 scopes), Connect apps, or basic auth with email + API token. The official documentation is at https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/.
How do I get access to the Jira API?
Self-serve for any developer with an Atlassian account; calls act with the permissions of the authorizing user on a Jira Cloud site.
Does the Jira API have rate limits?
Points-based hourly quota (65,000 points/hour for most apps in the global pool), plus per-second burst limits (100 req/s for GET/POST, 50 for PUT/DELETE) and per-issue write limits (20 writes per 2s, 100 per 30s).
Can I connect Jira to my other tools without writing code against its API?
Yes. With Caddi you show the Jira task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Jira and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Jira with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Jira is reviewed before it runs in production, and every run is logged.
Connect Jira without the build.
Drop your work email and pick a time. We'll show you Caddi running your Jira workflow end to end.