Jira

Jira Project components API

This resource represents project components. Use it to get, create, update, and delete project components. Also get components for project and get a count of issues by component.

GitHub OpenAPI

Operations 8

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 /rest/api/3/component Find components across several projects · Find components for projects #
Ask an LLM
“Which components exist across a set of projects, including Compass components?”
“Can I search components by name across multiple projects?”
Tell an agent
Find components in projects {projectIdsOrKeys}.
Search components matching {query} across projects {projectIdsOrKeys}.
POST /rest/api/3/component Create a component in a project · Create component #
Ask an LLM
“How do I add a new component to a project?”
“Can I set a component lead and default assignee when creating it?”
Tell an agent
Create a component named {name} in project {project}.
Create component {name} in project {project} led by {leadAccountId} with assignee type {assigneeType}.
DELETE /rest/api/3/component/{id} Delete a component · Delete component #
Ask an LLM
“How do I delete a component from a project?”
“Can I move the component's issues to another component when deleting it?”
Tell an agent destructive · confirm first
Delete component {id}.
Delete component {id} and move its issues to component {moveIssuesTo}.
GET /rest/api/3/component/{id} Get a component's details · Get component #
Ask an LLM
“Who is the lead of a particular component?”
“How do I look up one component by its ID?”
Tell an agent
Get component {id}.
Show the lead and default assignee of component {id}.
PUT /rest/api/3/component/{id} Update a component · Update component #
Ask an LLM
“Can I rename a component or change its lead?”
“How do I remove the lead from a component?”
Tell an agent
Rename component {id} to {name}.
Make {leadAccountId} the lead of component {id}.
GET /rest/api/3/component/{id}/relatedIssueCounts Count issues assigned to a component · Get component issues count #
Ask an LLM
“How many issues are assigned to a component?”
“What's the issue count for a component before I delete it?”
Tell an agent
Count the issues in component {id}.
Tell me how many issues belong to component {id}.
GET /rest/api/3/project/{projectIdOrKey}/component Page through a project's components · Get project components paginated #
Ask an LLM
“Can I page through a project's components and filter them by name?”
“Is it possible to list only Jira or only Compass components in a project?”
Tell an agent
Page through the components of project {projectIdOrKey}, {maxResults} at a time.
Search components in project {projectIdOrKey} matching {query}, ordered by {orderBy}.
GET /rest/api/3/project/{projectIdOrKey}/components List all components in a project at once · Get project components #
Ask an LLM
“How do I get every component of a project in one unpaginated list?”
“What components does my project have?”
Tell an agent
List all components in project {projectIdOrKey} without paging.
Get the full component list of project {projectIdOrKey} from source {componentSource}.

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/
📖
APIReference
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-project-components-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:jira-project-components-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-project-components-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  contact:
    email: ecosystem@atlassian.com
  description: Jira Cloud platform REST API documentation
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  termsOfService: https://developer.atlassian.com/platform/marketplace/atlassian-developer-terms/
  title: Jira Cloud platform REST Project components API
  version: 1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df
servers:
- url: https://your-domain.atlassian.net
tags:


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