Guide
App Store Connect API vs Helm
When to call the App Store Connect API directly versus using Helm’s native Mac/iOS apps and helm-asc CLI. Honest fit for teams, agents, and CI.The App Store Connect API is the raw pipe. Helm is a native product built on that pipe. You can use either, and many teams use both. This guide clarifies when raw API access fits, when Helm’s UI and CLI save time, and how to avoid maintaining two competing automation stacks.
Helm is not an Apple product. It authenticates with your API key and focuses on releases, listings, TestFlight, reviews, and related shipping work. It does not replace App Analytics, agreements, or banking on Apple’s site. Compare the broader product story in Helm vs App Store Connect.
What the raw API is for
Use the App Store Connect API directly when you need:
- Custom internal tools none of the shipping UIs cover
- Fine-grained control over pagination, webhooks-adjacent polling, or proprietary data models
- A language or runtime Helm does not wrap the way you need
- One-off migrations that will never become a weekly human workflow
The cost is real: auth, JWT session handling, endpoint discovery, error recovery, and keeping up with Apple’s API changes. You own the UX for every operator who has to run it.
What Helm is for
Use Helm when the job is the weekly shipping loop:
- Prepare versions, What’s New, builds, and submit paths in a native Mac app
- Edit listings, keywords, tags, and screenshots with preview
- Manage TestFlight groups and feedback without ASC tab mazes
- Triage reviews with templates and translation on Mac and iPhone
- Let teammates ship without teaching them REST resources
On Helm Pro, helm-asc adds a CLI and agent-friendly mode that reuses the Mac app’s account setup through an App Group. You get scriptable ASC actions without pasting keys into every agent config.
UI vs CLI vs raw API
| Need | Best fit |
|---|---|
| Visual review of customer-facing metadata | Helm Mac / iOS UI |
| Scripts, agents, repeatable prep | helm-asc (Pro) |
| Deep custom platform / unique data joins | Raw ASC API |
| Binary CI upload pipelines | Fastlane / Transporter / Xcode Cloud (often alongside Helm) |
| Agreements, users, banking, Analytics | App Store Connect web |
A healthy default: humans confirm truth in the UI; agents prepare with helm-asc; bespoke platforms call the API only where Helm does not cover the resource.
When raw API still wins
Keep direct API code when:
- You already run a mature internal release platform with tests and on-call ownership.
- You need endpoints or workflows Helm does not expose yet.
- Compliance requires your own audit layer around every mutation.
- The work is pure data sync into a warehouse (and you accept that Helm is not App Analytics).
Do not rewrite a working internal platform just to say you use Helm. Do adopt Helm for the interactive gaps your platform never polished (reviews inbox, screenshot layout, on-device TestFlight ops).
When Helm (and helm-asc) win
Choose Helm when:
- Indies or small teams spend more time in ASC browser tabs than in Xcode.
- Marketing and support need App Store access without living in JSON.
- You want agents to help with localizations or TestFlight prep under one credential model. See set up helm-asc.
- You already use Fastlane for binaries and need a better day-to-day UI. See use Helm with Fastlane.
A practical hybrid
Many teams land here:
- CI uploads builds (Fastlane, Xcode Cloud, or Transporter)
- helm-asc creates versions, pushes localizations, or attaches metadata in agent workflows
- Helm UI previews the product page, checks the launch list, and submits
- ASC web handles contracts, users, and finance
- Raw API only for the one internal dashboard that joins ASC data with your own billing system
That hybrid avoids forcing every teammate through curl while still leaving escape hatches for engineers.
Safety notes for both paths
- Limit API key roles to the minimum apps and permissions you need
- Prefer dry runs and read-only discovery before mutating production metadata
- Require a human for submit-for-review style actions when agents are involved
- Never treat App Store Connect as a second analytics product inside Helm. Shipping metadata and reviews are the job.
