For Agents
Manage iOS app submissions, TestFlight beta groups, in-app purchases, and sales reports on the Apple App Store. Authenticates with JWT bearer tokens.
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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 instanceJentic 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.
What an agent can do with App Store Connect API API.
Submit a new app version for review and track its review status through appStoreVersions
Invite testers to a TestFlight beta group and assign builds to that group
Pull weekly sales and financial reports for a vendor account through salesReports and financeReports
Manage in-app purchase products, pricing tiers, and review screenshots per locale
GET STARTED
Use for: I need to upload a new build to TestFlight and assign it to my external testers, Submit a new version of my iOS app for App Store review, Retrieve the latest weekly sales report for my vendor account, List all customer reviews left on my app in the last 30 days
Not supported: Does not handle binary upload (use Transporter or Xcode), Android Play Store releases, or end-user purchase processing — use for iOS, macOS, watchOS, and tvOS App Store metadata, TestFlight, and reporting only.
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 automates iOS, macOS, watchOS, and tvOS app distribution on Apple's App Store, covering app metadata, builds uploaded from Xcode, beta testing through TestFlight, in-app purchases, sales and finance reports, and provisioning profiles. Authentication uses signed JWT bearer tokens generated from an App Store Connect API key. The spec covers 252 operations across app records, builds, beta groups, customer reviews, pre-release versions, and pricing.
Register devices, generate signing certificates, and create provisioning profiles for development and distribution
Read customer reviews left on an app and respond through customerReviewResponses
Update App Store metadata localizations including descriptions, keywords, and screenshots per territory
Patterns agents use App Store Connect API API for, with concrete tasks.
★ Automated TestFlight Beta Distribution
Push every successful CI build to TestFlight and route it to the right beta tester group without manual upload. Use the builds and betaGroups endpoints to attach a processed build to internal or external groups, manage tester invitations, and read crash and feedback reports. Replaces hand-managed TestFlight uploads from Xcode with a scripted release pipeline that runs in minutes.
Find the latest build for app id 1234567 with processingState VALID and assign it to beta group 'External QA'
App Store Submission Pipeline
Create a new appStoreVersion, attach localized metadata and screenshots, link a build, and submit for review without using App Store Connect's web UI. The API exposes appStoreVersionLocalizations, appScreenshots, and appStoreReviewDetails so a release manager can prepare a fully reviewed submission from a Git-tracked manifest. Each App Store version transitions through reviewable states the agent can poll.
Create an appStoreVersion of platform IOS with version 2.4.0, attach build id ABC, upload English screenshots, and submit for review
Sales and Royalty Reporting
Pull daily, weekly, monthly, or yearly sales reports and finance reports for a vendor number, then load them into a finance system or BI warehouse. The salesReports endpoint returns gzipped TSV files keyed by report subtype, frequency, and date. Use this to track unit downloads, in-app purchase revenue, and territory-level performance without scraping App Store Connect.
Download the SALES weekly report for vendor number 12345678 for the report date 2026-06-02 and parse total units sold
AI Agent App Release Coordinator
An AI agent uses Jentic to coordinate release tasks across App Store Connect, monitoring build processing, ranking pending customer reviews by sentiment, and drafting reply text for the highest-priority reviews. Jentic vaults the JWT signing key and the agent only sees scoped tokens, so the App Store Connect API key never enters the agent's context.
Search Jentic for 'submit an iOS app for review', load the App Store Connect operation, and create an appStoreVersion submission for build id ABC
252 endpoints — jentic publishes the only available openapi specification for app store connect api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v1/apps
List all apps in your App Store Connect account
/v1/appStoreVersions
Create a new App Store version for submission
/v1/builds
List uploaded builds and their processing state
/v1/betaGroups
Create a TestFlight beta tester group
/v1/salesReports
Download sales and download report files
/v1/customerReviews
List customer reviews left on an app
/v1/profiles
Create a provisioning profile for signing
/v1/apps
List all apps in your App Store Connect account
/v1/appStoreVersions
Create a new App Store version for submission
/v1/builds
List uploaded builds and their processing state
/v1/betaGroups
Create a TestFlight beta tester group
/v1/salesReports
Download sales and download report files
Three things that make agents converge on Jentic-routed access.
Credential isolation
App Store Connect requires a private signing key that must never leak. Jentic stores the key encrypted in the MAXsystem vault and signs short-lived JWTs server-side; the agent only receives a scoped bearer token, never the raw .p8 file.
Intent-based discovery
Agents search Jentic by intent (e.g. 'submit an iOS app for review' or 'invite a TestFlight tester') and Jentic returns the matching App Store Connect operation, its parameters, and its response shape so the agent can call it without browsing Apple's reference docs.
Time to first call
Direct App Store Connect integration: 2-4 days to handle JWT signing, key rotation, and the relationship-based JSON:API response format. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Google Play Android Publisher API
Google's equivalent for managing Android app releases on Google Play
Choose Android Publisher when releasing on Google Play; the App Store Connect API is iOS, macOS, watchOS, and tvOS only.
GitHub REST API
Often paired in mobile release pipelines to tag commits and update release notes alongside App Store submissions
Use GitHub when the agent also needs to read commit messages, draft release notes, or open PRs as part of the iOS release flow.
CircleCI API
Drive CI builds whose artefacts are then uploaded to App Store Connect
Use CircleCI to trigger and monitor iOS builds; use App Store Connect to push the resulting build into TestFlight and the App Store.
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?
The App Store Connect API uses signed JWT bearer tokens. You generate a private key from App Store Connect, sign a JWT with the ES256 algorithm using your key id and issuer id, and pass it as Authorization: Bearer {jwt}. Tokens expire within 20 minutes and must be regenerated. Through Jentic the signing key is stored in the vault and the agent receives short-lived scoped credentials only.
Can I upload a new TestFlight build with the App Store Connect API?
Builds themselves are uploaded through the Transporter command-line tool or Xcode, not the REST API. Once a build is uploaded and processed, you can use POST /v1/betaGroups and the betaGroupBuilds relationships to attach a build to a tester group, manage testers via /v1/betaTesters, and track processingState through /v1/builds.
What are the rate limits for the App Store Connect API?
Apple enforces an hourly request quota per team that varies by endpoint. Sales and finance report downloads are rate-limited separately. Responses include the Retry-After header when limits are hit. Use ETags and conditional requests to avoid burning quota on unchanged resources.
How do I download a weekly sales report through Jentic?
Run pip install jentic, search for 'download app store sales report' through the Jentic SDK, load the GET /v1/salesReports operation, and execute it with filter[frequency]=WEEKLY, filter[reportType]=SALES, filter[reportSubType]=SUMMARY, and filter[vendorNumber] set to your vendor id. The response is a gzipped TSV file.
Is the App Store Connect API free to use?
Yes. The API is free for any active Apple Developer Program member. You only need to enroll in the Apple Developer Program ($99/year) to access the API and create the API keys used to sign JWT tokens.
/v1/customerReviews
List customer reviews left on an app
/v1/profiles
Create a provisioning profile for signing