PASAR API

🇸🇬 Singpass Myinfo ~ consent-based KYC personal-data retrieval

← directory

National KYC source: with user consent, retrieve verified identity, demographic, income (NOA), CPF and HDB data straight from government records after Singpass login. Partner onboarding + app registration required; sandbox available. SG-first.

View docs ↗ More Auth & identity APIs

Get started

# Singpass Myinfo ~ consent-based KYC personal-data retrieval needs OAuth credentials ~ get yours at:
# https://docs.developer.singpass.gov.sg/docs/products/singpass-myinfo
curl 'https://api.myinfo.gov.sg' \
  -H 'Authorization: Bearer YOUR_TOKEN'

AI prompt

I'm integrating a Singapore API into my app.

API: Singpass Myinfo ~ consent-based KYC personal-data retrieval
Provider: GovTech Singapore (Singpass)
Auth: requires OAuth credentials (sign up: https://docs.developer.singpass.gov.sg/docs/products/singpass-myinfo)
Pricing: free
Base URL: https://api.myinfo.gov.sg
Important note: National KYC source: with user consent, retrieve verified identity, demographic, income (NOA), CPF and HDB data straight from government records after Singpass login. Partner onboarding + app registration required; sandbox available. SG-first.

Source: GovTech Singapore (Singpass) (https://docs.developer.singpass.gov.sg/docs/products/singpass-myinfo)
Source type: Provider API or developer docs
Endpoint type: Provider API base URL
Integration difficulty: Regulated setup
Last checked: 2026-06-29
Production caveat: You are pulling government-verified personal data (NRIC, income, CPF). Production access is approval-gated; request only the attributes you need, honour each consent scope, and treat everything you store as PDPA-regulated with minimal retention.

Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.

Related Auth & identity APIs