Zoho Expense Python API Docs | dltHub

Build a Zoho Expense-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Zoho Expense is a REST API for managing business expense tracking, reports, receipts, users, currencies, categories, projects and related resources. The REST API base URL is https://www.zohoapis.com/expense/v1 and all requests require an OAuth 2.0 access token passed in the 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 add "dlt[hub]" and start loading Zoho Expense data in under 10 minutes.


What data can I load from Zoho Expense?

Here are some of the endpoints you can load from Zoho Expense:

ResourceEndpointMethodData selectorDescription
organizations/organizationsGETorganizationsList all organizations
expenses/expensesGETexpensesList all expenses
expense_reports/expensereportsGETexpensereportsList all expense reports
projects/projectsGETprojectsList all projects
expense_categories/expensecategoriesGETexpense_categoriesList all expense categories
users/usersGETusersList all users
currencies/currenciesGETcurrenciesList all currencies

How do I authenticate with the Zoho Expense API?

All requests require an Authorization header with the format 'Zoho-oauthtoken <access_token>' and a required 'X-com-zoho-expense-organizationid' header to specify the organization.

1. Get your credentials

  1. Navigate to the Zoho API Console at https://api-console.zoho.com/. 2. Click Add Client and select the appropriate client type (e.g., Self Client for testing). 3. Upon registration, you will be issued a Client ID and a Client Secret. 4. To generate an OAuth access token, use the Authorization Code flow: First, direct the user to the Authorization URL (https://accounts.zoho.com/oauth/v2/auth) with the required scope and your client ID to obtain an authorization code. 5. Exchange this code for an access token and a refresh token by making a POST request to https://accounts.zoho.com/oauth/v2/token with your client_id, client_secret, code, and grant_type=authorization_code.

2. Add them to .dlt/secrets.toml

[sources.zoho_expense_source] access_token = "REPLACE_ME"

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 harness:

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 Zoho Expense 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 zoho_expense_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline zoho_expense_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zoho_expense_data The duckdb destination used duckdb:/zoho_expense.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 /organizations and /expensereports from the Zoho Expense 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_expense_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.zohoapis.com/expense/v1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "expensereports", "endpoint": {"path": "expensereports", "data_selector": "expensereports"}}, {"name": "expenses", "endpoint": {"path": "expenses", "data_selector": "expenses"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zoho_expense_pipeline", destination="duckdb", dataset_name="zoho_expense_data", ) load_info = pipeline.run(zoho_expense_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_expense_pipeline").dataset() sessions_df = data.expensereports.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM zoho_expense_data.expensereports LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("zoho_expense_pipeline").dataset() data.expensereports.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 Expense data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Zoho Expense?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines