Load Imperva SDK data to DuckDB

Imperva provides a REST API for managing account security, WAF policies, DDoS protection, bot management, and other cloud application security services. Everything needed to build a working Imperva SDK → 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 Imperva SDK 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 Imperva SDK 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 Imperva SDK 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.

---

Imperva SDK API at a glance

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

---

How do I authenticate with the Imperva SDK API?

Imperva APIs require authentication by including the API ID and API key in every request using the x-API-Id and x-API-Key HTTP request headers.

1. Get your credentials

1. Log in to the Imperva Cloud Security Console. 2. Navigate to 'Account' > 'Account Management' (or 'My Profile' for individual keys) > 'Users'. 3. Locate the user, click the ellipsis (...) in the 'Actions' column, and select 'Edit' (if managing another user) or directly access the 'API keys' tab. 4. Click 'Add API key'. 5. Provide a name and description, then save. 6. Copy the generated 'API ID' and 'API Key' immediately from the pop-up window; they cannot be retrieved after the window is closed. Note: Ensure 'API Client Creation Consent' is enabled in your account settings if required by your organization.

2. Add them to .dlt/secrets.toml

Copy
[sources.imperva_sdk_source]
imperva_api_id = "your_api_id_here"
imperva_api_key = "your_api_key_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 Imperva SDK data can I load into DuckDB?

These are the Imperva SDK endpoints dlt can load into DuckDB:

---

How do I load only new Imperva SDK records?

Imperva SDK exposes page_num on prov/v3/sites, 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": "sites", "endpoint": {
    "path": "prov/v3/sites",
    "data_selector": "sites",
    "incremental": {"cursor_path": "page_num", "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 Imperva SDK pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading policies/v2/policies and prov/v3/sites from the Imperva SDK API into DuckDB:

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

@dlt.source
def imperva_sdk_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.imperva.com",
            "auth": {"type": "api_key", "api_key": api_key, "name": "x-API-Key"},
        },
        "resources": [
            {"name": "sites", "endpoint": {"path": "prov/v3/sites", "data_selector": "sites"}},
            {"name": "policies", "endpoint": {"path": "prov/v3/sites/{site_id}/policies", "data_selector": "policies"}}
        ],
    }
    yield from rest_api_resources(config)


def load_imperva_sdk_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="imperva_sdk_pipeline",
        destination="duckdb",
        dataset_name="imperva_sdk_data",
    )
    load_info = pipeline.run(imperva_sdk_source())
    print(load_info)


if __name__ == "__main__":
    load_imperva_sdk_to_duckdb()

Run it with python imperva_sdk_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 Imperva SDK 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("imperva_sdk_pipeline").dataset()
df = data.sites.df()
print(df.head())

SQL:

Copy
SELECT * FROM imperva_sdk_data.sites LIMIT 10;

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

---

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