Pystac Client Python API Docs | dltHub
Build a Pystac Client-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Pystac Client is a Python client for interacting with STAC Catalogs and STAC APIs, providing helpers for opening STAC roots, searching, paging, and retrieving Collections and Items. The REST API base URL is https://earth-search.aws.element84.com/v1 and All requests require a Bearer token provided in the Authorization header..
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 Pystac Client data in under 10 minutes.
What data can I load from Pystac Client?
Here are some of the endpoints you can load from Pystac Client:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| client_root | / | GET | STAC Catalog root (contains links, conformsTo) | |
| collections | /collections | GET | collections | List collections (if implemented) |
| collection_items | /collections/{collection_id}/items | GET | features | Items in a collection (STAC ItemFeatureCollection) |
| search | /search | POST/GET | features | Item search results (ItemCollection) |
| queryables | /queryables | GET | Queryables schema describing searchable fields | |
| collection | /collections/{collection_id} | GET | Single collection metadata | |
| item | /collections/{collection_id}/items/{item_id} | GET | Single item metadata | |
| conformance | /conformance | GET | List of conformance classes | |
| landing_pages | links from root | GET | Additional linked resources |
How do I authenticate with the Pystac Client API?
Authentication is provided via custom HTTP headers (e.g., Authorization: Bearer ) passed to StacApiIO or the Client's request_modifier.
1. Get your credentials
- Visit the provider’s website (e.g., https://planetarycomputer.microsoft.com or https://earth-search.aws.element84.com).
- Sign in or create an account.
- Navigate to the API/Token section of the dashboard.
- Generate a new API token or locate the existing token.
- Copy the token and store it securely (e.g., in an environment variable or secrets.toml).
- Supply the token as a Bearer header in your PySTAC‑Client code.
2. Add them to .dlt/secrets.toml
[sources.pystac_client_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 Pystac Client 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 pystac_client_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pystac_client_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pystac_client_data The duckdb destination used duckdb:/pystac_client.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline pystac_client_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 search and collections from the Pystac Client 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 pystac_client_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://earth-search.aws.element84.com/v1", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "search", "endpoint": {"path": "search", "data_selector": "features"}}, {"name": "collections", "endpoint": {"path": "collections", "data_selector": "collections"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pystac_client_pipeline", destination="duckdb", dataset_name="pystac_client_data", ) load_info = pipeline.run(pystac_client_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("pystac_client_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pystac_client_data.search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pystac_client_pipeline").dataset() data.search.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 Pystac Client 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.
Troubleshooting
Authentication failures
Ensure you pass an Authorization header (e.g., Bearer token) via Client.open(..., stac_io=StacApiIO(headers={"Authorization":"Bearer <token>"})) or using request_modifier. Verify that the token is still valid with the provider.
Pagination and method fallback
ItemSearch uses POST by default; if POST returns a 405, the client automatically retries with GET for subsequent pages. Control page size with limit or max_items; results are returned in the features array and pagination follows the links provided by the STAC API.
Missing /collections or /search support
Not all STAC roots implement these endpoints. When the endpoint/link is absent, the client raises NotImplementedError. Check the root catalog's links to confirm available endpoints before invoking them.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Pystac Client?
Request dlt skills, commands, AGENT.md files, and AI-native context.