Documentation Changelog
This page logs significant updates to the Singpass developer documentation. For API spec changes (FAPI 2.0 migration), refer to the Changelog.
August 2026
3 Sep
Integration Guide
Authorization Request — session timeout guidance added; applications should accommodate up to 10 minutes for users to complete the Singpass authentication flow
24 Aug
SDP — App Management
Create Staging App, Create Production App, Edit Staging App, Edit Production App — FAPI 2.0 automatic migration notice added; explains the informational banner shown for apps with consistent FAPI 2.0 traffic; legacy API supported until 31 Dec 2026
24 Aug
Getting Started
App Logo — new sections added: logo preview shown during app creation wizard; logo pending-approval behaviour when a change request is under review
14 Aug
Technical Specifications
Client Assertion guide — iat/exp corrected to JSON numbers; compact JWT sample updated with correct payload (removed erroneous code field, added jti); validator tool description corrected (jwk → kid)
14 Aug
Integration Guide
Userinfo Request — iat field type corrected to Number; warning added that DPoP proof must include ath claim and htu must be /fapi/userinfo
14 Aug
Integration Guide
Handling the Redirect — successful redirect now correctly states three query parameters (code, state, iss)
14 Aug
Integration Guide
Parsing the ID Token — dead anchor #the-sub_account-claim corrected to #the-sub_attributes-claim
14 Aug
Migration Guides
Myinfo v4 migration guide — userinfo comparison table corrected from GET /userinfo to GET /fapi/userinfo
14 Aug
Getting Started
New page: Singpass Button Design Specification — button design specifications for developers and designers
14 Aug
Getting Started
New page: Singpass Brand Guidelines — brand guidelines consolidated into Getting Started
14 Aug
Products
Singpass Button Guidelines page removed — content moved to Singpass Button Design Specification under Getting Started
14 Aug
Products
Logo Download and Brand Guidelines page removed — content moved to Singpass Brand Guidelines under Getting Started
3 Aug
Pricing
Pricing page updated — Singpass Login is now priced by authentication form factor (QR/Passkey, Username/Password, SMS OTP); SFV pricing section added; Partner Support FAQ link added; references to the in-portal FAQ tab removed
3 Aug
Integration Guide
authentication_context_message allowable character set widened — now accepts all printable ASCII except <, >, \, and the backtick; max 100 characters unchanged
3 Aug
Pricing
Pricing guide updated — all four tabs on the Pricing Plan page now listed, including the Pricing Examples tab
3 Aug
SDP — App Management
Managing Drafts guide updated — "Saving..." indicator and "Draft saved" label for auto-save described
July 2026
28 Jul
SDP — App Management
App name must be 100 characters or fewer — documented in App name & purpose and Create Staging App
28 Jul
SDP — App Management
Client External ID is read-only and cannot be changed after app creation — callout added to Edit Staging App and Edit Production App
28 Jul
Integration Guide
Code samples use the staging endpoint (stg-id.singpass.gov.sg) — callout added to Authorization Request and Token Exchange
28 Jul
Technical Concepts
Do not pin Singpass TLS leaf certificates — warning added to OpenID Provider Configuration
28 Jul
Migration Guides
Duplicate app recommended as preferred migration path — updated in Myinfo v3 migration guide and Myinfo v4 migration guide
15 Jul
SDP — App Management
New page: Managing Drafts — auto-save, 30-day expiry, 7-day email reminder
14 Jul
Technical Specifications
Legacy Singpass Authentication API documentation retired — superseded by FAPI 2.0 Integration Guide
June 2026
16 Jun
Migration Guides
Login/Myinfo v5 migration guide expanded with guidance on replacing custom scheme URLs with Universal Links / App Links
15 Jun
Getting Started
New page: App Logo requirements — PNG, 256–512px, max 200KB, no padding. Effective August 2026
10 Jun
Getting Started
User Journey — 4th template added for Login with Mandatory Face Verification (high-risk, submit via partner support portal)
Breaking change (24 Jun): The userinfo endpoint URL has changed to /fapi/userinfo. Update your integration if you are using a hardcoded path.
May 2026
28 May
Technical Concepts
6 May
Integration Guide
Userinfo request fully rewritten for FAPI 2.0 — DPoP header, ath claim, person_info structure
April 2026
21 Apr
Technical Concepts
Client Assertion expanded with additional JWT payload requirements; DPoP minor corrections
20 Apr
Integration Guide
Error code corrected to upstream_dependency_error in Token Exchange and Userinfo Request
18 Mar
SDP — Billing
New page: How to view entity transactions
March 2026
24 Mar
Migration Guides
Myinfo v4 migration guide — client assertion incorrectly required code parameter; fixed
5 Mar
Migration Guides
Login/Myinfo v5 migration guide — user.identity scope clarified as available to all app types, not Login only
February 2026
23 Feb
Technical Concepts
DPoP guide substantially expanded — full JWT structure, per-request requirements, key lifecycle rules
13 Feb
Integration Guide
authentication_context_type full values table added — CPF, Banking, Other FIs, Telcos, generic
10 Feb
Technical Specifications
FAPI 2.0 documentation published — Integration Guide, Technical Concepts, Migration Guides. All new apps require FAPI 2.0. Existing integrations must migrate by 31 December 2026.
6–24 Feb
Testing
Myinfo test personas updated across multiple rounds — refreshed persona data and CSV download
Last updated
Was this helpful?