NCEI Data Service Python API Docs | dltHub
Build a NCEI Data Service-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The NCEI Data Service API provides access to environmental data in various formats. It uses RESTful API with GET requests. The endpoint is at /access/services/data/v1. The REST API base URL is https://www.ncei.noaa.gov/access/services and No authentication required for the NCEI Access Data, Search and Support services (public, open endpoints)..
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 NCEI Data Service data in under 10 minutes.
What data can I load from NCEI Data Service?
Here are some of the endpoints you can load from NCEI Data Service:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| data | /data/v1?{params} | GET | (top-level array) | Access and subset dataset observations; supports dataset, stations, dataTypes, startDate, endDate, format=json, options, units, etc. |
| search_data | /search/v1/data?{params} | GET | results | Search for data granules/records (returns paginated results array) |
| search_datasets | /search/v1/datasets?{params} | GET | results | Discover datasets available to the Search service (returns results array) |
| support_datasets | /support/v3/datasets.json or /support/v3/datasets/{datasetId}.json | GET | results | Retrieve dataset metadata/attributes (returns results array) |
| orders | /orders/v1?{params} | GET | results | Retrieve previous orders (paginated results array) |
| search_keywords | /search/v1/keywords?{params} | GET | keywords.bucket | List available keywords (returned in keywords.bucket array) |
How do I authenticate with the NCEI Data Service API?
The Data, Search and Support APIs are public REST endpoints that use HTTPS and return JSON (when format=json). No API key or Authorization header is required. (Note: NCEI’s separate Climate Data Online API requires an access token, but that is a different service.)
1. Get your credentials
The Data, Search and Support services do not require credentials. For other NCEI APIs (e.g., Climate Data Online) obtain a token from the NOAA/NCEI developer portal per that API’s docs.
2. Add them to .dlt/secrets.toml
[sources.ncei_data_service_source] # no credentials required for Data/Search/Support services
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 NCEI Data Service 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 ncei_data_service_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline ncei_data_service_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ncei_data_service_data The duckdb destination used duckdb:/ncei_data_service.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline ncei_data_service_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 data and datasets from the NCEI Data Service 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 ncei_data_service_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.ncei.noaa.gov/access/services", "auth": { "type": "none", "": , }, }, "resources": [ {"name": "data", "endpoint": {"path": "data/v1"}}, {"name": "datasets", "endpoint": {"path": "search/v1/datasets", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ncei_data_service_pipeline", destination="duckdb", dataset_name="ncei_data_service_data", ) load_info = pipeline.run(ncei_data_service_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("ncei_data_service_pipeline").dataset() sessions_df = data.data.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM ncei_data_service_data.data LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("ncei_data_service_pipeline").dataset() data.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 NCEI Data Service 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 NCEI Data Service?
Request dlt skills, commands, AGENT.md files, and AI-native context.