First Street Python API Docs | dltHub
Build a First Street-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
First Street API offers three main services: Climate Risk, Enterprise, and Raster Map. Authorization is required via Bearer token. The current default version is Vintage 2. The REST API base URL is https://api.firststreet.org/v1 and All requests require an API key (Bearer token or key 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 pip install "dlt[workspace]" and start loading First Street data in under 10 minutes.
What data can I load from First Street?
Here are some of the endpoints you can load from First Street:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| location_summary_property | /location/summary/property/{fsid} | GET | Property-level location summary (Flood Factor, counts, projections). | |
| location_detail_property | /location/detail/property/{fsid} | GET | Property-level detail including FSIDs, geometry, footprint, FEMA zone, elevation. | |
| probability_depth_property | /probability/depth/property/{fsid} | GET | Probability depth product for a property (JSON numeric depth values) and also available as PNG tiles. | |
| probability_chance_property | /probability/chance/property/{fsid} | GET | Probability chance product for a property. | |
| probability_count_neighborhood | /probability/count/neighborhood/{fsid} | GET | Probability count aggregated for neighborhoods (counts of at-risk properties). | |
| probability_cumulative_property | /probability/cumulative/property/{fsid} | GET | Cumulative probability product for a property. | |
| raster_tile_probability_depth | /probability/depth/{year}/{returnPeriod}/{z}/{x}/{y}.png | GET | Raster PNG tiles for probability depth map tiles. | |
| historic_event_tile | /historic/event/{eventId}/{z}/{x}/{y}.png | GET | Raster tiles for historic events. |
How do I authenticate with the First Street API?
The API accepts an API key either in the Authorization header as 'Authorization: Bearer <API_KEY>' or as a URL parameter 'key=<API_KEY>'.
1. Get your credentials
Log in to your First Street account/dashboard (or contact api@firststreet.org). Your API key is displayed in the dashboard; copy it and use it as the Authorization Bearer token or pass it as the 'key' URL parameter.
2. Add them to .dlt/secrets.toml
[sources.first_street_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 First Street 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 first_street_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline first_street_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset first_street_data The duckdb destination used duckdb:/first_street.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline first_street_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 location_summary_property and location_detail_property from the First Street 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 first_street_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.firststreet.org/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "location_summary_property", "endpoint": {"path": "location/summary/property/{fsid}"}}, {"name": "location_detail_property", "endpoint": {"path": "location/detail/property/{fsid}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="first_street_pipeline", destination="duckdb", dataset_name="first_street_data", ) load_info = pipeline.run(first_street_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("first_street_pipeline").dataset() sessions_df = data.location_summary_property.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM first_street_data.location_summary_property LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("first_street_pipeline").dataset() data.location_summary_property.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 First Street 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 First Street?
Request dlt skills, commands, AGENT.md files, and AI-native context.