ApiVerve Python API Docs | dltHub
Build a ApiVerve-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
ApiVerve is a unified API platform providing access to 200+ utility, data, and AI-powered APIs through a single, consistent REST interface. The REST API base URL is https://api.apiverve.com/v1 and all requests require an X-API-Key header for authentication.
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 ApiVerve data in under 10 minutes.
What data can I load from ApiVerve?
Here are some of the endpoints you can load from ApiVerve:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| car_models | ref/carmodels | GET | data.carModels | Returns vehicle make and model reference data. |
| integrations | integrations | GET | data.integrations | Lists available third‑party integrations and services. |
| api_list | api-endpoints | GET | data.apis | Directory of available APIs and endpoints. |
| glossary | glossary | GET | data.glossary | Platform glossary and terminology entries. |
| health | v1/health | GET | data | Service health status. |
How do I authenticate with the ApiVerve API?
APIVerve uses a single API key provided in the X-API-Key HTTP header for all requests; include Content-Type: application/json for POST/PUT requests.
1. Get your credentials
- Sign in or create an account at https://apiverve.com/. 2) Open the developer dashboard or API Keys section. 3) Create a new API key; copy the generated key. 4) Store the key securely and use it in the X-API-Key header for requests.
2. Add them to .dlt/secrets.toml
[sources.api_verve_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 ApiVerve 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 api_verve_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline api_verve_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset api_verve_data The duckdb destination used duckdb:/api_verve.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline api_verve_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 car_models and integrations from the ApiVerve 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 api_verve_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.apiverve.com/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "car_models", "endpoint": {"path": "ref/carmodels", "data_selector": "data.carModels"}}, {"name": "integrations", "endpoint": {"path": "integrations", "data_selector": "data.integrations"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="api_verve_pipeline", destination="duckdb", dataset_name="api_verve_data", ) load_info = pipeline.run(api_verve_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("api_verve_pipeline").dataset() sessions_df = data.car_models.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM api_verve_data.car_models LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("api_verve_pipeline").dataset() data.car_models.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 ApiVerve 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 "Invalid API key" or 401/403 responses, verify the X-API-Key header contains a valid API key from your dashboard, no extra spaces, and the key is active.
Rate limits
APIVerve returns rate‑limit headers on responses; if you hit limits, implement exponential backoff and inspect headers to determine remaining quota.
Unexpected response structure
APIVerve returns a standardized wrapper: {"status":"ok"|"error","error":null|"message","data":{...}}. Use the documented data selectors (e.g., data.carModels). If data is null and status is "error", inspect the error message for details.
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 ApiVerve?
Request dlt skills, commands, AGENT.md files, and AI-native context.