# (Legacy) Pre-FAPI 2.0 API Specifications

{% hint style="danger" %}
All Login and Myinfo apps must follow Singpass' [FAPI 2.0-compliant authentication API](https://docs.developer.singpass.gov.sg/docs/technical-specifications/integration-guide) 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](https://docs.developer.singpass.gov.sg/docs/technical-specifications/migration-guides/login-myinfo-v5-apps) early to avoid service disruptions.
{% endhint %}

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](https://docs.developer.singpass.gov.sg/docs/technical-specifications/singpass-authentication-api/1.-authorization-endpoint).

**Backend:**

* Step 4: Exchange auth code with ID token (involves client authentication) using [Token endpoint](https://github.com/SingpassPX/dev-docs/blob/main/technical-specifications/singpass-authentication-api/2.-token-endpoint).