Corppass Python API Docs | dltHub

Build a Corppass-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Corppass Authorization API v2.0 documentation is available for onboarding digital services. The API facilitates OpenID Connect authentication and authorization. The legacy version is also documented for reference. The REST API base URL is https://id.corppass.gov.sg and All protected endpoints require a Bearer access token for 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 pip install "dlt[workspace]" and start loading Corppass data in under 10 minutes.


What data can I load from Corppass?

Here are some of the endpoints you can load from Corppass:

ResourceEndpointMethodData selectorDescription
openid_configuration.well-known/openid-configurationGETOpenID Provider metadata
jwks.well-known/jwks.jsonGETkeysJSON Web Key Set used to verify signatures
userinfouserinfoGETRetrieves user/entity information (requires Access Token)
authorization_infoauthorization-infoGETLegacy endpoint returning Corppass user authorization details
tokentokenPOSTExchanges client assertion for ID and Access tokens
requestrequestPOSTPushed Authorization Request (PAR) endpoint, returns request_uri

How do I authenticate with the Corppass API?

Obtain an access token from the token endpoint using a client assertion, then send it as Authorization: Bearer <access_token> on each request.

1. Get your credentials

  1. Log in to the Corppass Developer Portal.
  2. Create a new client application and note the client_id.
  3. Upload your public JWKS URL and set the redirect URIs.
  4. Generate a client assertion JWT signed with your private key.
  5. Call the /token endpoint (POST) with client_id, client_assertion, and required scopes to receive an access token.
  6. Store the access token securely for use in API calls.

2. Add them to .dlt/secrets.toml

[sources.corppass_authorisation_api_source] token = "your_access_token_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 Corppass 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 corppass_authorisation_api_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline corppass_authorisation_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset corppass_authorisation_api_data The duckdb destination used duckdb:/corppass_authorisation_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline corppass_authorisation_api_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 userinfo and authorization_info from the Corppass 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 corppass_authorisation_api_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://id.corppass.gov.sg", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "userinfo", "endpoint": {"path": "userinfo"}}, {"name": "authorization_info", "endpoint": {"path": "authorization-info"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="corppass_authorisation_api_pipeline", destination="duckdb", dataset_name="corppass_authorisation_api_data", ) load_info = pipeline.run(corppass_authorisation_api_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("corppass_authorisation_api_pipeline").dataset() sessions_df = data.userinfo.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM corppass_authorisation_api_data.userinfo LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("corppass_authorisation_api_pipeline").dataset() data.userinfo.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 Corppass data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Corppass?

Request dlt skills, commands, AGENT.md files, and AI-native context.