Windborne Systems Python API Docs | dltHub

Build a Windborne Systems-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

WindBorne Systems provides a REST API serving atmospheric observations, weather soundings, and AI-based gridded and point weather forecasts. The REST API base URL is https://api.windbornesystems.com and all requests require either a Bearer token or HTTP Basic Authentication.

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 Windborne Systems data in under 10 minutes.


What data can I load from Windborne Systems?

Here are some of the endpoints you can load from Windborne Systems:

ResourceEndpointMethodData selectorDescription
observations/observations/v1/observationsGETAccess atmospheric observations from GSB constellation
soundings/observations/v1/soundingsGETDiscover atmospheric soundings by time, location
mission_metadata/observations/v1/missionsGETRetrieve mission information and launch sites
point_forecast/forecasts/v6/point_forecastGETGet forecasts for specific coordinates
gridded_forecast/forecasts/v6/gridded_forecastGETDownload gridded forecast data

How do I authenticate with the Windborne Systems API?

The API supports two authentication methods: Bearer token authentication (using 'Authorization: Bearer <WB_API_KEY>' header) and HTTP Basic Auth (using WB_CLIENT_ID as username and WB_API_KEY as password).

1. Get your credentials

  1. Navigate to the WindBorne API portal at https://api.windbornesystems.com/. 2. Create an account to access the dashboard. 3. From the dashboard or API tokens page, request a free trial API key. For full commercial access, email data@windbornesystems.com with your intended workflow and requirements. 4. Once generated, ensure you have both your WB_API_KEY and WB_CLIENT_ID, as both are required for authentication.

2. Add them to .dlt/secrets.toml

[sources.windborne_systems_source] wb_client_id = "your_client_id_here" wb_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 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 Windborne Systems 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 windborne_systems_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline windborne_systems_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset windborne_systems_data The duckdb destination used duckdb:/windborne_systems.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 /debug/v1/auth_status and /point_forecast/interpolated from the Windborne Systems 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 windborne_systems_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.windbornesystems.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "observations", "endpoint": {"path": "observations/v1/observations"}}, {"name": "soundings", "endpoint": {"path": "observations/v1/soundings"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="windborne_systems_pipeline", destination="duckdb", dataset_name="windborne_systems_data", ) load_info = pipeline.run(windborne_systems_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("windborne_systems_pipeline").dataset() sessions_df = data.observations.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM windborne_systems_data.observations LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("windborne_systems_pipeline").dataset() data.observations.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 Windborne Systems data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Windborne Systems?

Request dlt skills, commands, AGENT.md files, and AI-native context.