Developer Docs for Singpass
  • INTRODUCTION
    • Overview of Singpass
    • Understanding the basics of OIDC
  • GETTING STARTED
    • Onboarding Checklist
    • Understanding the Basics
      • Discovery Endpoint
      • Scopes
      • Setup JSON Web Key Store (JWKS)
      • Configure Singpass Application on SDP (In-Progress)
      • Configure Singpass Application
      • Request for Staging Account and Staging Mobile App
    • Start Integration
    • Custom Integration
      • Demo Application Setup
      • Invoke Authorization Endpoint
      • Setup Client Assertion
      • Invoke Token Endpoint
  • MORE INFOMATION
    • Contact
    • FAQ
Powered by GitBook
On this page
  • Step 1: Login to Singpass Developer Portal
  • Step 2: Create a Login Linkup Request
  • Step 3: Configure Application
  • Step 6: Save Application Settings
  • Next steps
  1. GETTING STARTED
  2. Understanding the Basics

Configure Singpass Application

PreviousConfigure Singpass Application on SDP (In-Progress)NextRequest for Staging Account and Staging Mobile App

Last updated 10 months ago

Every Singpass Application is assigned a unique identity known as Client ID that will be required when calling Singpass’s Endpoint. Login to to create a new Singpass Application or use an existing application client’s ID for the integration.

Refer to the following guide for configuration of Application settings.

Step 1: Login to

  • Click on "Login with Singpass".

  • Select Password Login.

  • Input the following credentials and click "Login".

Singpass ID : S9992672D Password : Spcp1111

Step 2: Create a Login Linkup Request

  • Click the “View” button via Dashboard to submit a new linkup request. Alternatively, you can access the linkup request button via APIs > My Linkup Requests.

  • Select “Login” as the Singpass APIs and click "Select".

  • Select “No, onboarding as a new digital service” and click "Proceed".

  • Configure App Name, App Description, and Target Implementation Date

Configure App Name

This application name is the name of your digital service/application. This will appear on the consent page that your users will see when they give consent to login to your digital service. For testing purposes, please follow the following naming convention:

[Your Name]_[App Name]


Example of consent page when App Name is configured as Test App.

Configure App Description

Description of your digital service/application. Describe the use case for your app and what it does for Singpass’s administrative purposes.

Configure Target Implementation Date

Target Implementation Date of your digital service/application. Can only be today or a future date

  • Review the details, acknowledge the fees involved, and declarations. Once done, click "Confirm & Submit".

  • Linkup Requests will be auto-approved, and an App will be created.

Step 3: Configure Application

  • Click the “View” button to configure the Application immediately once the linkup request is auto-approved. Alternatively, you can access the respective Application via APIs > My Apps. Search for your app name.

  • Configure Application

Configure Production URL

Indicate the URL that hosts your Singpass Login Button

Configure Support Email

Indicate the email addresses that will be receiving updates regarding this application

  • Fill in the Application's Staging Environment Configuration Details. This section is not relevant, you may fill in the details as indicated.

  • Fill in the Application's Production Environment Configuration Details.

Client ID field will be populated once the app has been created successfully.

NDI Sync Status field will be populated once the app has been created successfully. The field will be shown as synced if creation was successful else it will be displayed as not synced or synced failed.

Configure Callback URL (s)

A redirect/callback URL is a URL in your application that Singpass will be used to redirect users after they have been authenticated or when the ID Token is being returned.

If you are using the demo Singpass Application code, your redirect URL should be configured as [Your domain]/callback. Example: Singpass demo app is hosted on Netlify

Domain: https://singpassdemoapp.netlify.app Callback file created: callback Hence, in the callback URL field, it will be indicated as https://singpassdemoapp.netlify.app/callback

Configure Origin (s)

This field is no longer relevant. Can be set to https://www.testing.com

Configure JWKS Endpoint/JWKS Object

  • Provide a JWKS in a JSON format or

For configuration with JWKS Endpoint

  • Select JWKS Endpoint and provide the JWKS Endpoint

For configuration with JWKS Object

  • Select JWKS Object and provide the JWKS Object

Step 6: Save Application Settings

  • Click Update App. Review changes and click Confirm Changes. Once saved, the client ID will be populated. This is a unique identity known as that will be required when calling Singpass’s Endpoint.

Next steps

Profile Type field has been defaulted to direct_pii_allowedas displayed as NRIC/UUID. Refer to .

Authentication Flow has been defaulted to 1-Factor Authentication. Refer to .

Configure JWKS with the public keys set in the . This will be used by Singpass for verification and encryption purposes. You can do so only via ONE of the following forms:

Host the JWKS on a publicly accessible URL. This endpoint must be compatible with

required for testing purposes

If you already have the staging account credential and staging mobile app setup, to call Singpass's Authorization Endpoint

Client Profile Type
Authentication Types
previous step
Singpass’s service level expectations
Request for Staging Account and Staging Mobile App
Create a Singpass Login Button
Singpass Developer Portal
Singpass Developer Portal