NASA OSDR Developer API Python API Docs | dltHub
Build a NASA OSDR Developer API-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
NASA OSDR (Open Science Data Repository) Biological Data API provides REST and query interfaces for accessing and exploring GeneLab and ALSDA biological datasets and metadata. The REST API base URL is https://visualization.osdr.nasa.gov/biodata/api/ and all requests are publicly accessible without authentication, though an optional API key can be used for rate-limited or intensive usage..
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 OSDR Developer API data in under 10 minutes.
What data can I load from NASA OSDR Developer API?
Here are some of the endpoints you can load from NASA OSDR Developer API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| datasets | /v2/datasets/ | GET | Returns a list of all datasets. | |
| dataset | /v2/dataset/{accession}/ | GET | Returns an expanded version of a specific dataset. | |
| assay | /v2/assay/ | GET | Returns a list of assays. | |
| experiments | /v2/experiments/ | GET | Returns a list of experiments. | |
| missions | /v2/missions/ | GET | Returns a list of missions. |
How do I authenticate with the NASA OSDR Developer API API?
Authentication is not required to access the OSDR APIs; however, a NASA developer key is recommended for intensive use.
1. Get your credentials
The NASA Open Science Data Repository (OSDR) APIs are currently public and do not require authentication or an API key to access. While other NASA APIs utilize the central api.nasa.gov portal for credential issuance, the OSDR Biological Data API and associated services remain open for programmatic access without a registered key.
2. Add them to .dlt/secrets.toml
[sources.nasa_osdr_developer_api_source] # No API key is required for NASA OSDR. # You may leave these fields blank or omit them from your configuration. osdr_api_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 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 OSDR Developer API 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_osdr_developer_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline nasa_osdr_developer_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset nasa_osdr_developer_api_data The duckdb destination used duckdb:/nasa_osdr_developer_api.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 /v2/query/metadata/ and /v2/query/data/ from the NASA OSDR Developer API 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_osdr_developer_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://visualization.osdr.nasa.gov/biodata/api/", "auth": {"type": "api_key", "api_key": api_key}, }, "resources": [ {"name": "datasets", "endpoint": {"path": "v2/datasets/"}}, {"name": "dataset", "endpoint": {"path": "v2/dataset/"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="nasa_osdr_developer_api_pipeline", destination="duckdb", dataset_name="nasa_osdr_developer_api_data", ) load_info = pipeline.run(nasa_osdr_developer_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("nasa_osdr_developer_api_pipeline").dataset() sessions_df = data.datasets.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM nasa_osdr_developer_api_data.datasets LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("nasa_osdr_developer_api_pipeline").dataset() data.datasets.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 OSDR Developer API 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 OSDR Developer API?
Request dlt skills, commands, AGENT.md files, and AI-native context.