Load SMC Python data to DuckDB

Forcepoint Secure Management Center (SMC) API is a RESTful interface for managing and automating Forcepoint NGFW and network security infrastructure components. Everything needed to build a working SMC Python → 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 SMC Python 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 SMC Python 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 SMC Python 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.

---

SMC Python API at a glance

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

---

How do I authenticate with the SMC Python API?

Authentication is performed via a POST request to the login endpoint, requiring an API client key provided in the JSON payload as {"authenticationkey": "..."}. Subsequent requests use a session cookie returned upon successful login.

1. Get your credentials

To obtain credentials for the Forcepoint Secure Management Center (SMC) API, perform the following steps within the SMC Client dashboard: 1. Navigate to 'Configuration' > 'Administration' > 'Access Rights'. 2. Right-click 'Access Rights' and select 'New' > 'API Client'. 3. Enter a unique name for the API Client. 4. Either use the initial authentication key provided or click 'Generate Authentication Key'. 5. Important: Copy this key immediately, as it is only displayed once. 6. Click the 'Permissions' tab to assign necessary access (e.g., 'Viewer' permission for 'All Simple Elements') and click 'OK' to save.

2. Add them to .dlt/secrets.toml

Copy
[sources.smc_python_source]
smc_address = "https://your_smc_ip:8082"
smc_apikey = "your_secret_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 SMC Python data can I load into DuckDB?

These are the SMC Python endpoints dlt can load into DuckDB:

---

How do I load only new SMC Python records?

The SMC Python 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": "elements", "endpoint": {
    "path": "elements",
    # 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 SMC Python pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /login and /elements from the SMC Python API into DuckDB:

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

@dlt.source
def smc_python_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://<smc-address>:8082",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key},
        },
        "resources": [
            {"name": "elements", "endpoint": {"path": "elements"}},
            {"name": "hosts", "endpoint": {"path": "elements/host"}}
        ],
    }
    yield from rest_api_resources(config)


def load_smc_python_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="smc_python_pipeline",
        destination="duckdb",
        dataset_name="smc_python_data",
    )
    load_info = pipeline.run(smc_python_source())
    print(load_info)


if __name__ == "__main__":
    load_smc_python_to_duckdb()

Run it with python smc_python_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 SMC Python 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("smc_python_pipeline").dataset()
df = data.elements.df()
print(df.head())

SQL:

Copy
SELECT * FROM smc_python_data.elements LIMIT 10;

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

---

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