Load Zoho recruit data to DuckDB

Zoho Recruit is a REST API providing tools for managing recruitment modules such as candidates, clients, and job openings. Everything needed to build a working Zoho recruit → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Zoho recruit to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Zoho recruit to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Zoho recruit API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Zoho recruit API at a glance

These values come from the Zoho recruit API documentation. Check them against the vendor's current reference before relying on them in production.

---

How do I authenticate with the Zoho recruit API?

The Zoho Recruit API uses OAuth 2.0 authentication. Access tokens must be passed in the HTTP Authorization header using the format 'Authorization: Zoho-oauthtoken {access_token}'.

1. Get your credentials

Zoho Recruit REST API uses OAuth 2.0 authentication. To obtain credentials: 1. Go to the Zoho Developer Console (https://api-console.zoho.com/). 2. Click 'Add Client' and select a client type (e.g., 'Web-based' or 'Self Client'). 3. Enter the required details (Client Name, Homepage URL, Redirect URIs) and click 'Create'. 4. You will receive a Client ID and Client Secret. 5. Use these credentials to initiate the OAuth 2.0 flow: authorize your app to obtain a 'grant token' (authorization code), then exchange this code at the Zoho accounts token endpoint for an access token and refresh token. The access token must be passed in the HTTP Authorization header as 'Authorization: Zoho-oauthtoken {access_token}' for every API request.

2. Add them to .dlt/secrets.toml

Copy
[sources.zoho_recruit_source]
client_id = "your_client_id_here"
client_secret = "your_client_secret_here"
refresh_token = "your_refresh_token_here"
accounts_url = "https://accounts.zoho.com"
api_domain = "https://www.zohoapis.com"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Zoho recruit data can I load into DuckDB?

These are the Zoho recruit endpoints dlt can load into DuckDB:

---

How do I load only new Zoho recruit records?

Zoho recruit exposes Modified_Time on {module_api_name}, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "records", "endpoint": {
    "path": "{module_api_name}",
    "data_selector": "data",
    "incremental": {"cursor_path": "Modified_Time", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Zoho recruit pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading GET /recruit/v2/{module_api_name} and POST /recruit/v2/{module_api_name} from the Zoho recruit API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def zoho_recruit_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://recruit.zoho.com/recruit/v2/ (Note: domain varies by data center, e.g., zohoapis.eu, zohoapis.com.cn)",
            "auth": {"type": "api_key", "api_key": access_token, "name": "Authorization", "location": "header"},
        },
        "resources": [
            {"name": "records", "endpoint": {"path": "{module_api_name}", "data_selector": "data"}},
            {"name": "users", "endpoint": {"path": "users", "data_selector": "users"}}
        ],
    }
    yield from rest_api_resources(config)


def load_zoho_recruit_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="zoho_recruit_pipeline",
        destination="duckdb",
        dataset_name="zoho_recruit_data",
    )
    load_info = pipeline.run(zoho_recruit_source())
    print(load_info)


if __name__ == "__main__":
    load_zoho_recruit_to_duckdb()

Run it with python zoho_recruit_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Zoho recruit data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("zoho_recruit_pipeline").dataset()
df = data.records.df()
print(df.head())

SQL:

Copy
SELECT * FROM zoho_recruit_data.records LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Zoho recruit to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Zoho recruit loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Zoho recruit data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack