Bitrise API

Name: Bitrise API API
Brand: Bitrise API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi CdapiKey119 EndpointsREST

For Agents

Trigger and inspect mobile CI/CD builds on Bitrise, manage signing assets, and download build artifacts. 119 endpoints with Personal Access Token authentication.

Quickstart

Get started with Bitrise API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger a mobile ci build on bitrise"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Bitrise API API.

Trigger a build on a registered app via the apps and builds endpoints

Read build status and logs for a given app slug and build slug

Upload and manage Android keystore files, iOS provisioning profiles, and build certificates

Download build artifacts including IPAs, APKs, and dSYM bundles

GET STARTED

Start building with Bitrise API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Bitrise API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Bitrise API, keeping it validated and agent-ready. Bitrise is a CI/CD platform built specifically for mobile app teams. The v0.1 REST API exposes 119 endpoints covering apps, builds, workflows, generic file storage, Android keystore files, provisioning profiles, build certificates, build artifacts, addon management, archived builds, and webhooks. Authentication uses a Personal Access Token in the Authorization header for user-context calls and an addon auth token for addon-context calls.

Use Cases

Patterns agents use Bitrise API API for, with concrete tasks.

★ On-demand mobile builds from chat

Mobile teams trigger Bitrise builds from a chat command rather than the Bitrise UI. The trigger endpoint accepts a workflow id and an optional branch, and Bitrise returns a build slug that the same chat session can poll for status and artifact URLs. Posting an IPA download link back into the channel takes seconds because the artifact endpoints expose direct download URLs.

Trigger a build on app slug abc123 with workflow 'release', poll the build status until success, and post the IPA artifact URL back to the chat

Signing asset rotation across apps

Mobile platform teams rotate Android keystores and iOS provisioning profiles across many Bitrise apps when certificates expire. The /apps/{app-slug}/android-keystore-files and provisioning profile endpoints accept new uploads and mark them as the active asset, so a single script can iterate every app in the org and replace the expiring credential. The same script reads back the uploaded slug to confirm the rotation succeeded.

For each app in the organisation, upload the new keystore via /apps/{app-slug}/android-keystore-files and confirm the uploaded flag turns true

Build artifact ingestion for release notes

Release engineering teams ingest finished Bitrise build artifacts (IPAs, APKs, dSYMs) into a release notes pipeline that maps a build to a Git commit and a feature list. The build and artifact endpoints return the metadata needed to assemble release notes without manually copying URLs out of the Bitrise UI. A nightly job covers every app slug.

List builds for app slug abc123 in the last 24 hours, fetch their artifacts, and write IPA URLs and commit hashes into the release-notes pipeline

Agent integration via Jentic for mobile CI

An AI agent that needs to run a mobile build calls Jentic with the intent 'trigger a mobile ci build'. Jentic returns the Bitrise builds endpoint with its input schema (app slug, branch, workflow id), and injects the Personal Access Token at execution. The agent never holds the token, so a chat session can spin up a release build without exposing the credential.

Search Jentic for 'trigger a mobile ci build', load the Bitrise builds schema, and execute against the user's app slug and the 'release' workflow

Key Endpoints

119 endpoints — jentic publishes the only available openapi specification for bitrise api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/apps

List the apps the authenticated user can access

POST

/apps/register

GET

/apps/{app-slug}

Read a single app's metadata

GET

/apps/{app-slug}/addons

List addons installed on an app

POST

/apps/{app-slug}/android-keystore-files

Upload a new Android keystore to an app

GET

/apps/{app-slug}/archived-builds

List archived builds for an app

GET

/addons

List available addons

GET

/apps

List the apps the authenticated user can access

POST

/apps/register

GET

/apps/{app-slug}

Read a single app's metadata

GET

/apps/{app-slug}/addons

List addons installed on an app

POST

/apps/{app-slug}/android-keystore-files

Upload a new Android keystore to an app

Why though Jentic?

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

Credential isolation

Bitrise Personal Access Tokens and addon auth tokens are stored encrypted in the Jentic vault. Jentic injects the correct header at execution, so agent prompts and logs never contain the raw token.

Intent-based discovery

Agents search by intent (e.g. 'trigger a mobile ci build' or 'download bitrise artifact') and Jentic returns the matching v0.1 operation with its input and response schema.

Time to first call

Direct Bitrise integration: 1-3 days to map app slugs, build trigger payloads, and artifact URL handling across 119 endpoints. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

CircleCI API

General-purpose CI/CD platform with REST API for triggering and inspecting workflows.

Choose CircleCI when the agent's project is not mobile-specific and benefits from CircleCI's broader build matrix.

Alternative

Buddy

CI/CD platform with REST API and visual pipelines.

Choose Buddy when the agent needs visual pipeline composition and broader language coverage than Bitrise's mobile focus.

Complementary

GitHub API

Source control and Actions surface that commonly triggers Bitrise builds upstream.

Use the GitHub API alongside Bitrise when the agent must correlate a Bitrise build with the originating commit, PR, or status check.

FAQs

Specific to using Bitrise API API through Jentic.

Why is there no official OpenAPI spec for Bitrise API?

Bitrise does not publish a maintained OpenAPI specification (its public Swagger reference exists but drifts from the live API). Jentic generates and maintains this spec so that AI agents and developers can call Bitrise API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Bitrise API use?

User-context calls authenticate with a Personal Access Token passed in the Authorization header. Addon-context calls use a separate Bitrise-Addon-Auth-Token header. Through Jentic the appropriate token is held encrypted in the vault and injected at call time.

Can I trigger a build with the Bitrise API?

Yes. POST against the build trigger endpoint for an app slug with a payload that names a workflow id and a branch. Bitrise returns a build slug you can pass to /apps/{app-slug}/builds/{build-slug} to poll for status and artifact URLs.

What are the rate limits for the Bitrise API?

Bitrise enforces per-token rate limits documented as 60 requests per second sustained with short bursts allowed. A 429 response indicates the limit was hit; retry with exponential backoff. Heavy artifact downloads count against the same quota as control-plane calls.

How do I trigger a Bitrise build through Jentic?

Run pip install jentic, search Jentic for 'trigger a mobile ci build', load the Bitrise build trigger operation, and execute with the app slug, branch, and workflow id. Jentic injects the Personal Access Token automatically.

Can I download IPA and APK artifacts via the API?

Yes. The build artifacts endpoints under /apps/{app-slug}/builds/{build-slug}/artifacts list each artifact and return signed download URLs. Use these URLs to fetch the IPA, APK, or dSYM bundle without going through the Bitrise UI.