Dear Partners,
As part of our ongoing commitment to strengthen security standards and align with global security best practices, Singpass will be adopting FAPI 2.0 for all APIs, including Login and Myinfo.
We are now pleased to announce that the Singpass FAPI 2.0 staging environment is now available.
What you need to know:
- Existing vs. New Apps:
- New staging and production apps created after production launch (Mid-Feb 2026) must adopt FAPI 2.0.
- Existing apps must migrate to and adopt FAPI 2.0 by 31 Dec 2026.
- Privacy enhancements to Singpass Login apps:
- You can now request the user's principal name, mobile number, and email address in the ID token via the Singpass Developer Portal.
- For new FAPI 2.0-compliant Login apps created after production launch (Mid-Feb 2026), requesting for principal name, mobile number or email address will now trigger a user consent screen to ensure transparency.
- Engagement Sessions: Technical briefings will be held in March 2026. Registration details will follow shortly.
What you need to do:
- Access the FAPI 2.0 Integration Guide to test your setup against the new FAPI staging endpoints.
- Verify your application’s support emails at https://go.gov.sg/sp-poc-update to receive critical updates.
Timeline Summary
| Date | Milestone |
| 19 Jan 2026 | Singpass FAPI 2.0 staging environment is now live. |
| Mid-Feb 2026 | Singpass FAPI 2.0 production environment will go live. |
| 30 Sept 2026 | Myinfo v3/v4 decommissioned. |
| 31 Dec 2026 | All APIs must be FAPI 2.0 compliant. |
Thank you for your continued partnership in strengthening security and trust across all digital services. If you have any questions, please reach out to our support team here.
Best regards,
Singpass Partner Experience team
Comments
0 comments
Please sign in to leave a comment.