Zuora Python API Docs | dltHub
Build a Zuora-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Zuora is a subscription management and billing platform that offers a REST API for managing accounts, subscriptions, orders, and custom objects. The REST API base URL is https://rest.zuora.com and All requests require a Bearer OAuth 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 add "dlt[hub]" and start loading Zuora data in under 10 minutes.
What data can I load from Zuora?
Here are some of the endpoints you can load from Zuora:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| accounts | /v1/accounts/{account-key} | GET | Retrieve account information including contacts, billing, and payment setup. | |
| subscriptions | /v1/subscriptions/{subscription-key} | GET | Retrieve details of a specific subscription. | |
| subscriptions_by_account | /v1/subscriptions/accounts/{account-key} | GET | List all subscriptions belonging to a given account. | |
| orders | /v1/orders | GET | records | Retrieve a list of orders. |
| custom_object_records | /objects/records/default/{object} | GET | records | Retrieve custom object records; response uses the 'records' key. |
How do I authenticate with the Zuora API?
Zuora uses OAuth 2.0. Obtain a bearer token from the /oauth/token endpoint and include it in each request as the Authorization header: "Bearer {access_token}".
1. Get your credentials
- Log in to your Zuora tenant.
- Navigate to Settings → Security → OAuth Clients.
- Click Create New Client and fill in the required details (name, redirect URI, etc.).
- After saving, note the generated client_id and client_secret.
- To obtain an access token, make a POST request to
https://rest.zuora.com/oauth/tokenwithgrant_type=client_credentials,client_id, andclient_secretin the request body (application/x‑www‑form‑urlencoded). - The response will contain an
access_tokenvalue to use for API calls.
2. Add them to .dlt/secrets.toml
[sources.zuora_source] access_token = "your_access_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 init uv add "dlt[hub]"
1. Install the dlt AI Workbench:
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 Zuora 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 zuora_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline zuora_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zuora_data The duckdb destination used duckdb:/zuora.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 accounts and subscriptions from the Zuora 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 zuora_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://rest.zuora.com", "auth": { "type": "bearer", "access_token": access_token, }, }, "resources": [ {"name": "accounts", "endpoint": {"path": "v1/accounts"}}, {"name": "subscriptions", "endpoint": {"path": "v1/subscriptions"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zuora_pipeline", destination="duckdb", dataset_name="zuora_data", ) load_info = pipeline.run(zuora_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("zuora_pipeline").dataset() sessions_df = data.accounts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM zuora_data.accounts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("zuora_pipeline").dataset() data.accounts.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 Zuora 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 bearer token is missing, expired, or invalid. Ensure you are requesting a fresh token from
/oauth/tokenand that theAuthorization: Bearer <token>header is correctly set.
Rate Limiting
- 429 Too Many Requests – Zuora enforces request throttling. If you receive this response, back off for a few seconds and retry. Consider implementing exponential backoff.
Pagination
- Zuora GET list endpoints support
pageandsizequery parameters. Example:GET /v1/orders?page=1&size=200. Continue fetching pages until the response contains no further records.
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.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-runtime
Was this page helpful?
Community Hub
Need more dlt context for Zuora?
Request dlt skills, commands, AGENT.md files, and AI-native context.
Available Pipelines
Zuora to AlloyDB
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: AlloyDB
Zuora to Amazon Athena
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Amazon Athena
Zuora to Amazon Redshift
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Amazon Redshift
Zuora to Amazon S3
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Amazon S3
Zuora to Azure Blob Storage
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Azure Blob Storage
Zuora to Azure Synapse Analytics
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Azure Synapse Analytics
Zuora to BigQuery
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: BigQuery
Zuora to ClickHouse
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: ClickHouse
Zuora to Databricks
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Databricks
Zuora to Dremio
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Dremio
Zuora to DuckDB
Zuora REST API provides access to billing, commerce, and finance operations including account management and report generation
Destination: DuckDB
Zuora to Google Cloud Storage
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Google Cloud Storage
Zuora to Local Filesystem
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Local Filesystem
Zuora to Microsoft SQL Server
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Microsoft SQL Server
Zuora to MotherDuck
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: MotherDuck
Zuora to Neon
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Neon
Zuora to PostgreSQL
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: PostgreSQL
Zuora to Snowflake
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Snowflake
Zuora to Supabase
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Supabase
Zuora to Timescale
Zuora’s v1 REST API provides operations for storefront integration, subscriber and account management, revenue schedules, and manipulation of Zuora object-model resources
Destination: Timescale