App Store Connect Python API Docs | dltHub
Build a App Store Connect-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
The App Store Connect API is a REST API used to automate tasks within App Store Connect, such as managing apps, builds, and TestFlight resources. The REST API base URL is https://api.appstoreconnect.apple.com and all requests require a Bearer token containing a JWT signed with an ES256 private key.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading App Store Connect data in under 10 minutes.
What data can I load from App Store Connect?
Here are some of the endpoints you can load from App Store Connect:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| apps | v1/apps | GET | data | List apps visible in App Store Connect. |
| builds | v1/builds | GET | data | List builds for all apps. |
| app_infos | v1/appInfos | GET | data | List app information resources. |
| users | v1/users | GET | data | List users associated with the account. |
| apps_beta_groups | v1/apps/{id}/betaGroups | GET | data | List beta groups for a specific app. |
How do I authenticate with the App Store Connect API?
The API uses JSON Web Tokens (JWT) signed with the ES256 algorithm; the resulting string must be provided in the Authorization header as 'Bearer '.
1. Get your credentials
- Sign in to App Store Connect.\n2. Navigate to 'Users and Access' in the main navigation menu.\n3. Select the 'Integrations' tab at the top.\n4. Click 'App Store Connect API' in the left-hand column.\n5. Ensure the 'Team Keys' tab is selected (or choose 'Individual' keys if preferred).\n6. Click the '+' (add) button to generate a new key.\n7. Provide a name for the key and assign it an appropriate role (e.g., 'Developer' or 'Admin').\n8. Click 'Generate'.\n9. Immediately download the private key (a '.p8' file). Note: This is a one-time download; Apple does not store the private key.\n10. Note the 'Key ID' (displayed next to your new key) and the 'Issuer ID' (displayed at the top of the keys list).
2. Add them to .dlt/secrets.toml
[sources.app_store_connect_source] key_id = "your_key_id_here" issuer_id = "your_issuer_id_here" private_key = "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----" vendor_number = "your_vendor_number_if_required"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the App Store Connect API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python app_store_connect_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline app_store_connect_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset app_store_connect_data The duckdb destination used duckdb:/app_store_connect.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads apps and sales_reports from the App Store Connect API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def app_store_connect_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.appstoreconnect.apple.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "apps", "endpoint": {"path": "v1/apps", "data_selector": "data"}}, {"name": "builds", "endpoint": {"path": "v1/builds", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="app_store_connect_pipeline", destination="duckdb", dataset_name="app_store_connect_data", ) load_info = pipeline.run(app_store_connect_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("app_store_connect_pipeline").dataset() sessions_df = data.apps.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM app_store_connect_data.apps LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("app_store_connect_pipeline").dataset() data.apps.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load App Store Connect data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for App Store Connect?
Request dlt skills, commands, AGENT.md files, and AI-native context.