Load Agencyzoom-ca67272 data to DuckDB

AgencyZoom is a sales and automation software for P&C insurance agents that exposes a REST API for managing leads, customers, policies, tasks, and configuration. Everything needed to build a working Agencyzoom-ca67272 → 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 Agencyzoom-ca67272 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 Agencyzoom-ca67272 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 Agencyzoom-ca67272 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.

---

Agencyzoom-ca67272 API at a glance

These values come from the Agencyzoom-ca67272 API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Agencyzoom-ca67272 API?

All API requests require an Authorization header containing a JWT bearer token formatted as 'Bearer '.

1. Get your credentials

To obtain credentials for the AgencyZoom API, follow these steps: 1. Log in to the AgencyZoom web application with an account that has appropriate administrative access (preferably the agency owner). 2. Navigate to the 'Integrations' page in the dashboard. 3. Locate the 'Zapier' (or generic API) integration section. 4. Click 'Show API Key' (and 'Show API Secret' if needed). These credentials can be used to authenticate requests. Note that for most programmatic access, you will need to exchange these credentials or use account email/password credentials to generate a JWT bearer token via the POST /v1/api/auth/login endpoint.

2. Add them to .dlt/secrets.toml

Copy
[sources.agencyzoom_ca67272_source]
token = "your_jwt_token_here"

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 Agencyzoom-ca67272 data can I load into DuckDB?

These are the Agencyzoom-ca67272 endpoints dlt can load into DuckDB:

---

How do I load only new Agencyzoom-ca67272 records?

The Agencyzoom-ca67272 API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "leads", "endpoint": {
    "path": "v1/api/leads",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "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 Agencyzoom-ca67272 pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v1/api/auth/login and /v1/api/customers from the Agencyzoom-ca67272 API into DuckDB:

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

@dlt.source
def agencyzoom_ca67272_source(token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.agencyzoom.com/v1/api",
            "auth": {"type": "bearer", "token": token},
        },
        "resources": [
            {"name": "leads", "endpoint": {"path": "v1/api/leads"}},
            {"name": "customers", "endpoint": {"path": "v1/api/customers"}}
        ],
    }
    yield from rest_api_resources(config)


def load_agencyzoom_ca67272_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="agencyzoom_ca67272_pipeline",
        destination="duckdb",
        dataset_name="agencyzoom_ca67272_data",
    )
    load_info = pipeline.run(agencyzoom_ca67272_source())
    print(load_info)


if __name__ == "__main__":
    load_agencyzoom_ca67272_to_duckdb()

Run it with python agencyzoom_ca67272_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 Agencyzoom-ca67272 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("agencyzoom_ca67272_pipeline").dataset()
df = data.leads.df()
print(df.head())

SQL:

Copy
SELECT * FROM agencyzoom_ca67272_data.leads LIMIT 10;

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

---

How do I deploy the Agencyzoom-ca67272 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 Agencyzoom-ca67272 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 Agencyzoom-ca67272 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