# [JWT] Silent authentication

Exchanges a platform-specific authentication credential (a session ticket/exchange code/authorization token) from Epic Games, Steam, or Xbox for the JWT in your project (projectId).

You will get the link to redirect the user to your project.

To enable silent authentication, use the instruction.

Endpoint: GET /social/{cross_social_provider_name}/cross_auth
Version: v1

## Query parameters:

  - `projectId` (string, required)
    Login project ID from Publisher Account.

  - `login_url` (string)
    URL to redirect the user to after account confirmation, successful authentication, two-factor authentication configuration, or password reset confirmation. Must be identical to the Callback URL specified in the URL block of Publisher Account. For the scenario of a login error, the value should be identical to the the Error callback URL specified in the URL block of Publisher Account. To find the settings, go to Login > your Login project and select the Callback URLs section in the upper block. Required if there are several Callback URLs.

  - `fields` (array)
    List of parameters which must be requested from the user or social network additionally and written to the JWT. The parameters must be separated by a comma. For example, email.

When the email is requested and the social network did not respond with the email value:
* the user will be asked to input their email in the corresponding form if you integrated Login Widget,
* the user must be asked to input their email in the corresponding form of your own interface if you integrated Login API. Please send the URL of this form to your Customer Success Manager.

After the email is inputted, the user receives an email confirmation message. To disable email confirmation, please contact your Customer Success Manager.

  - `session_ticket` (string)
    Required. A credential received from a platform during user authentication, encoded according to the Base64 standard. Depending on the social provider, it can be:   - an exchange code for Epic Games   - a session ticket for Steam   - an Xbox authorization token in the following format: -;XSTSToken

  - `payload` (string)
    Your custom data. The value of the parameter will be returned in the payload claim of the user JWT. Recommended maximum length less than 500 characters. Note, that this parameter is only available if you use a custom user data storage.

  - `with_logout` (string)
    Shows whether to deactivate the existing user JWT values and activate the one generated by this call. Can have the following values:
* 1 to deactivate the existing values and activate a new one,
* 0 to keep the existing values activated.

  - `app_id` (string)
    Your app ID on the platform. Required if the platform where the user is authorized is Steam.

  - `code` (string)
    Code received from the platform.

  - `is_redirect` (boolean)
    Shows how the Xsolla Login server should respond. If you set:
* true value, the Xsolla Login server returns the 302 response code. URL for user redirection with user JWT will be in the Location header.
* false value, the Xsolla Login server returns the 200 response code. URL for user redirection with user JWT will be in the response body.

  - `no_user_creation` (boolean)
    Do not create new user if they not exist yet. Existing users will be authorized as usual

  - `deployment_id` (string)
    The deployment ID that the client is trying to authenticate with in Epic Games. This will impact interactions with other services that require a deployment. If the deployment is not public, only users who have been entitled will be able to log in. For more information on deployments and deployment IDs see Product, Sandbox, and Deployment IDs.
Note: You must use this unique identifier to use the Ecommerce APIs, and to request access tokens used by game clients.

## Path parameters:

  - `cross_social_provider_name` (string, required)
    Name of the platform the user authorized in. Can be steam, xbox, epicgames.

## Response 200 fields (application/json):

  - `login_url` (string, required)
    URL with the token parameter to redirect the user to your project.

## Response 400 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.

## Response 404 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.

## Response 422 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.

## Response 429 fields (application/json):

  - `error` (object, required)

  - `error.code` (string, required)
    Error code.
    Example: "003-061"

  - `error.description` (string, required)
    Error description.
    Example: "Object not found."

  - `error.details` (object)
    Additional information.


## Response 302 fields