myChips Python API Docs | dltHub

Build a myChips-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The Revenue API allows retrieval of performance data for websites and ad units. It supports requests in various programming languages. Essential documentation is available at https://docs.mychips.io/revenue-api. The REST API base URL is https://public-api.myappfree.com/graphql/index.html and All requests require an API key sent in the x-api-key header..

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 pip install "dlt[workspace]" and start loading myChips data in under 10 minutes.


What data can I load from myChips?

Here are some of the endpoints you can load from myChips:

ResourceEndpointMethodData selectorDescription
revenue_metricsgraphql (revenueMetrics query)POST (GraphQL)data.revenueMetrics.itemsReturns revenue metrics grouped by site/adunit with fields like siteId, siteName, adunitId, adunitName, impressions, clicks, revenue, ecpm, arpdau, dau

How do I authenticate with the myChips API?

API uses an API key obtained from the Universal Developer Portal. This key must be included in the HTTP header named x-api-key for every request. GraphQL POSTs also require Content-Type: application/json.

1. Get your credentials

  1. Visit the Universal Developer Portal / dashboard referenced in the docs. 2) Create or select your developer/application. 3) Generate or copy the API key (labelled for public API access). 4) Use that key as the x-api-key header value in API requests.

2. Add them to .dlt/secrets.toml

[sources.mychips_revenue_api_source] api_key = "YOUR_API_KEY_HERE"

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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt 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:

dlt ai toolkit rest-api-pipeline install

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 myChips 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:

python mychips_revenue_api_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline mychips_revenue_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mychips_revenue_api_data The duckdb destination used duckdb:/mychips_revenue_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline mychips_revenue_api_pipeline 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 revenue_metrics and revenue_metrics (GraphQL single endpoint; primary resource is revenueMetrics) from the myChips 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 mychips_revenue_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://public-api.myappfree.com/graphql/index.html", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "revenue_metrics", "endpoint": {"path": "graphql/index.html", "data_selector": "data.revenueMetrics.items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mychips_revenue_api_pipeline", destination="duckdb", dataset_name="mychips_revenue_api_data", ) load_info = pipeline.run(mychips_revenue_api_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("mychips_revenue_api_pipeline").dataset() sessions_df = data.revenue_metrics.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM mychips_revenue_api_data.revenue_metrics LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("mychips_revenue_api_pipeline").dataset() data.revenue_metrics.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 myChips data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for myChips?

Request dlt skills, commands, AGENT.md files, and AI-native context.