canonical: https://jentic.com/apis/apple.com

# Apple APIs

Apple's developer APIs cover two distinct integration surfaces that Jentic makes agent-ready with generated, validated OpenAPI specifications. The App Store Connect API exposes 252 operations for iOS, macOS, watchOS, and tvOS app distribution, including app records, TestFlight builds and beta groups, App Store version submissions, in-app purchases, provisioning profiles, and sales and finance reports, authenticated with signed JWT bearer tokens. SiriKit Cloud Media is the server-side contract that music and podcast providers implement so Siri can resolve, play, add, and update affinity for their content across Apple devices. Apple does not publish official OpenAPI specifications for either surface, so the Jentic versions are the structured source agents and developers use.

## For AI agents

Across Apple's developer surfaces an agent can automate iOS and macOS release operations through App Store Connect, driving TestFlight distribution, App Store submissions, in-app purchases, and sales and finance reporting, and can scaffold or test a SiriKit Cloud Media extension that answers Siri voice intents for a media provider. Both surfaces are reached through Jentic-generated OpenAPI specs.

## Scope

Use for: Automating iOS and macOS App Store Connect release operations (TestFlight, submissions, in-app purchases, sales and finance reports) and implementing or testing a SiriKit Cloud Media extension server for Siri voice intents.

Not supported:
- binary build upload
- Google Play releases
- end-user purchases
- catalog browsing
- Siri client behavior
- DRM handling

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| App Store Connect API | developer-tools | 252 | Programmatically manage iOS and macOS app submissions, TestFlight builds, in-app purchases, and Apple sales reports through JWT-authenticated REST endpoints. |
| SiriKit Cloud Media | media | 6 | Server-side contract that media providers implement so Siri can resolve, play, and update affinity for their catalog content. |

## Cross-API use cases

### Voice-Ready Music App Release Pipeline

A streaming music startup ships its iOS app and its Siri integration in one workflow. The agent drives the App Store Connect API to attach a build to a TestFlight beta group and submit an App Store version for review, then scaffolds and contract-tests the SiriKit Cloud Media extension so the released app answers Siri play and add-media intents. Both surfaces come from Jentic-generated specs, so one agent covers store distribution and voice integration.

Example prompt: Submit the current build for App Store review via App Store Connect, then generate SiriKit Cloud Media handler stubs for /intent/playMedia and /intent/addMedia and validate them against the spec

### Media Provider Launch Readiness Check

Before a media provider goes live, the agent verifies both halves of the Apple integration. It reads App Store Connect to confirm the app version is approved and the TestFlight build is valid, and it checks the SiriKit Cloud Media /configuration response so Siri routes the correct media types to the extension. This surfaces mismatches between the shipped app and the voice contract in a single pass.

Example prompt: Check the latest appStoreVersion state via App Store Connect, then confirm the SiriKit Cloud Media /configuration response advertises song, album, and podcast media types

## Why Jentic

- **Setup:** Apple ships no OpenAPI specs and splits developer access across a JWT-signed store API and an unauthenticated Siri contract. Through Jentic you install once, add the App Store Connect API and SiriKit Cloud Media from the Jentic directory, store any credential once, and your agent calls both.
- **Permission scoping:** Because Jentic One is self-hosted, your own rules decide which operations your agent may call on each API, running against a positive allow-list. You can keep App Store Connect read-only for listing apps or downloading sales reports while excluding writes, and restrict SiriKit Cloud Media to only the intent handlers a task needs.
- **Credential handling:** Your App Store Connect signing key, and any shared SiriKit test secret, is stored encrypted by your own Jentic One instance, which signs short-lived JWTs and injects them at execution time. The raw .p8 key never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent, such as 'submit an app for review' or 'handle a Siri play media intent', and Jentic returns the matching operation with its parameter and response schema, so the agent calls the right Apple endpoint without crawling developer.apple.com.

## Related vendors

- **Google APIs** — Android Publisher is the Google Play equivalent of App Store Connect for the other mobile platform
- **Spotify** — Provides catalog and track lookup a SiriKit Cloud Media extension resolves and plays
- **CircleCI** — Runs the iOS builds whose archives feed App Store Connect submissions
- **GitHub** — Handles source tagging and release notes alongside App Store version submissions

## FAQ

### Does Apple publish official OpenAPI specs for these APIs?

No. Apple documents both App Store Connect and SiriKit Cloud Media as prose on developer.apple.com and does not ship OpenAPI specifications. Jentic generates and maintains structured, validated specs for both so agents and developers can call them through consistent tooling.

### Do these two APIs share credentials or an account?

No. App Store Connect uses JWT bearer tokens signed from a private .p8 key tied to your Apple Developer Program account, while SiriKit Cloud Media has no standard security scheme because Apple's Siri service authenticates itself against your hosted extension. You configure each independently.

### Who calls each API?

Your agent or code calls the App Store Connect API to manage app distribution and reporting. SiriKit Cloud Media is the reverse: your service implements the six endpoints and Apple's Siri service calls them, so the spec is used mainly to scaffold an extension server and write contract tests.

### What can an AI agent do across Apple's developer APIs?

An agent can automate the full store side, from TestFlight distribution and App Store submission to in-app purchases and sales report downloads, and it can generate and test a SiriKit Cloud Media extension that answers Siri voice intents. Together these cover shipping an iOS app and making its content available by voice.

### Are these APIs iOS and Apple only?

Yes. App Store Connect manages the iOS, macOS, watchOS, and tvOS app families on the Apple App Store, and SiriKit Cloud Media integrates only with Apple's Siri. For Android releases or Google Assistant voice you would use a different vendor's API.

### Is an Apple Developer Program membership required?

The App Store Connect API is included with an active Apple Developer Program membership and has no per-call charge. SiriKit Cloud Media requires registering your extension relationship in the Apple developer portal, which is also part of program membership.