API Specs

OAuth2

Start OAuth-style authorization flow

get
/authorize

Initiates the authorization flow. Verifies client_id, redirect_uri, and optional state. If valid, redirects to the consent/verification page with a auth_request_id for further processing. Partner can then exchange the authorization code for an access token.

Query parameters
response_typestring · enumRequiredPossible values:
client_idstringRequired
redirect_uristring · uriRequired
statestringOptional
noncestringOptional
scopestringRequired

Space-separated list of scopes. Must include "openid" for OpenID Connect authentication. Use "offline_access" to request refresh tokens.

Example: openid offline_accessPattern: ^openid( offline_access)?$
Responses
get
/authorize

No content

Exchange authorization code for external user ID

post
/token

After successful palm verification, exchanges an authorization code for the corresponding external_user_id.

Body
grant_typestring · enumRequired

OAuth 2.0 / OIDC grant type

Possible values:
client_idstringRequired
client_secretstringRequired
codestringOptional

Authorization code (required for authorization_code grant)

refresh_tokenstringOptional

Refresh token (required for refresh_token grant)

redirect_uristring · uriOptional

Redirect URI (required for authorization_code grant)

Responses
post
/token

Retrieve user profile from Access Token

get
/userinfo

Standard OIDC UserInfo endpoint. Returns claims about the subject (sub) represented by the Bearer Access Token presented in the Authorization header.

• Requires scope=openid. • Only returns claims the user originally consented to (e.g., email, picture)—never private biometric templates.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Responses
get
/userinfo

Last updated

Was this helpful?