Integrate the Jira API.Caddi writes and runs the integration for you.
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.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. 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).
Register an app, store Jira credentials, refresh tokens and code around the rate limits.
Connect your Jira account once. Caddi holds the connection.
The job doesn't stop at Jira.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Jira API only reaches Jira.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
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.
When to build the Jira integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Jira work off someone's desk, the build is the slow part, and Caddi does it for you.
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.
Everything Caddi does with Jira.
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. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
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.