Expo Python API Docs | dltHub
Build a Expo-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Expo Modules API is a native modules API for writing Swift and Kotlin to add native capabilities to Expo apps; it is not a REST HTTP API. The REST API base URL is `` and .
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 Expo data in under 10 minutes.
What data can I load from Expo?
Here are some of the endpoints you can load from Expo:
| There are no public GET/HTTP endpoints for the Expo Modules API. The Modules API exposes native functions to JavaScript/TypeScript; it does not return JSON over HTTP. (No endpoints to list.) |
|---|
How do I authenticate with the Expo API?
1. Get your credentials
Expo provides no REST credentials because the Modules API is used inside the app; there are no dashboard steps to obtain HTTP API credentials.
2. Add them to .dlt/secrets.toml
[sources.expo_module_api_source]
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 Expo 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 expo_module_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline expo_module_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset expo_module_api_data The duckdb destination used duckdb:/expo_module_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline expo_module_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 from the Expo 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 expo_module_api_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "", "auth": { "type": "", "": , }, }, "resources": [ ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="expo_module_api_pipeline", destination="duckdb", dataset_name="expo_module_api_data", ) load_info = pipeline.run(expo_module_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("expo_module_api_pipeline").dataset() sessions_df = data..df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM expo_module_api_data. LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("expo_module_api_pipeline").dataset() data..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 Expo 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.
Troubleshooting
Module Not Found Errors
When using requireNativeModule, ensure the module is correctly linked and built into your native project. Check your app.json or app.config.js for proper configuration and ensure the native code is compiled for the target platform.
Platform Differences
Native modules often have platform-specific implementations (Swift for iOS, Kotlin for Android). Ensure your module handles differences between iOS and Android correctly, or provides appropriate fallbacks. Test thoroughly on both platforms.
Building and Uploading Native Code
Issues can arise during the build process of native modules or when uploading to app stores. Verify your Xcode and Android Studio configurations, ensure all dependencies are met, and follow Expo's guidelines for custom native code builds and submissions.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Expo?
Request dlt skills, commands, AGENT.md files, and AI-native context.