Load Pega Platform data in Python using dltHub
Build a Pega Platform-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Pega Platform REST API is a suite of services for managing and interacting with application components such as cases, assignments, and data integration. The REST API base URL is https://<host>/prweb/api and Requests can be authenticated via OAuth 2.0 (Bearer token) or HTTP Basic Authentication..
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 add "dlt[hub]" and start loading Pega Platform data in under 10 minutes.
What data can I load from Pega Platform?
Here are some of the endpoints you can load from Pega Platform:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| data_objects | /data_objects | GET | Retrieve a list of data objects. | |
| data_pages | /data_pages | GET | Retrieve a list of available data pages (data views). | |
| cases | /api/v1/cases | GET | cases | Get a list of cases created by the authenticated user. |
| data_view | /data_views/{data_view_ID} | GET | Retrieve a single data page (data view). | |
| data_view_list | /data_views/{data_view_ID} | POST | Query a list data page using filters and pagination. |
How do I authenticate with the Pega Platform API?
Authentication is typically performed using OAuth 2.0 via a Bearer token in the Authorization header or HTTP Basic Authentication. When using OAuth 2.0, the Authorization header follows the format 'Authorization: Bearer ', where the token is a Pega-issued Authorized Access Token (AAT) in JWT format.
1. Get your credentials
- Log in to your Pega Platform instance and switch to Dev Studio. 2. Navigate to the Records explorer and locate Data Model > Data-Admin-Security-OAuth2-ClientRegistration. 3. Create a new OAuth 2.0 client registration instance. 4. In the Client Information tab, select 'Client Credentials' grant type. 5. Associate an Operator ID that has the necessary access privileges. 6. Click 'Save' to generate the Client ID and Client Secret. 7. Click 'View & download' to save your credentials to a text file (this is your only opportunity to view the secret). 8. Use the provided Access token endpoint URL, along with your Client ID and Client Secret, to authenticate and receive an access token.
2. Add them to .dlt/secrets.toml
[sources.pega_platform_source] api_key = "REPLACE_ME"
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 Pega Platform 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:
uv run python pega_platform_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pega_platform_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pega_platform_data The duckdb destination used duckdb:/pega_platform.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 /cases and /assignments from the Pega Platform 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 pega_platform_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<host>/prweb/api", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "cases", "endpoint": {"path": "api/v1/cases", "data_selector": "cases"}}, {"name": "data_views_query", "endpoint": {"path": "data_views/{data_view_ID}", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pega_platform_pipeline", destination="duckdb", dataset_name="pega_platform_data", ) load_info = pipeline.run(pega_platform_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("pega_platform_pipeline").dataset() sessions_df = data.data_views.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pega_platform_data.data_views LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pega_platform_pipeline").dataset() data.data_views.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 Pega Platform 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Pega Platform?
Request dlt skills, commands, AGENT.md files, and AI-native context.