App Store Connect API

Name: App Store Connect API API
Brand: App Store Connect API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer252 EndpointsREST

For Agents

Programmatically manage iOS and macOS app submissions, TestFlight builds, in-app purchases, and Apple sales reports through JWT-authenticated REST endpoints.

Connect the App Store Connect API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the App Store Connect 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.

Install Jentic One Beta (Self-Hosted)

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

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 App Store Connect API API.

Drive App Store version submissions from a build to in-review state via /v1/appStoreVersions

Attach a processed build to one or more TestFlight beta groups

Pull weekly and monthly salesReports and financeReports per vendorNumber

List and respond to customerReviews on an app

GET STARTED

Start building with App Store Connect API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for App Store Connect API, keeping it validated and agent-ready. The App Store Connect API exposes 252 operations covering iOS, macOS, watchOS, and tvOS app distribution: app records, builds, TestFlight beta groups, App Store version submissions, in-app purchases, sales and finance reports, and provisioning profiles. Authentication uses signed JWT bearer tokens generated from a private key issued in App Store Connect. This is the same surface area surfaced under Apple's app-store-connect slug, indexed under an alternate path for discoverability.

Use Cases

Patterns agents use App Store Connect API API for, with concrete tasks.

★ Continuous TestFlight Delivery

Wire CI builds into TestFlight without touching App Store Connect's web UI. After Transporter uploads a build, this API lets a release script poll /v1/builds for processingState VALID, attach the build to internal and external beta groups, manage tester invitations, and read crash and screenshot feedback. The full pipeline from green CI to testers' devices runs in under five minutes.

Poll /v1/builds for app id 1234567 until processingState=VALID, then create a betaBuildLocalization and add the build to beta group 'External QA'

Programmatic App Store Submission

Replace the manual App Store Connect submission form with code. Create a new appStoreVersion, attach appStoreVersionLocalizations for each language with description, keywords, and screenshots, link a build, fill in appStoreReviewDetails, and submit. The agent can read state transitions through reviewSubmissions and surface review rejections back to the team.

Create an appStoreVersion 2.4.1 for platform IOS with build id ABC, upload English-US screenshots, and submit for review

Sales and Finance Data Sync

Pull daily, weekly, monthly, or yearly sales and finance reports for a vendor account into an internal warehouse or BI tool. The /v1/salesReports endpoint returns gzipped TSV per reportType, frequency, and date. Combined with /v1/financeReports this powers automated revenue dashboards and royalty splits without scraping App Store Connect.

Download SALES weekly report for vendor 12345678, report date 2026-06-02, parse the gzip TSV, and total proceeds in USD

AI Agent Release Operations

An AI agent uses Jentic to monitor App Store Connect, draft replies to negative customer reviews, and orchestrate cross-platform release rollouts. Jentic isolates the App Store Connect signing key in the MAXsystem vault and hands the agent short-lived bearer tokens, so the .p8 file never enters the agent's context window.

Search Jentic for 'list customer reviews', call GET /v1/customerReviews with sort=-createdDate, and draft responses for any review with rating <= 2

Key Endpoints

252 endpoints — jentic publishes the only available openapi specification for app store connect api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/apps

List apps in the App Store Connect account

POST

/v1/appStoreVersions

Create a new App Store version

GET

/v1/builds

List uploaded builds and processing state

POST

/v1/betaGroups

Create a TestFlight tester group

GET

/v1/salesReports

Download a sales report file

GET

/v1/customerReviews

List App Store customer reviews

POST

/v1/profiles

Generate a provisioning profile

GET

/v1/apps

List apps in the App Store Connect account

POST

/v1/appStoreVersions

Create a new App Store version

GET

/v1/builds

List uploaded builds and processing state

POST

/v1/betaGroups

Create a TestFlight tester group

GET

/v1/salesReports

Download a sales report file

Why though Jentic?

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

Credential isolation

The signing .p8 key is the long-lived secret for App Store Connect. Jentic stores it encrypted in the MAXsystem vault and signs short-lived JWTs on the agent's behalf, so the raw key never leaves Jentic infrastructure.

Intent-based discovery

Agents search Jentic with intents like 'submit app for review' or 'list TestFlight builds' and Jentic returns the matching App Store Connect operation with its parameter and response schemas, removing the need to crawl developer.apple.com.

Time to first call

Direct App Store Connect integration: 2-4 days to wire JWT signing, key rotation, and the JSON:API relationship model. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Google Play Android Publisher API

Equivalent surface for managing Android releases on Google Play

Pick Android Publisher when the target platform is Google Play; App Store Connect is iOS-family only.

Complementary

GitHub REST API

Tag releases and update changelogs alongside App Store submissions

Use GitHub for source-side actions (tagging, release notes) and App Store Connect for the store-side submission.

Complementary

CircleCI API

Run iOS builds whose archives feed App Store Connect

Use CircleCI to produce the .ipa; use App Store Connect to push it through TestFlight and the App Store.

FAQs

Specific to using App Store Connect API API through Jentic.

Why is there no official OpenAPI spec for App Store Connect API?

Apple does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call App Store Connect 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 App Store Connect API use?

It uses JWT bearer tokens. You generate a private .p8 key in App Store Connect, sign a JWT with ES256 using your key id and issuer id, and send Authorization: Bearer {jwt}. Tokens are valid for at most 20 minutes. Through Jentic the .p8 lives in the vault and the agent receives only short-lived scoped tokens.

Can I submit an app for review with the App Store Connect API?

Yes. Create an appStoreVersion with POST /v1/appStoreVersions, attach localizations and screenshots, link a build, and submit through reviewSubmissions. Note that build binary upload itself is handled by Transporter or Xcode — the REST API works on the metadata and submission lifecycle.

What are the rate limits for the App Store Connect API?

Apple enforces hourly per-team quotas that vary by endpoint, with separate limits for sales report downloads. When you exceed them the API returns 429 with a Retry-After header. Caching with ETags and conditional GETs is the recommended way to stay under the limit.

How do I attach a build to a TestFlight group through Jentic?

Run pip install jentic, search 'attach build to testflight group', load the betaGroupBuilds operation under POST /v1/betaGroups/{id}/relationships/builds, and execute it with the betaGroup id and the build id. Jentic handles JWT signing and token rotation.

Is the App Store Connect API free?

Access is included with an active Apple Developer Program membership ($99/year for individuals and organizations, $299/year for the Enterprise Program). There is no per-call charge for the API itself.