Load CyberArk Identity API data to DuckDB

CyberArk Identity is an identity and access management platform that provides REST APIs for authentication, OAuth/OIDC token issuance, and user/resource management. Everything needed to build a working CyberArk Identity API → 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 CyberArk Identity API 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 CyberArk Identity API 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 CyberArk Identity API 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.

---

CyberArk Identity API API at a glance

These values come from the CyberArk Identity API API documentation. Check them against the vendor's current reference before relying on them in production.

---

How do I authenticate with the CyberArk Identity API API?

Authenticated requests require an 'Authorization' header with the value 'Bearer '. The token is typically obtained via an OAuth2 flow or the /Security/AdvanceAuthentication endpoint.

1. Get your credentials

To obtain API credentials for machine-to-machine integration, navigate to the CyberArk Identity Admin Portal. Go to 'Apps' > 'Web Apps' or 'OAuth2 Client' to create a custom application. Configure it as an 'OAuth2 Confidential Client' and assign a 'Service User' with appropriate permissions. Upon saving, you will be provided with a 'Client ID' and 'Client Secret'. If using the API Gateway for on-premises access, navigate to the application's 'API Gateway' tab to generate an 'API Key', which is a unique string used for secure communication via specific request headers.

2. Add them to .dlt/secrets.toml

Copy
[sources.cyberark_identity_api_source]
api_key = "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 CyberArk Identity API data can I load into DuckDB?

These are the CyberArk Identity API endpoints dlt can load into DuckDB:

---

How do I load only new CyberArk Identity API records?

CyberArk Identity API exposes startIndex on scim/v2/Users, 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": "scim_users", "endpoint": {
    "path": "scim/v2/Users",
    "data_selector": "Resources",
    "incremental": {"cursor_path": "startIndex", "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 CyberArk Identity API pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /Security/StartAuthentication and /Security/AdvanceAuthentication from the CyberArk Identity API API into DuckDB:

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

@dlt.source
def cyberark_identity_api_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://<tenant-id>.id.cyberark.cloud",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "scim_users", "endpoint": {"path": "scim/v2/Users", "data_selector": "Resources"}},
            {"name": "discovered_accounts", "endpoint": {"path": "discovery/discoveredAccounts", "data_selector": "Results"}}
        ],
    }
    yield from rest_api_resources(config)


def load_cyberark_identity_api_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="cyberark_identity_api_pipeline",
        destination="duckdb",
        dataset_name="cyberark_identity_api_data",
    )
    load_info = pipeline.run(cyberark_identity_api_source())
    print(load_info)


if __name__ == "__main__":
    load_cyberark_identity_api_to_duckdb()

Run it with python cyberark_identity_api_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 CyberArk Identity API 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("cyberark_identity_api_pipeline").dataset()
df = data.scim_users.df()
print(df.head())

SQL:

Copy
SELECT * FROM cyberark_identity_api_data.scim_users LIMIT 10;

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

---

How do I deploy the CyberArk Identity API 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 CyberArk Identity API 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 CyberArk Identity API 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