Zendesk - Main API Python API Docs | dltHub
Build a Zendesk-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Zendesk is a customer service and engagement platform providing REST APIs for managing support, CRM, and omnichannel communication data. The REST API base URL is https://{subdomain}.zendesk.com/api/v2 and Zendesk APIs require an 'Authorization' header using either Basic (for API tokens) or Bearer (for OAuth access tokens) schemes..
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 Zendesk - Main API data in under 10 minutes.
What data can I load from Zendesk - Main API?
Here are some of the endpoints you can load from Zendesk - Main API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| incremental_tickets | /api/v2/incremental/tickets.json | GET | tickets | Time-based incremental export for tickets |
| incremental_users | /api/v2/incremental/users.json | GET | users | Time-based incremental export for users |
| incremental_tickets_cursor | /api/v2/incremental/tickets/cursor.json | GET | tickets | Cursor-based incremental export for tickets |
| tickets | /api/v2/tickets.json | GET | tickets | List all tickets using cursor or offset pagination |
| users | /api/v2/users.json | GET | users | List all users using cursor or offset pagination |
How do I authenticate with the Zendesk - Main API API?
Zendesk supports Basic authentication for API tokens (using '{email_address}/token:{api_token}' encoded in Base64) and Bearer token authentication for OAuth access tokens. The required header for both is 'Authorization'.
1. Get your credentials
To generate API credentials, log in to the Zendesk Admin Center as an administrator. Navigate to Apps and integrations > APIs > API configuration, enable Allow API token access, and save. Then, navigate to Apps and integrations > APIs > Zendesk API (or 'API tokens'), click Add API token, enter a description, and save. Copy the generated token immediately as it will not be shown again. Note that Zendesk is migrating away from API tokens toward OAuth access tokens, with full deprecation scheduled for April 30, 2027.
2. Add them to .dlt/secrets.toml
[sources.zendesk_main_api_source] subdomain = "your_subdomain" email = "your_email_address" api_token = "your_api_token"
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 Zendesk - Main API 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 zendesk_main_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline zendesk_main_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zendesk_main_api_data The duckdb destination used duckdb:/zendesk_main_api.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 tickets and search from the Zendesk - Main API 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 zendesk_main_api_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{subdomain}.zendesk.com/api/v2", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_token}, }, "resources": [ {"name": "incremental_tickets_cursor", "endpoint": {"path": "api/v2/incremental/tickets/cursor.json", "data_selector": "tickets"}}, {"name": "incremental_tickets", "endpoint": {"path": "api/v2/incremental/tickets.json", "data_selector": "tickets"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zendesk_main_api_pipeline", destination="duckdb", dataset_name="zendesk_main_api_data", ) load_info = pipeline.run(zendesk_main_api_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("zendesk_main_api_pipeline").dataset() sessions_df = data.incremental_tickets_cursor.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM zendesk_main_api_data.incremental_tickets_cursor LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("zendesk_main_api_pipeline").dataset() data.incremental_tickets_cursor.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 Zendesk - Main API 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 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 Zendesk - Main API?
Request dlt skills, commands, AGENT.md files, and AI-native context.
Available Pipelines
Zendesk - Main API to Microsoft Fabric
Zendesk is a customer service and engagement platform providing REST APIs for managing support, CRM, and omnichannel communication data
Destination: Microsoft Fabric
Zendesk - Main API to Snowflake
Zendesk is a customer service and engagement platform providing REST APIs for managing support, CRM, and omnichannel communication data
Destination: Snowflake