Singpass Python API Docs | dltHub

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

Last updated:

Singpass APIs provide OpenID Connect authentication and identity services for relying parties to verify user identities and access information. The REST API base URL is https://id.singpass.gov.sg and all requests require DPoP proof and token authentication via DPoP header and Authorization header.

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 Singpass data in under 10 minutes.


What data can I load from Singpass?

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

ResourceEndpointMethodData selectorDescription
person_v4/com/v4/person/{sub}/GETRetrieves Person data (v4).
person_sample_v4/com/v4/person-sample/{uinfin}/GETRetrieves sample Person data (v4).
token_v4/com/v4/tokenPOSTExchanges authorization code for tokens.
authorize_v4/com/v4/authorizeGETInitiates OAuth2 authorization flow.
person_sg_verify_v2/sgverify/v2/person/{uuid}/GETRetrieves SG-Verify person data.

How do I authenticate with the Singpass API?

Singpass APIs use OAuth 2.0 with DPoP (Demonstrating Proof-of-Possession). Requests require an 'Authorization' header with the 'DPoP' prefix and a 'DPoP' header containing a signed DPoP proof JWT.

1. Get your credentials

To obtain access and credentials for Singpass APIs, follow these steps: 1. Log in to the Singpass Developer Portal (SDP) at https://developer.singpass.gov.sg using your Singpass account. 2. Ensure your Corppass Administrator has assigned your organization’s UEN and the 'Singpass API Developer and Partner Portal' digital service access to your account. 3. Within the portal, navigate to your app configuration page. 4. Create a new app (Staging or Production). 5. Upon app creation, you will be provided with a 'client_id' (App ID), which acts as your primary identifier for authentication. Note that Singpass APIs use OIDC/FAPI 2.0 standards, which rely on asymmetric authentication (JWKS/private keys) rather than static API keys.

2. Add them to .dlt/secrets.toml

[sources.singpass_source] client_id = "your_app_id_from_sdp" jwks_url = "https://your-domain.com/.well-known/jwks.json" redirect_uri = "https://your-domain.com/callback"

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 Singpass 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 singpass_pipeline.py

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

Pipeline singpass_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset singpass_data The duckdb destination used duckdb:/singpass.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 pushed_authorization_request_endpoint and token_endpoint from the Singpass 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 singpass_source(client_assertion=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://id.singpass.gov.sg", "auth": {"type": "api_key", "api_key": client_assertion, "name": "Authorization", "location": "header"}, }, "resources": [ {"name": "person_v4", "endpoint": {"path": "com/v4/person/{sub}"}}, {"name": "person_sg_verify_v2", "endpoint": {"path": "sgverify/v2/person/{uuid}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="singpass_pipeline", destination="duckdb", dataset_name="singpass_data", ) load_info = pipeline.run(singpass_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("singpass_pipeline").dataset() sessions_df = data.person_v4.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM singpass_data.person_v4 LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("singpass_pipeline").dataset() data.person_v4.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 Singpass 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 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 Singpass?

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

Available Pipelines