Zuva Python API Docs | dltHub
Build a Zuva-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Zuva's REST API allows embedding machine learning into applications, with documentation available at https://zuva.ai/documentation/. The API supports data extraction and security policies for data protection. The REST API base URL is https://us.app.zuva.ai/api/v2 and All requests require a Bearer token 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 Zuva data in under 10 minutes.
What data can I load from Zuva?
Here are some of the endpoints you can load from Zuva:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| fields | /fields | GET | List all fields available to the user (response is a JSON array of field objects). | |
| field_accuracy | /fields/{field_id}/accuracy | GET | Get accuracy metrics for a custom field (response object with precision/recall/f_score). | |
| field_metadata | /fields/{field_id}/metadata | GET | Get metadata for a field (object with field_id, name, file_ids, etc.). | |
| field_validation_details | /fields/{field_id}/validation-details | GET | Returns an array of validation-example objects (example response is an array). | |
| extraction_status | /extraction/{request_id} | GET | Retrieve status of a single extraction request (response object with file_id, request_id, status). | |
| extraction_results | /extraction/{request_id}/results/text | GET | results | Retrieves extraction results; response contains a "results" array with field result objects. |
| extraction_statuses | /extractions | GET | statuses | Retrieve statuses for multiple extraction requests; response object contains a "statuses" object keyed by request_id. |
| mlc_status | /mlc/{request_id} | GET | Get status/results of a multi-level classification request (response includes "classifications" array when complete). | |
| mlc_statuses | /mlcs | GET | statuses | Get statuses of many MLC requests; response contains "statuses" mapping. |
| ocr_status | /ocr/{request_id} | GET | Get OCR request status (object with file_id, request_id, status, page_count, character_count). | |
| ocr_statuses | /ocrs | GET | statuses | Get multiple OCR statuses; response contains "statuses" mapping and "errors". |
| ocr_text | /ocr/{request_id}/text | GET | Returns OCR text as object with "request_id" and "text" string. | |
| ocr_images | /ocr/{request_id}/images | GET | Returns images as binary zip (no JSON record list). | |
| ocr_eocr | /ocr/{request_id}/eocr | GET | Returns eOCR document (binary/string). |
How do I authenticate with the Zuva API?
Include an Authorization header: "Authorization: Bearer ". Requests must be made to the same region (base URL) the token was created for.
1. Get your credentials
- Sign in to Zuva Dashboard (https://dashboard.zuva.ai).
- Open the Zuva API / DocAI console (e.g., https://docai.zuva.ai/).
- Select the region you will use (e.g., United States).
- Click Create Token, give it a name/description and confirm.
- Copy the generated token; it is shown only once.
2. Add them to .dlt/secrets.toml
[sources.zuva_source] token = "your_zuva_bearer_token_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 Zuva 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 zuva_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline zuva_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zuva_data The duckdb destination used duckdb:/zuva.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline zuva_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 fields and extraction_results from the Zuva 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 zuva_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://us.app.zuva.ai/api/v2", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "fields", "endpoint": {"path": "fields"}}, {"name": "extraction_results", "endpoint": {"path": "extraction/{request_id}/results/text", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zuva_pipeline", destination="duckdb", dataset_name="zuva_data", ) load_info = pipeline.run(zuva_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("zuva_pipeline").dataset() sessions_df = data.fields.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM zuva_data.fields LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("zuva_pipeline").dataset() data.fields.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 Zuva 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 Zuva?
Request dlt skills, commands, AGENT.md files, and AI-native context.