Load App Store Connect data to DuckDB

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. Everything needed to build a working App Store Connect → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your App Store Connect to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from App Store Connect to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the App Store Connect API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

App Store Connect API at a glance

These values come from the App Store Connect API reference — the authoritative source if anything here looks out of date.

---

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

1. 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

Copy
[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 file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What App Store Connect data can I load into DuckDB?

These are the App Store Connect endpoints dlt can load into DuckDB:

---

How do I load only new App Store Connect records?

App Store Connect exposes links.next on v1/apps, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "apps", "endpoint": {
    "path": "v1/apps",
    "data_selector": "data",
    "incremental": {"cursor_path": "links.next", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated App Store Connect pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading apps and sales_reports from the App Store Connect API into DuckDB:

Copy
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 load_app_store_connect_to_duckdb() -> 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)


if __name__ == "__main__":
    load_app_store_connect_to_duckdb()

Run it with python app_store_connect_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query App Store Connect data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("app_store_connect_pipeline").dataset()
df = data.apps.df()
print(df.head())

SQL:

Copy
SELECT * FROM app_store_connect_data.apps LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the App Store Connect to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw App Store Connect loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load App Store Connect data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack