Jira Development Information API

APIs related to integrating development information (commits, branches and pull requests) with Jira. These APIs are available to Atlassian Connect apps and on-premise integrations using OAuth. Connect apps using these APIs must have the `jiraDevelopmentTool` module in the Connect app descriptor. See https://developer.atlassian.com/cloud/jira/software/modules/development-tool/. For more details on integrating Jira Software Cloud with on-premises tools using OAuth 2.0 credentials, see https://developer.atlassian.com/cloud/jira/software/integrate-jsw-cloud-with-onpremises-tools/. These APIs are available to Forge apps with the `devops:developmentInfoProvider` module in the Forge app's manifest. See https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-software-development-info/.

Operations 6

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

POST /rest/devinfo/0.10/bulk Send commits, branches and pull requests to Jira · Store development information #
Ask an LLM
“How do I push repository commits, branches and pull requests into Jira so they show on issues?”
“Can I stop smart commits from transitioning issues when I send dev data?”
Tell an agent
Store development information for repositories {repositories}.
Send repositories {repositories} to Jira without firing issue transitions: preventTransitions {preventTransitions}.
GET /rest/devinfo/0.10/repository/{repositoryId} Get a repository's stored development data · Get repository #
Ask an LLM
“What development data does Jira currently hold for one of my repositories?”
“How many recent commits and branches come back with a repository lookup?”
Tell an agent
Get the stored repository {repositoryId} and its dev entities.
Show what Jira has stored for repository {repositoryId}.
DELETE /rest/devinfo/0.10/repository/{repositoryId} Delete a repository's development data · Delete repository #
Ask an LLM
“How do I remove a repository and all of its dev data from Jira?”
“Is deleting a repository's dev information immediate or asynchronous?”
Tell an agent destructive · confirm first
Delete repository {repositoryId} and all its development information.
Remove repository {repositoryId} data older than sequence {_updateSequenceId}.
DELETE /rest/devinfo/0.10/bulkByProperties Delete dev data matching tagged properties · Delete development information by properties #
Ask an LLM
“Can I wipe all repositories tagged with a certain account or project property?”
“When deleting development data by properties, are the properties combined as AND?”
Tell an agent destructive · confirm first
Delete all development information whose repositories carry every one of the given properties.
Bulk remove dev data by properties, only entries with sequence below {_updateSequenceId}.
GET /rest/devinfo/0.10/existsByProperties Check whether dev data exists for properties · Check if data exists for the supplied properties #
Ask an LLM
“Is there any repository data in Jira tagged with a given set of properties?”
“Can I confirm a property-based deletion of dev data has finished?”
Tell an agent
Check if any development data exists for the properties I supply.
Check whether dev data tagged with these properties exists at or below sequence {_updateSequenceId}.
DELETE /rest/devinfo/0.10/repository/{repositoryId}/{entityType}/{entityId} Delete one commit, branch or pull request · Delete development information entity #
Ask an LLM
“How do I remove a single pull request or branch from Jira's dev panel?”
“Can I delete one development entity without deleting the whole repository?”
Tell an agent destructive · confirm first
Delete {entityType} {entityId} from repository {repositoryId}.
Remove only the {entityType} with ID {entityId} in repository {repositoryId} from Jira.

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-development-information-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.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

jira-development-information-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  contact:
    url: https://getsupport.atlassian.com
  description: Jira Software Cloud REST API documentation
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  termsOfService: http://atlassian.com/terms/
  title: Jira Software Cloud Development Information API
  version: 1001.0.0
servers:
- url: https://your-domain.atlassian.net
tags:


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