One Identity Safeguard for Privileged Sessions Python API Docs | dltHub
Build a One Identity Safeguard for Privileged Sessions-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
One Identity Safeguard for Privileged Sessions 8.0 LTS REST API allows CRUD operations on configuration resources. The API documentation is available for reference. The API enables configuration of certain SPS features via RESTful methods. The REST API base URL is https://<sps_host>/api and Requests require authentication — session-based session_id cookie or API keys (both supported)..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading One Identity Safeguard for Privileged Sessions data in under 10 minutes.
What data can I load from One Identity Safeguard for Privileged Sessions?
Here are some of the endpoints you can load from One Identity Safeguard for Privileged Sessions:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| configuration_management_license | /api/configuration/management/license | GET | body | Get license information for the appliance (response contains key, body, meta). |
| cluster | /api/cluster | GET | items | List cluster endpoints / nodes (top-level items list). |
| audit_sessions | /api/audit/sessions | GET | items | List audited sessions (session search/listing returns items array). |
| audit_recordings | /api/audit/recordings | GET | items | List available recorded files/recordings (returns items list). |
| configuration_management_universal_siem_forwarder | /api/configuration/management/universal_siem_forwarder | GET | body | Get SIEM forwarder configuration (configuration returned under body). |
| configuration_management_support_info | /api/configuration/management/support_info | GET | body | Get support/contact info (response contains body with uri). |
How do I authenticate with the One Identity Safeguard for Privileged Sessions API?
Authenticate by POSTing credentials to /api/authentication to receive a session_id cookie (use that cookie on subsequent requests). Alternatively SPS supports API keys and X.509 client certificate auth; API keys can be created in the SPS UI and used for REST calls.
1. Get your credentials
- Log in to the SPS web interface as an administrator. 2) Navigate to the Users & Access Control / API keys (or the "Authenticate to the SPS REST API -> Authenticate to the SPS REST API using API keys" section). 3) Create a new API key and copy its value. 4) Use the API key as the credential for the dlt source configuration (or authenticate via POST /api/authentication to obtain a session_id cookie).
2. Add them to .dlt/secrets.toml
[sources.one_identity_safeguard_privileged_sessions_source] api_key = "your_sps_api_key_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the One Identity Safeguard for Privileged Sessions API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python one_identity_safeguard_privileged_sessions_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline one_identity_safeguard_privileged_sessions_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset one_identity_safeguard_privileged_sessions_data The duckdb destination used duckdb:/one_identity_safeguard_privileged_sessions.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline one_identity_safeguard_privileged_sessions_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads audit_sessions and configuration_management_license from the One Identity Safeguard for Privileged Sessions API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def one_identity_safeguard_privileged_sessions_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<sps_host>/api", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "audit_sessions", "endpoint": {"path": "api/audit/sessions", "data_selector": "items"}}, {"name": "configuration_management_license", "endpoint": {"path": "api/configuration/management/license", "data_selector": "body"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="one_identity_safeguard_privileged_sessions_pipeline", destination="duckdb", dataset_name="one_identity_safeguard_privileged_sessions_data", ) load_info = pipeline.run(one_identity_safeguard_privileged_sessions_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("one_identity_safeguard_privileged_sessions_pipeline").dataset() sessions_df = data.audit_sessions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM one_identity_safeguard_privileged_sessions_data.audit_sessions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("one_identity_safeguard_privileged_sessions_pipeline").dataset() data.audit_sessions.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load One Identity Safeguard for Privileged Sessions data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for One Identity Safeguard for Privileged Sessions?
Request dlt skills, commands, AGENT.md files, and AI-native context.