(Legacy) Pre-FAPI 2.0 Singpass API Specifications

All Login and Myinfo apps must follow Singpass' FAPI 2.0-compliant authentication API by 31 Dec 2026.

The specifications on this page apply to you only if you are maintaining an existing Login / Myinfo (v5) integration. We encourage you to migrate early to avoid service disruptions.

The purpose of this guide is to describe the necessary APIs that Relying Parties (RPs) must invoke to facilitate an Open ID Connect (OIDC) authentication for a Singpass user via the Redirect Authentication Flow.

RPs are to implement the following steps:

Frontend:

• Step 1a: Redirect to Authorization endpoint.

Backend:

• Step 4: Exchange auth code with ID token (involves client authentication) using Token endpoint.