Anvyl Python API Docs | dltHub
Build a Anvyl-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Anvyl is a supply chain intelligence API that provides programmatic access to purchase orders, shipments, suppliers, products, and related data. The REST API base URL is https://api.anvyl.com/api/v1 and All requests require an API Key and the team_id, passed via an 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 Anvyl data in under 10 minutes.
What data can I load from Anvyl?
Here are some of the endpoints you can load from Anvyl:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| purchase_orders | /v1/teams/{team_id}/purchase_orders | GET | Retrieve a list of purchase orders for a team. | |
| shipments | /v1/teams/{team_id}/shipments | GET | Retrieve shipment records for a team. | |
| suppliers | /v1/teams/{team_id}/suppliers | GET | List suppliers associated with a team. | |
| products | /v1/teams/{team_id}/products | GET | Get product catalog for a team. | |
| parts | /v1/teams/{team_id}/parts | GET | Retrieve parts information for a team. |
How do I authenticate with the Anvyl API?
Include the API Key in the Authorization header (e.g., 'Authorization: Bearer <api_key>') and include the team_id in the URL path, such as /v1/teams/{team_id}/... .
1. Get your credentials
- Log in to the Anvyl portal.
- Click on your avatar in the top‑right corner.
- Select My Account.
- Click the GENERATE API KEY button.
- Copy the displayed API key and store it securely; only one key is needed per team.
2. Add them to .dlt/secrets.toml
[sources.anvyl_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 Anvyl 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 anvyl_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline anvyl_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset anvyl_data The duckdb destination used duckdb:/anvyl.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline anvyl_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 purchase_orders and shipments from the Anvyl 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 anvyl_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.anvyl.com/api/v1", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "purchase_orders", "endpoint": {"path": "v1/teams/{team_id}/purchase_orders"}}, {"name": "shipments", "endpoint": {"path": "v1/teams/{team_id}/shipments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="anvyl_pipeline", destination="duckdb", dataset_name="anvyl_data", ) load_info = pipeline.run(anvyl_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("anvyl_pipeline").dataset() sessions_df = data.purchase_orders.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM anvyl_data.purchase_orders LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("anvyl_pipeline").dataset() data.purchase_orders.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 Anvyl 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 Errors
- 401 Unauthorized – Occurs when the API key is missing, malformed, or does not match the team_id. Verify that the
Authorization: Bearer <api_key>header is present and that the correctteam_idis used in the URL.
Rate Limiting
- 429 Too Many Requests – The API enforces request quotas per team. If exceeded, the response includes a
Retry-Afterheader indicating when to retry.
Pagination
- Endpoints return paginated results using
pageandpage_sizequery parameters. The response includestotal,page, andpage_sizefields to navigate through pages.
Request IDs
- Every response includes an
X-Request-Idheader which can be used for debugging and support tickets.
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 Anvyl?
Request dlt skills, commands, AGENT.md files, and AI-native context.