asc CLI — App Store Connect CLI

Authentication

Option A — Persistent login (recommended):

bash
1# Single account
2asc auth login \
3  --key-id YOUR_KEY_ID \
4  --issuer-id YOUR_ISSUER_ID \
5  --private-key-path ~/.asc/AuthKey_XXXXXX.p8
6
7# Multiple accounts
8asc auth login --key-id K1 --issuer-id I1 --private-key-path work.p8 --name work
9asc auth login --key-id K2 --issuer-id I2 --private-key-path personal.p8 --name personal
10asc auth use work         # switch active account
11asc auth list             # see all accounts
12asc auth logout           # remove active account
13asc auth logout --name personal  # remove specific account
14asc auth check            # verify active credentials

Credentials are saved to ~/.asc/credentials.json. All asc commands use the active account automatically. See the asc-auth skill for full multi-account details.

Option B — Environment variables:

bash
1export ASC_KEY_ID="YOUR_KEY_ID"
2export ASC_ISSUER_ID="YOUR_ISSUER_ID"
3export ASC_PRIVATE_KEY_PATH="~/.asc/AuthKey_XXXXXX.p8"

Resolution order: active account in ~/.asc/credentials.json → environment variables.

CAEOAS — Follow the Affordances

Every response includes an affordances field with ready-to-run next commands. Always use affordances from prior responses instead of constructing commands from scratch.

json
1{
2  "data": [{
3    "id": "6748760927",
4    "name": "My App",
5    "affordances": {
6      "listVersions": "asc versions list --app-id 6748760927"
7    }
8  }]
9}

Command Reference

See commands.md for full command reference with options and examples. See api_reference.md for the underlying App Store Connect API endpoints and error codes.

Quick reference

Common Workflows

First-time authentication setup

1. asc auth login --key-id <id> --issuer-id <id> --private-key-path ~/.asc/AuthKey_<id>.p8
2. asc auth check   → confirm source: "file", keyID and issuerID shown
3. asc apps list    → no env vars needed from now on

Submit an app for review

1. asc apps list                                    → find app ID
2. asc versions list --app-id <id>                  → find editable iOS version (PREPARE_FOR_SUBMISSION)
   → use affordances.submitForReview if present
3. asc versions submit --version-id <id>

Prerequisite check: submitForReview affordance only appears when state is editable. A 409 error means the version is missing required content (screenshots, build, description). Check App Store Connect UI.

Upload screenshots

1. asc versions list --app-id <id>                  → get version ID
2. asc version-localizations list --version-id <id>         → get localization ID
3. asc screenshot-sets list --localization-id <id>  → get set ID for display type
4. asc screenshots upload --set-id <id> --file ./screenshot.png

Import screenshots from ZIP (screenshot editor workflow)

1. Design screenshots in homepage/editor/index.html → Export ZIP
2. asc screenshots import --version-id <id> --from ./export.zip

Update app name / subtitle

1. asc app-infos list --app-id <id>                          → get app info ID
2. asc app-info-localizations list --app-info-id <id>        → get localization ID
3. asc app-info-localizations update --localization-id <id> --name "New Name" --subtitle "New Subtitle"

Check build availability

asc builds list --app-id <id> --limit 5

Output Flags

bash
1asc apps list                    # compact JSON (default)
2asc apps list --pretty           # pretty-printed JSON
3asc apps list --output table     # table format
4asc apps list --output markdown  # markdown table

Error Handling

When a submission fails with 409, inspect the version in App Store Connect web UI for missing requirements.