Zoho CRM Python API Docs | dltHub
Build a Zoho CRM-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Zoho CRM is a cloud customer relationship management platform exposing REST APIs to manage CRM records and metadata. The REST API base URL is https://www.zohoapis.com/crm/v2 and All requests require OAuth2 Bearer access tokens..
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 Zoho CRM data in under 10 minutes.
What data can I load from Zoho CRM?
Here are some of the endpoints you can load from Zoho CRM:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| leads | /crm/v2/Leads | GET | data | List records in Leads module |
| contacts | /crm/v2/Contacts | GET | data | List Contact records |
| accounts | /crm/v2/Accounts | GET | data | List Account records |
| deals | /crm/v2/Deals | GET | data | List Deal (Potential) records |
| modules | /crm/v2/settings/modules | GET | modules | List metadata for all modules |
| fields | /crm/v2/settings/fields?module=Leads | GET | fields | List field metadata for a specific module |
| record_by_id | /crm/v2/Leads/{id} | GET | data | Retrieve a single Lead record |
| search_records | /crm/v2/Leads/search?criteria=(...) | GET | data | Search Leads based on criteria |
How do I authenticate with the Zoho CRM API?
Use OAuth2 to obtain access and refresh tokens via Zoho Accounts and include an "Authorization: Bearer <access_token>" header in each request.
1. Get your credentials
- Log in to the Zoho API Console and create a new client.
- Note the generated client_id and client_secret.
- Build the authorization URL: https://accounts.zoho.com/oauth/v2/auth?client_id=<client_id>&scope=ZohoCRM.modules.ALL&response_type=code&redirect_uri=<redirect_uri>.
- Open the URL, grant access, and capture the authorization code.
- Exchange the code for tokens via POST to https://accounts.zoho.com/oauth/v2/token with client_id, client_secret, redirect_uri, code, and grant_type=authorization_code.
- Store the returned access_token and refresh_token for API calls; refresh the access token when it expires using the refresh_token.
2. Add them to .dlt/secrets.toml
[sources.zoho_crm_source] access_token = "your_access_token" refresh_token = "your_refresh_token" client_id = "your_client_id" client_secret = "your_client_secret"
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 Zoho CRM 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 zoho_crm_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline zoho_crm_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zoho_crm_data The duckdb destination used duckdb:/zoho_crm.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline zoho_crm_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 leads and contacts from the Zoho CRM 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 zoho_crm_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.zohoapis.com/crm/v2", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "leads", "endpoint": {"path": "crm/v2/Leads", "data_selector": "data"}}, {"name": "contacts", "endpoint": {"path": "crm/v2/Contacts", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zoho_crm_pipeline", destination="duckdb", dataset_name="zoho_crm_data", ) load_info = pipeline.run(zoho_crm_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("zoho_crm_pipeline").dataset() sessions_df = data.leads.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM zoho_crm_data.leads LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("zoho_crm_pipeline").dataset() data.leads.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 Zoho CRM 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 (401)
- Cause: Missing, expired, or invalid access token.
- Remedy: Regenerate the access token using the refresh token or repeat the OAuth2 grant flow.
Rate limits (429)
- Cause: Exceeding the allowed number of requests per minute.
- Header:
X-RateLimit-Limit,X-RateLimit-Remaining,X-RateLimit-Reset. - Remedy: Honor the
Retry-Afterheader or implement exponential backoff.
Invalid parameters (400)
- Cause: Incorrect query syntax, unsupported fields, or malformed IDs.
- Remedy: Check the error
codeandmessagein the response body and adjust the request accordingly.
Pagination
- Zoho returns an
infoobject withmore_records(boolean) andpagenumber. - Use the
pagequery parameter and continue fetching whileinfo.more_recordsis true.
Token expiry
- Access tokens are short‑lived; when a 401 with
invalid_tokenoccurs, use the stored refresh token to obtain a new access token via the token endpoint.
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 Zoho CRM?
Request dlt skills, commands, AGENT.md files, and AI-native context.