ADS-B Exchange Python API Docs | dltHub
Build a ADS-B Exchange-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
ADS-B Exchange offers a REST API for accessing flight data; commercial use requires a license; free access is available for personal, non-profit research or education. The REST API base URL is https://adsbexchange.com/api and All requests require an api-auth header with your API UUID (or RapidAPI 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 pip install "dlt[workspace]" and start loading ADS-B Exchange data in under 10 minutes.
What data can I load from ADS-B Exchange?
Here are some of the endpoints you can load from ADS-B Exchange:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| aircraft_near_point | api/aircraft/lat/{lat}/lon/{lon}/dist/{nm}/ | GET | ac | All aircraft within X nautical miles of a latitude/longitude point. |
| aircraft_by_icao | api/aircraft/icao/{hex}/ | GET | ac | Aircraft details for a given Mode‑S (ICAO) hex code. |
| aircraft_by_callsign | api/aircraft/call/{callsign}/ | GET | ac | Aircraft details for a given callsign. |
| version2_recent | api/aircraft.json | GET | aircraft | Recent aircraft list (Version 2) – top‑level aircraft array. |
| trace_file | api/trace/{icao}.json | GET | Trace file for an aircraft; response is a top‑level object containing a trace array. |
How do I authenticate with the ADS-B Exchange API?
Requests must include an api-auth HTTP header with your API UUID (or RapidAPI key).
1. Get your credentials
- Personal / lightweight access: Sign up at RapidAPI, subscribe to the ADSBexchange (adsbx) listing, and copy the provided RapidAPI key (use it as the
api-authheader).\n2) Enterprise / production access: Contact ADSBexchange via https://www.adsbexchange.com/contact/ or the Enterprise API product page to request an API UUID or credential bundle.
2. Add them to .dlt/secrets.toml
[sources.ads_b_exchange_source] api_key = "your_uuid_or_rapidapi_key"
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 ADS-B Exchange 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 ads_b_exchange_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline ads_b_exchange_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ads_b_exchange_data The duckdb destination used duckdb:/ads_b_exchange.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline ads_b_exchange_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 aircraft_near_point and aircraft_by_icao from the ADS-B Exchange 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 ads_b_exchange_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://adsbexchange.com/api", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "aircraft_near_point", "endpoint": {"path": "api/aircraft/lat/{lat}/lon/{lon}/dist/{nm}/", "data_selector": "ac"}}, {"name": "aircraft_by_icao", "endpoint": {"path": "api/aircraft/icao/{hex}/", "data_selector": "ac"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ads_b_exchange_pipeline", destination="duckdb", dataset_name="ads_b_exchange_data", ) load_info = pipeline.run(ads_b_exchange_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("ads_b_exchange_pipeline").dataset() sessions_df = data.aircraft_near_point.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM ads_b_exchange_data.aircraft_near_point LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("ads_b_exchange_pipeline").dataset() data.aircraft_near_point.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 ADS-B Exchange 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 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 ADS-B Exchange?
Request dlt skills, commands, AGENT.md files, and AI-native context.