Atlassian The Jira Cloud platform REST API

Name: The Jira Cloud platform REST API
Brand: The Jira Cloud platform REST API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsProject Managementoauth2, basic588 EndpointsREST

For Agents

Install Jentic One Beta

Connect the The Jira Cloud platform REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the The Jira Cloud platform REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with The Jira Cloud platform REST API.

Create issues with custom field values, components, fix versions, and sprint assignments in a single call

Transition issues through workflow states with required field validation and screen configuration

Execute JQL queries to search and filter issues across projects by status, assignee, label, and date

GET STARTED

Start building with The Jira Cloud platform REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use The Jira Cloud platform REST API for, with concrete tasks.

★ AI Agent Issue Triage and Routing

AI agents use the Jira API through Jentic to automate issue triage - reading new issues, analyzing priority and component, then assigning to appropriate teams with correct labels and sprint placement. An agent searches Jentic for 'create a jira issue', receives the schema for POST /rest/api/3/issue, and can also execute JQL searches to check for duplicates before creating. The entire triage workflow from detection to assignment completes in seconds.

Search for issues created in the last hour with no assignee in the PLATFORM project, analyze their summary and description, then assign each to the appropriate team lead based on component and set priority

Sprint Planning and Backlog Management

Automate sprint planning by querying backlog items, analyzing story point estimates, and moving issues into sprints based on team capacity and priority. The API provides board configuration, sprint details, and issue ranking to support automated capacity planning. Agents can balance workload across team members by reading current sprint assignments and redistribution.

Get the backlog for board 42, filter issues by priority P1 and P2 with story points estimated, then move the top 20 points worth of issues into the next sprint

Workflow Automation and Status Transitions

Programmatically transition issues through custom workflow states, respecting validators and conditions. The API exposes available transitions per issue with required fields, enabling agents to complete transitions without manual intervention. Useful for automated deployment pipelines that move issues to Done when code ships to production.

Find all issues in the DEPLOY project with status 'Ready for Release', transition each to 'Released' with the resolution field set to 'Done' and a comment noting the release version

Cross-Project Reporting and Analytics

Execute JQL queries spanning multiple projects to generate reports on velocity, cycle time, and blocker patterns. The API supports complex JQL with functions like updatedDate, components, and custom field comparisons. Agents build dashboards by aggregating issue counts by status, calculating time-in-status metrics, and identifying bottleneck workflows.

Run a JQL query for 'project in (PLATFORM, MOBILE, WEB) AND status changed to Done AFTER -7d' and calculate the average cycle time from In Progress to Done

Key Endpoints

588 endpoints — track issues, plan sprints, configure workflows, and query project data across jira cloud instances through 588 rest endpoints.

METHOD

PATH

DESCRIPTION

POST

/rest/api/3/issue

Create an issue

GET

/rest/api/3/search

Search issues using JQL

POST

/rest/api/3/issue/{issueIdOrKey}/transitions

Transition an issue to a new status

GET

/rest/api/3/issue/{issueIdOrKey}

Get issue details

PUT

/rest/api/3/issue/{issueIdOrKey}

Edit an issue

GET

/rest/api/3/field

List all fields

POST

/rest/api/3/issue/{issueIdOrKey}/comment

Add a comment to an issue

GET

/rest/api/3/project

List all projects

POST

/rest/api/3/issue

Create an issue

GET

/rest/api/3/search

Search issues using JQL

POST

/rest/api/3/issue/{issueIdOrKey}/transitions

Transition an issue to a new status

GET

/rest/api/3/issue/{issueIdOrKey}

Get issue details

PUT

/rest/api/3/issue/{issueIdOrKey}

Edit an issue

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Jira OAuth token or API token is stored once, encrypted, by your own Jentic One instance and injected with the tenant base URL at execution time. Raw credentials never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Jira issue' or 'transition issue status', and Jentic returns the matching Jira operation with its request schema including required custom fields so the agent calls the right endpoint without navigating the full reference.

Time to first call

FAQs

Specific to using The Jira Cloud platform REST API through Jentic.

What authentication does the Jira Cloud REST API use?

Jira Cloud supports OAuth 2.0 (3-legged) for user-context operations and basic authentication with email plus API token for server-to-server automation. OAuth 2.0 uses the authorization_code grant with scopes like read:jira-work, write:jira-work, and manage:jira-configuration. Through Jentic, credentials are stored encrypted in your Jentic One instance and injected automatically - agents never handle raw tokens or API keys.

How do I create a Jira issue through the API via Jentic?

Search Jentic for 'create a jira issue', load the operation schema for POST /rest/api/3/issue, and execute with project key, issuetype, summary, and any required custom fields. Jentic injects authentication and maps the domain-specific base URL automatically. The response returns the issue key (e.g., PROJ-123) and self URL.

What are the rate limits for the Jira Cloud REST API?

Jira Cloud enforces rate limits based on concurrent requests per user/app (typically 10 concurrent and 500 requests per 10 seconds). The API returns 429 Too Many Requests with a Retry-After header when limits are exceeded. Bulk operations like issue search have pagination limits of 100 results per page by default, configurable up to 1000.

Can I transition issues through workflow states via the Jira API?

Yes. First GET /rest/api/3/issue/{issueIdOrKey}/transitions to list available transitions for the issue's current state. Then POST to the same endpoint with the transition ID and any required fields (like resolution). Each transition may have validators that require specific field values - the GET response includes the required fields for each transition.

How do I search for issues using JQL through the Jira API?

Use GET /rest/api/3/search with a jql query parameter. For example: jql=project=PROJ AND status='In Progress' AND assignee=currentUser(). The response includes issue keys, fields, and pagination metadata. You can specify which fields to return using the fields parameter to reduce response size.

Is the Jira Cloud REST API free to use?

API access is included with all Jira Cloud plans including Free (up to 10 users). The Free plan supports up to 10 users with basic API access. Standard, Premium, and Enterprise plans offer higher rate limits and advanced features like advanced roadmaps and asset management. There is no separate API usage fee.

Can I limit what my agent is allowed to do with the Jira Cloud REST API?

Yes. Because you run Jentic One yourself, you decide which Jira operations your agent may call, so it can read and comment on issues without being able to transition or edit them unless you add those operations. Jira puts the issue id or key in the URL path (/rest/api/3/issue/{issueIdOrKey}), so your own rules can pin the agent to reads and comments on a single issue. Editing an issue or moving it through a workflow with POST /rest/api/3/issue/{issueIdOrKey}/transitions stays out of scope until you grant it.

Atlassian The Jira Cloud platform REST API

Connect the The Jira Cloud platform REST API to your agent

Capabilities

Start building with The Jira Cloud platform REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs