EasyPost Python API Docs | dltHub
Build a EasyPost-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
EasyPost is a shipping and logistics API platform that provides address verification, parcel and shipment creation, rate shopping, label purchasing, tracking, webhooks, and carrier integrations. The REST API base URL is https://api.easypost.com/v2 and All requests require Basic authentication using an API key as the username with no password..
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 EasyPost data in under 10 minutes.
What data can I load from EasyPost?
Here are some of the endpoints you can load from EasyPost:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| addresses | /addresses | GET | addresses | List Address objects |
| shipments | /shipments | GET | shipments | List Shipment objects |
| trackers | /trackers | GET | trackers | List Tracker objects |
| webhooks | /webhooks | GET | webhooks | List Webhook objects |
| parcels | /parcels | GET | parcels | List Parcel objects |
| rates | /shipments/:id/rates | GET | rates | Retrieve rates for a shipment (rates array in shipment object) |
| carriers | /carriers | GET | carriers | List Carrier objects |
| pickups | /pickups | GET | pickups | List Pickup objects |
| refunds | /refunds | GET | refunds | List Refund objects |
| orders | /orders | GET | orders | List Order objects |
How do I authenticate with the EasyPost API?
Authenticate every request by using your EasyPost API key as the HTTP Basic Auth username; the password field is left blank. All requests must be made over HTTPS.
1. Get your credentials
- Sign in to your EasyPost dashboard at https://app.easypost.com/.\n2) Navigate to Account Settings → API Keys (or directly to https://app.easypost.com/account/settings?tab=api-keys).\n3) Create a new API key or copy an existing Test or Production key.\n4) Store the key securely and use it as the username in HTTP Basic authentication.
2. Add them to .dlt/secrets.toml
[sources.easy_post_source] api_key = "your_easypost_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 EasyPost 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 easy_post_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline easy_post_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset easy_post_data The duckdb destination used duckdb:/easy_post.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline easy_post_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 shipments and trackers from the EasyPost 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 easy_post_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.easypost.com/v2", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "shipments", "endpoint": {"path": "shipments", "data_selector": "shipments"}}, {"name": "trackers", "endpoint": {"path": "trackers", "data_selector": "trackers"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="easy_post_pipeline", destination="duckdb", dataset_name="easy_post_data", ) load_info = pipeline.run(easy_post_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("easy_post_pipeline").dataset() sessions_df = data.shipments.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM easy_post_data.shipments LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("easy_post_pipeline").dataset() data.shipments.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 EasyPost 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
If you receive a 401 Unauthorized response, verify that you are using HTTP Basic authentication with your API key as the username and an empty password. Ensure the request is made over HTTPS and that the correct Test or Production key is being used.
Rate limits and throttling
EasyPost enforces rate limits on list endpoints. When a 429 Too Many Requests response is returned, implement exponential backoff and retry after a short delay. Monitor the X-RateLimit headers if they are present.
Pagination quirks
List endpoints return objects inside a top‑level plural key (e.g., shipments) together with a has_more boolean. Use pagination parameters such as before_id, after_id, start_datetime, end_datetime, and page_size (max 100, default 20) to navigate through pages.
Common error responses
EasyPost returns structured error objects. Example format:
{ "error": { "code": "...", "message": "...", "errors": [ { "code": "...", "field": "...", "message": "..." } ] } }
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 EasyPost?
Request dlt skills, commands, AGENT.md files, and AI-native context.