Auth

Overview

The Auth endpoint is used for authenticating a user within the Partner's ecosystem. It is primarily used when the Partner needs to verify and refresh a user's authentication credentials.

The main objectives of the Auth method are:

User Authentication: It validates the refresh token that the Partner originally provided during the initialization of the WebFrame. This process confirms the user's identity and ensures that the authentication session is legitimate.
Token Renewal: The method generates and returns a new, valid refresh token along with other user details. This updated token is essential for maintaining an active and secure session for the user.
User Registration (if needed): If the user is not already present in the system, the method helps in registering the new user during the authentication process while ensuring that appropriate account parameters (such as PartnerUserId and CurrencyCode) are set.
Session Integrity: By validating token authenticity and reissuing credentials, the method ensures that subsequent API calls are made by authenticated and authorized sessions, maintaining the overall security and data integrity within the BETCORE system.

In summary, the Auth endpoint is critical for securely managing user sessions by validating refresh tokens, reissuing updated tokens, and, if necessary, registering new users. This helps establish a trusted and consistent authentication flow between the Partner's client and the BETCORE API.

Request Parameters

Parameter		Data type	Description	Required
JWT payload
data		json string	Request data.	Yes
	RefreshToken	string	The refresh token that the Partner passed to the WebFrame when it was initialized.	Yes
	TagId	number	Identification tag for an embedded iFrame page element; relevant for Partners using WebFrame as a client. See more on Tags.	No

Responses

🟢200Success

application/json

Body

ErrorCode

number

required

Error code of the response.

Message

string

required

Code description.

Value

object

optional

RefreshToken

string

required

New current refresh token.

Requirements for the refresh token generation:
Latin letters (A-Z, a-z)
Numbers 0-9
Hyphen "-", period "."
Length from 10 to 1000 characters

PartnerUserId

string

required

Partner's user ID.
Each user currency wallet MUST have a unique PartnerUserId.

CurrencyCode

string

required

Player's account currency code.

IsTest

boolean

required

Test user flag.
The parameter is saved at the moment of the first bet and further requests with a different parameter value are considered erroneous.
The user MUST have an unchangeable flag of being a test user.

Example

{
    "ErrorCode": 200,
    "Message": "Success",
    "Value": {
        "RefreshToken": "456789-abcdef-1d2e3r4-8tbt9r",
        "PartnerUserId": "SomeUserId100",
        "CurrencyCode": "USD",
        "IsTest": true
    }
}

⚪103752Invalid request parameters

⚪103811JWT token validation failed

⚪103805Invalid token

⚪103799General API Error

Overview

Request Parameters

Request

Request samples

Responses