Introduction

This page is intended to be a quick-start guide for developers who seek to implement a solution for authentication. The page will outline a quick-start guide for using our APIs in this context, as well as some considerations that are good to know.

We emphasize that even though this guide contains most of the information needed to set up authentication with BankID, you'll need a commercial agreement with one of our partners in order to go live. We encourage to do this as early as possible. For more information on this, check out our getting started guide.

Using our APIs for Authentication

Using the approach outlined below will return the end user's identity in the form of an ID token. The information contained in this token may be used to match the user against an existing customer profile, and thus allowing the user to enter as his/her identity has been confirmed by BankID.

Step	What you do	Endpoint	Method	Considerations	Remarks
1	Get the key properties of the OIDC provider	openid-configuration	GET
2	Build the authorization URL, and redirect the user to the authorization endpoint	authorize	GET	In the callback, make sure to check for error and matching states	This is where the end user interacts with the BankID IDP selector and gives credentials for authentication (see user experience for details)
3	Exchange authorization code for tokens	token	POST	Check matching `nonce`	Use the ID Token to identify the user. For other services, such as electronic signing or digital onboarding, also note that you can... Use the Access token to access additional services provided by the BankID OIDC Provider, such as signing documents online Use the Refresh token to retrieve new access tokens Verify and store the BankID Proof token to prove that an end-user has authenticated with BankID Netcentric or BankID on Mobile.
4	Fetch our public keys and use these to validate token signatures	jwk	GET