Load Pax8 data to DuckDB

Pax8 is a cloud marketplace and channel management platform for IT professionals and managed service providers to manage products, billing, and provisioning. Everything needed to build a working Pax8 → 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 Pax8 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 Pax8 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 Pax8 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.

---

Pax8 API at a glance

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

---

How do I authenticate with the Pax8 API?

Pax8 uses OAuth 2.0. API requests must include an 'Authorization' header with a value of 'Bearer <access_token>'.

1. Get your credentials

1. Log in to your Pax8 account.\n2. Navigate to Settings in the left navigation menu, then open Integrations.\n3. Locate and open the Integrations Hub.\n4. Select API credentials.\n5. Click + Create API credential.\n6. Provide a descriptive name (e.g., 'Internal Automation' or the name of your integration).\n7. Save the credential to display your Client ID and Client Secret. Ensure these are stored securely as they provide full access to your Pax8 data.

2. Add them to .dlt/secrets.toml

Copy
[sources.pax8_source]
client_secret = "REPLACE_ME"

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

These are the Pax8 endpoints dlt can load into DuckDB:

---

How do I load only new Pax8 records?

Pax8 exposes page on v1/companies, 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": "companies", "endpoint": {
    "path": "v1/companies",
    "incremental": {"cursor_path": "page", "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 Pax8 pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading provision-requests and companies from the Pax8 API into DuckDB:

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

@dlt.source
def pax8_source(client_secret=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.pax8.com/v2",
            "auth": {"type": "bearer", "token": client_secret},
        },
        "resources": [
            {"name": "companies", "endpoint": {"path": "v1/companies"}},
            {"name": "subscriptions", "endpoint": {"path": "v1/subscriptions"}}
        ],
    }
    yield from rest_api_resources(config)


def load_pax8_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="pax8_pipeline",
        destination="duckdb",
        dataset_name="pax8_data",
    )
    load_info = pipeline.run(pax8_source())
    print(load_info)


if __name__ == "__main__":
    load_pax8_to_duckdb()

Run it with python pax8_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 Pax8 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("pax8_pipeline").dataset()
df = data.companies.df()
print(df.head())

SQL:

Copy
SELECT * FROM pax8_data.companies LIMIT 10;

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

---

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