Load HPE Aruba Networking Central data to DuckDB

HPE Aruba Networking Central is a cloud-based network management platform that provides REST APIs for managing and configuring network devices and services. Everything needed to build a working HPE Aruba Networking Central → 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 HPE Aruba Networking Central 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 HPE Aruba Networking Central 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 HPE Aruba Networking Central 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.

---

HPE Aruba Networking Central API at a glance

These values come from the HPE Aruba Networking Central API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the HPE Aruba Networking Central API?

Authentication is performed using OAuth 2.0 access tokens. The token must be included in the Authorization header as a Bearer token (e.g., Authorization: Bearer <access_token>).

1. Get your credentials

To obtain API credentials, log in to the HPE GreenLake Cloud Platform (GLP) portal. Navigate to your account Home page, go to Manage Workspace, and select Personal API credentials. From there, you can create a new set of API client credentials to generate a client_id and client_secret. Once created, store these values securely, as you will need them to programmatically request access tokens (OAuth2 client_credentials flow) to authorize your API requests.

2. Add them to .dlt/secrets.toml

Copy
[sources.hpe_aruba_networking_central_source]
client_id = "your_client_id_here"
client_secret = "your_client_secret_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 HPE Aruba Networking Central data can I load into DuckDB?

These are the HPE Aruba Networking Central endpoints dlt can load into DuckDB:

---

How do I load only new HPE Aruba Networking Central records?

HPE Aruba Networking Central exposes next on msp_api/v1/customers, 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": "customers", "endpoint": {
    "path": "msp_api/v1/customers",
    "data_selector": "customers",
    "incremental": {"cursor_path": "next", "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 HPE Aruba Networking Central pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /monitoring/v1/ and /configuration/v2/ from the HPE Aruba Networking Central API into DuckDB:

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

@dlt.source
def hpe_aruba_networking_central_source(base_url=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "The base URL depends on the user's geographical cluster (e.g., us1.api.central.arubanetworks.com, eu1.api.central.arubanetworks.com, etc.), and must be retrieved from the API Gateway section of the Aruba Central account interface.",
            "auth": {"type": "bearer", "token": base_url},
        },
        "resources": [
            {"name": "customers", "endpoint": {"path": "msp_api/v1/customers", "data_selector": "customers"}},
            {"name": "devices", "endpoint": {"path": "monitoring/v2/devices", "data_selector": "devices"}}
        ],
    }
    yield from rest_api_resources(config)


def load_hpe_aruba_networking_central_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="hpe_aruba_networking_central_pipeline",
        destination="duckdb",
        dataset_name="hpe_aruba_networking_central_data",
    )
    load_info = pipeline.run(hpe_aruba_networking_central_source())
    print(load_info)


if __name__ == "__main__":
    load_hpe_aruba_networking_central_to_duckdb()

Run it with python hpe_aruba_networking_central_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 HPE Aruba Networking Central 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("hpe_aruba_networking_central_pipeline").dataset()
df = data.customers.df()
print(df.head())

SQL:

Copy
SELECT * FROM hpe_aruba_networking_central_data.customers LIMIT 10;

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

---

How do I deploy the HPE Aruba Networking Central 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 HPE Aruba Networking Central 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 HPE Aruba Networking Central 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