Parcl Labs Python API Docs | dltHub
Build a Parcl Labs-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Parcl Labs API provides real-time unit-level data on property attributes and housing events for the U.S. housing market. The REST API base URL is https://api.parcllabs.com/v1 and all requests require an API key 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 add "dlt[hub]" and start loading Parcl Labs data in under 10 minutes.
What data can I load from Parcl Labs?
Here are some of the endpoints you can load from Parcl Labs:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| markets | v1/search/markets | GET | Search for markets by name or geographic criteria to retrieve parcl_id values. | |
| housing_stock | v1/market_metrics/{parcl_id}/housing_stock | GET | Retrieve housing stock data for a specific market using its parcl_id. | |
| sale_metrics | v1/market_metrics/{parcl_id}/sale_metrics | GET | Retrieve sale metrics for a specific market. | |
| rental_metrics | v1/market_metrics/{parcl_id}/rental_metrics | GET | Retrieve rental metrics for a specific market. | |
| property_search | v2/property_search | POST | Search for properties; pagination has been removed in favor of large-scale bulk retrieval. |
How do I authenticate with the Parcl Labs API?
Authentication is performed by passing the API key in the 'Authorization' header. The value must be the raw API key without any 'Bearer' prefix.
1. Get your credentials
To obtain your Parcl Labs API credentials, follow these steps: 1. Sign up for or log in to your account at the official Parcl Labs dashboard (https://dashboard.parcllabs.com/signup or https://app.parcllabs.com). 2. Navigate to the API-Resources section (accessible via https://app.parcllabs.com/data-vault/api-resources). 3. Copy your API key from the dashboard. Note that the API key is tied to your user account and should be handled securely as a secret.
2. Add them to .dlt/secrets.toml
[sources.parcl_labs_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 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 Parcl Labs 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 parcl_labs_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline parcl_labs_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset parcl_labs_data The duckdb destination used duckdb:/parcl_labs.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 /search/markets and /market_metrics/{parcl_id}/housing_stock from the Parcl Labs 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 parcl_labs_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.parcllabs.com/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "Authorization", "location": "header"}, }, "resources": [ {"name": "markets", "endpoint": {"path": "v1/search/markets"}}, {"name": "housing_stock", "endpoint": {"path": "v1/market_metrics/{parcl_id}/housing_stock"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="parcl_labs_pipeline", destination="duckdb", dataset_name="parcl_labs_data", ) load_info = pipeline.run(parcl_labs_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("parcl_labs_pipeline").dataset() sessions_df = data.markets.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM parcl_labs_data.markets LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("parcl_labs_pipeline").dataset() data.markets.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 Parcl Labs 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 Parcl Labs?
Request dlt skills, commands, AGENT.md files, and AI-native context.