Get claims about the authenticated end-user, using an Access Token. Claims that do not exist will be omitted. This endpoint uses your Custom Domain.
The contents of the response depend on the scopes granted to the client:
- All responses will always contain the sub claim.
- If the profile scope is granted, the name,
given_name, family_name, profile_picture, and locale claims will be returned.
- If the email scope is granted, the email and
email_verified claims will be returned.
- If the phone scope is granted, the
phone_number and phone_number_verified claims will be returned.
You can call this endpoint via both GET and POST.
This endpoint implements the OpenID Connect Core 1.0 UserInfo Endpoint.
Response
The subject of the token. This is a unique identifier for the user.
The end-user’s phone number. This claim is only returned when the client is granted the phone scope.
Indicates whether the end-user’s phone number has been verified. This claim is only returned when the client is granted the phone scope.
The end-user’s email address. This claim is only returned when the client is granted the email scope.
Indicates whether the end-user’s email address has been verified. This claim is only returned when the client is granted the email scope.
The full name of the end-user. This claim is only returned when the client is granted the profile scope.
The given (first) name of the end-user. This claim is only returned when the client is granted the profile scope.
The middle name of the end-user. This claim is only returned when the client is granted the profile scope.
The family (last) name of the end-user. This claim is only returned when the client is granted the profile scope.
The URL of the end-user’s profile picture. This claim is only returned when the client is granted the profile scope.
The end-user’s locale, typically in the form of a language tag (e.g., “en-US”). This claim is only returned when the client is granted the profile scope.
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we
may ask for this value to help identify a specific API call when helping you debug an issue.
The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values
equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.