https://login.xsolla.com/api
This section describes API calls for working with Login. Set up your Login project in Publisher Account before sending requests.
You have access to the following Login project types in Publisher Account:
To find more information on it, see Cross-platform account feature.
Login API supports the following token types:
You can determine whether an API call is client or server-side by the scheme of authentication:
Authorization
header: Bearer <user_JWT>
header, where <user_JWT>
— is the user token.X-SERVER-AUTHORIZATION: <server_JWT>
, where <server_JWT>
— is the server token.To get the token, send one of the following requests:
After JWT authentication, the user is redirected to the Callback URL with a token in a query-parameter: <Callback URL>?token=<User token (JWT)>
.
After OAuth 2.0 protocol-based authentication, send the Generate JWT request to the Xsolla Login server to exchange the received code
parameter for a user token (access_token
).
To get a server token:
On the back end of your application, implement a method to get the server JWT using the Generate JWT API call. The request must contain the following parameters:
grant_type
is the type of getting JWT, pass the client_credentials
value.client_secret
is the secret key that is received when you set up the server OAuth 2.0 client.client_id
is the client ID received when you set up the server OAuth 2.0 client.To prevent Xsolla system overloads and protect against sudden spikes in incoming traffic, Xsolla limits the number of requests received by the Xsolla API within a specified period of time. If the limit is exceeded, the Xsolla API returns an HTTP response with the 429
status code.
Rate limits vary by method, IP-address, authentication scheme, and other factors.
Rate limits for server-side methods are applied to methods with server-side authentication — methods that are called with the X-SERVER-AUTHORIZATION: <server_JWT>
header, where <server_JWT>
is the server token.
Rate limits for client-side methods are applied to methods without authentication or with client-side authentication — methods that are called with the Authorization: Bearer <user_JWT>
header, where <user_JWT>
is the user token.
Example of a method with server-side authentication:
Example of a method with client-side authentication:
Rate limits for client-side methods do not change and are necessary to prevent brute-force attacks. The maximum request rate for server-side methods is higher than for client-side methods. You can refer to the recommendations on how to manage rate limits in the documentation.
Every token has a JWT format and contains a definite information in a payload.
A token will contain the main claims after authentication or email address confirmation. Presence of these claims does not depend on the user database and authentication call.
Claim | Type | Required | Description |
exp |
Unix Timestamp | Yes | Date and time of token expiration. Default expiration time is 24 hours. You can change expiration time for every Login project. |
iss |
string | Yes | Service that signed the token: https://login.xsolla.com . |
iat |
Unix Timestamp | Yes | Date and time of giving the token. |
sub |
string (UUID) | Yes | User ID written on the Xsolla Login server side. |
groups |
array | Yes |
The list of groups the user is in. Every group is written in the following format:
There can be only one default group. This group initially includes all users before they are distributed into different groups. |
xsolla_login_project_id |
string (UUID) | Yes | Login project ID. |
type |
string |
Authentication option:
There can be only one default group. This group initially includes all users before they are distributed into different groups. |
|
avatar |
string | User avatar URL. | |
username |
string | Username. | |
publisher_id |
integer | ID of a merchant who owns a Login project. | |
email |
string | User email address. | |
payload |
string | Additional information that is passed in the payload parameter during authentication. | |
promo_email_agreement |
boolean |
May have one of the following values:
true value by default.
To add the feature to the registration form of the Login widget:
|
|
connection_information |
string | Shows whether the user confirmed their birth date or not. Confirmation is made via the okname service. |
Claims that are contained in the token after authentication if you use PlayFab storage.
Claim | Type | Required | Description |
external_account_id |
string | Yes | User PlayFab ID. |
session_ticket |
string | Yes |
A SessionTicket parameter received during an authentication request or requests to the PlayFab API. A token contains the claim if you authenticate users via the OAuth 2.0 protocol and pass the |
entity_token |
string | Yes | An EntityToken.EntityToken parameter. |
entity_type |
string | Yes | An EntityToken.Entity.Type parameter. Can have only the title_player_account value. |
entity_id |
string | Yes | An EntityToken.Entity.Id parameter. |
Claims that are contained in the token after authentication if you use custom storage.
Claim | Type | Required | Description |
provider |
string | Yes | Name of a social network used for authentication. If the user authenticates via username and password, the claim has the xsolla value. |
external_account_id |
string | User ID on your server side. | |
partner_data |
Data of any type returned by your server in the response body during authentication. To enable the transmission of this claim, contact your Customer Success Manager or email to csm@xsolla.com | ||
social_access_token |
Access token of the social network through which the user was authenticated. To enable the transmission of this claim, contact your Customer Success Manager or email to csm@xsolla.com. |
Claims that are contained in the token after authentication via a social network. Presence of these claims does not depend on the user database.
Claim | Type | Required | Description |
provider |
string | Yes | Name of a social network used for authentication. |
id |
string | Yes | User ID in a social network. |
is_cross_auth |
boolean | Shows that the silent authentication request is in progress. | |
social_access_token |
string | Social network account access_token parameter used for authentication. Contact your Account Manager to set up the feature. |
|
picture |
string (URL) | Link to the user profile picture in a social network. | |
birthday |
date (RFC3339) | User birth date in a social network. | |
gender |
string | User gender in a social network. | |
name |
string | User nickname in a social network. |
The server token is passed in the X-SERVER-AUTHORIZATION
header.
The token payload contains information about resources owned by the OAuth 2.0 client. The token has access to calls with server-based authentication for these resources.
Claim | Type | Required | Description |
xsolla_login_project_id |
string (UUID) | Yes | ID of a Login project that owns the OAuth 2.0 client. |
resources |
array | Yes |
List of resources owned by a OAuth 2.0 client. Possible types of resources:
Every group is written in the following format:
|
jti |
string | Yes | Unique token ID. |
To validate the JWT, use the following Login API calls:
Notice
Do not reveal your secret key to anyone. If it was compromised, please update it.
Refer to the documentation for information about Xsolla Login API errors.