N2YO Python API Docs | dltHub
Build a N2YO-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
N2YO's REST API provides satellite tracking data. An API key is required for access. The API is used for building satellite tracking applications. The REST API base URL is https://api.n2yo.com/rest/v1/satellite and All requests require an API key (license key) passed as an apiKey query parameter..
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 N2YO data in under 10 minutes.
What data can I load from N2YO?
Here are some of the endpoints you can load from N2YO:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| tle | /tle/{id} | GET | tles | Retrieve Two-Line Element (TLE) data for a satellite by NORAD id. |
| positions | /positions/{id}/{observer_lat}/{observer_lng}/{observer_alt}/{seconds} | GET | positions | Future per‑second satellite positions and observer‑relative azimuth/elevation (limit 300). |
| visualpasses | /visualpasses/{id}/{observer_lat}/{observer_lng}/{observer_alt}/{days}/{min_visibility} | GET | passes | Predicted optically visible passes for a satellite over an observer location. |
| radiopasses | /radiopasses/{id}/{observer_lat}/{observer_lng}/{observer_alt}/{days}/{min_elevation} | GET | passes | Predicted radio‑communication passes (filtered by min elevation). |
| above | /above/{observer_lat}/{observer_lng}/{observer_alt}/{search_radius}/{category_id} | GET | above | Returns all objects within a given search radius above the observer (filterable by category). |
How do I authenticate with the N2YO API?
The N2YO REST API uses a per‑account license key. Append &apiKey={YOUR_KEY} to every request URL (GET). No additional headers are required.
1. Get your credentials
- Create an account at n2yo.com and sign in.
- Open your profile page.
- Scroll down to the API key generation section and generate your REST API license key.
- Copy the generated key; it cannot be changed. Contact N2YO to request a new key if needed.
2. Add them to .dlt/secrets.toml
[sources.n2yo_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 N2YO 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 n2yo_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline n2yo_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset n2yo_data The duckdb destination used duckdb:/n2yo.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline n2yo_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 positions and visualpasses from the N2YO 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 n2yo_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.n2yo.com/rest/v1/satellite", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "positions", "endpoint": {"path": "positions/{id}/{observer_lat}/{observer_lng}/{observer_alt}/{seconds}", "data_selector": "positions"}}, {"name": "visualpasses", "endpoint": {"path": "visualpasses/{id}/{observer_lat}/{observer_lng}/{observer_alt}/{days}/{min_visibility}", "data_selector": "passes"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="n2yo_pipeline", destination="duckdb", dataset_name="n2yo_data", ) load_info = pipeline.run(n2yo_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("n2yo_pipeline").dataset() sessions_df = data.positions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM n2yo_data.positions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("n2yo_pipeline").dataset() data.positions.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 N2YO 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 N2YO?
Request dlt skills, commands, AGENT.md files, and AI-native context.