How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Jira Builds API

APIs related to integrating build data with Jira Software.These APIs are available to Atlassian Connect apps. To use these APIs you must have the `jiraBuildInfoProvider` module in your Connect app's descriptor. See https://developer.atlassian.com/cloud/jira/software/modules/build/. They are also related to 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:buildInfoProvider` module in the Forge app's manifest. See https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-software-build-info/.

Jira Builds API is one of 132 APIs that Jira publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Builds. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and an API reference.

This API exposes 4 operations across 3 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1001.0.0.

Requests are made against a single base URL, https://your-domain.atlassian.net.

4 operations 3 paths 1 schemas 2 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1001.0.0
Base URL
https://your-domain.atlassian.net/rest/api/2
Authentication
OAuth 2.0, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Jira Builds API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 46 scopes. It accepts HTTP basic authentication (basicAuth).

  • OAuth2 — OAuth2 scopes for Jira
  • basicAuth — Basic authentication using email and API token

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 DELETE, 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Builds 4

APIs related to integrating build data with Jira Software.

POST
/rest/builds/0.1/bulk
Submit build data
submitBuilds 1 param body → 202400401403413429503default
DELETE
/rest/builds/0.1/bulkByProperties
Delete builds by Property
deleteBuildsByProperty 2 params → 202400401403429503default
GET
/rest/builds/0.1/pipelines/{pipelineId}/builds/{buildNumber}
Get a build by key
getBuildByKey 3 params → 200401403404429503default
DELETE
/rest/builds/0.1/pipelines/{pipelineId}/builds/{buildNumber}
Delete a build by key
deleteBuildByKey 4 params → 202401403429503default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is IssueIdOrKeysAssociation (2 properties). Each schema is shown below with its type and property counts.

IssueIdOrKeysAssociation
object
An association type referencing issues in Jira.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jira-builds-api-openapi.yml Raw ↑

Other APIs Jira publishes across the network.

Jira Cloud Platform REST API v2
Jira Service Management Operations REST API
Jira Align REST API
Jira Customer Service Management REST API
Jira Issue Comments API
Jira Issue Priorities API
Jira Issue Search API
Jira Issue Statuses API
Jira Issue Transitions API
Jira Issue Types API
Jira Issues API
Jira Projects API
Where this information came from

This is an independent, third-party profile of Jira Builds API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.