Load Connectors API data to DuckDB

The Connectors API enables users to create and manage connections to Google Cloud services and third-party business applications. Everything needed to build a working Connectors API → 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 Connectors API 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 Connectors API 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 Connectors API 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.

---

Connectors API API at a glance

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

---

How do I authenticate with the Connectors API API?

All requests require an OAuth 2.0 access token passed in the Authorization header with the format 'Bearer <ACCESS_TOKEN>'.

1. Get your credentials

The Google Cloud Connectors API requires OAuth 2.0 authentication. 1. Go to the Google Cloud Console (console.cloud.google.com). 2. Navigate to 'APIs & Services' > 'Credentials'. 3. Click 'Create Credentials' and select 'Service account'. 4. Assign the appropriate IAM roles (e.g., 'Connectors Admin') to the service account. 5. Create a JSON key for the service account and download the file. 6. In your dlt pipeline, set the environment variable GOOGLE_APPLICATION_CREDENTIALS to the path of this JSON key file, which dlt will use automatically to generate the required Bearer access tokens.

2. Add them to .dlt/secrets.toml

Copy
[sources.connectors_api_source]
# Example for .dlt/secrets.toml\n[sources.connectors_api]\n# Use these if you are managing custom tokens or API-based auth\napi_key = \"your_api_key_or_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 Connectors API data can I load into DuckDB?

These are the Connectors API endpoints dlt can load into DuckDB:

---

How do I load only new Connectors API records?

Connectors API exposes cursor on v1/projects/*/locations/*/providers/*/connectors, 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": "connectors", "endpoint": {
    "path": "v1/projects/*/locations/*/providers/*/connectors",
    "data_selector": "connectors",
    "incremental": {"cursor_path": "cursor", "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 Connectors API pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading 'connections and connectors'}},top_results:} target:{} }; from the Connectors API API into DuckDB:

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

@dlt.source
def connectors_api_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://connectors.googleapis.com",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "connectors", "endpoint": {"path": "v1/projects/*/locations/*/providers/*/connectors", "data_selector": "connectors"}},
            {"name": "environments_connectors", "endpoint": {"path": "connectivity/environments/{environmentId}/connectors", "data_selector": "value"}}
        ],
    }
    yield from rest_api_resources(config)


def load_connectors_api_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="connectors_api_pipeline",
        destination="duckdb",
        dataset_name="connectors_api_data",
    )
    load_info = pipeline.run(connectors_api_source())
    print(load_info)


if __name__ == "__main__":
    load_connectors_api_to_duckdb()

Run it with python connectors_api_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 Connectors API 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("connectors_api_pipeline").dataset()
df = data.connectors.df()
print(df.head())

SQL:

Copy
SELECT * FROM connectors_api_data.connectors LIMIT 10;

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

---

How do I deploy the Connectors API 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 Connectors API 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 Connectors API 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