NASA CMR Search Python API Docs | dltHub
Build a NASA CMR Search-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
The NASA Common Metadata Repository (CMR) Search API is a RESTful service used to discover and access scientific metadata for Earth science collections, granules, and related assets. The REST API base URL is https://cmr.earthdata.nasa.gov/search and requests are authenticated using Bearer tokens or Launchpad tokens provided via Authorization headers or a token URL 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 add "dlt[hub]" and start loading NASA CMR Search data in under 10 minutes.
What data can I load from NASA CMR Search?
Here are some of the endpoints you can load from NASA CMR Search:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| collections | collections | GET | feed.entry | Search for metadata collections |
| granules | granules | GET | feed.entry | Search for metadata granules |
| providers | providers | GET | List available providers | |
| tags | tags | GET | List available tags | |
| tokens | tokens | GET | List user tokens |
How do I authenticate with the NASA CMR Search API?
Authentication is performed using tokens passed in the Authorization header. Earthdata Login (EDL) tokens use the 'Bearer' scheme (Authorization: Bearer ), while Launchpad tokens are passed directly (Authorization: ).
1. Get your credentials
- Create an account at the Earthdata Login (URS) portal (https://urs.earthdata.nasa.gov). 2. Once registered and logged in, navigate to your profile dashboard. 3. Look for the option to 'Generate Token' or manage authorized apps to create an EDL bearer token. Save this token securely as it will be used in your API request headers.
2. Add them to .dlt/secrets.toml
[sources.nasa_cmr_search_source] earthdata_bearer_token = "your_edl_access_token_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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 NASA CMR Search 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:
uv run python nasa_cmr_search_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline nasa_cmr_search_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset nasa_cmr_search_data The duckdb destination used duckdb:/nasa_cmr_search.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 /search/collections and /search/granules from the NASA CMR Search 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 nasa_cmr_search_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://cmr.earthdata.nasa.gov/search", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "collections", "endpoint": {"path": "collections", "data_selector": "feed.entry"}}, {"name": "granules", "endpoint": {"path": "granules", "data_selector": "feed.entry"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="nasa_cmr_search_pipeline", destination="duckdb", dataset_name="nasa_cmr_search_data", ) load_info = pipeline.run(nasa_cmr_search_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("nasa_cmr_search_pipeline").dataset() sessions_df = data.collections.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM nasa_cmr_search_data.collections LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("nasa_cmr_search_pipeline").dataset() data.collections.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 NASA CMR Search 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for NASA CMR Search?
Request dlt skills, commands, AGENT.md files, and AI-native context.