Load PredictHQ data to DuckDB

PredictHQ provides a Demand Intelligence API for accessing global event data, demand surges, and forecasting features. Everything needed to build a working PredictHQ → 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 PredictHQ 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 PredictHQ 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 PredictHQ 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.

---

PredictHQ API at a glance

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

---

How do I authenticate with the PredictHQ API?

PredictHQ uses token-based authentication via the Authorization header. Each request must include an 'Authorization' header with the value 'Bearer '.

1. Get your credentials

1. Log in to the PredictHQ WebApp at https://control.predicthq.com/. 2. Navigate to API Tools in the left-hand menu and select API Tokens. 3. Click the Create Token (or Create New Token) button. 4. Enter a descriptive name for the token and click Create. 5. Copy the generated token immediately, as it will not be displayed again.

2. Add them to .dlt/secrets.toml

Copy
[sources.predicthq_source]
api_token = "your_predicthq_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 PredictHQ data can I load into DuckDB?

These are the PredictHQ endpoints dlt can load into DuckDB:

---

How do I load only new PredictHQ records?

PredictHQ exposes updated on v1/events, 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": "events", "endpoint": {
    "path": "v1/events",
    "data_selector": "results",
    "incremental": {"cursor_path": "updated", "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 PredictHQ pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v1/events/ and /v1/events/count/ from the PredictHQ API into DuckDB:

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

@dlt.source
def predicthq_source(api_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.predicthq.com",
            "auth": {"type": "bearer", "token": api_token},
        },
        "resources": [
            {"name": "events", "endpoint": {"path": "v1/events", "data_selector": "results"}},
            {"name": "broadcasts", "endpoint": {"path": "v1/broadcasts", "data_selector": "results"}}
        ],
    }
    yield from rest_api_resources(config)


def load_predicthq_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="predicthq_pipeline",
        destination="duckdb",
        dataset_name="predicthq_data",
    )
    load_info = pipeline.run(predicthq_source())
    print(load_info)


if __name__ == "__main__":
    load_predicthq_to_duckdb()

Run it with python predicthq_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 PredictHQ 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("predicthq_pipeline").dataset()
df = data.events.df()
print(df.head())

SQL:

Copy
SELECT * FROM predicthq_data.events LIMIT 10;

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

---

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