Data

Overview

The Data endpoint is used to retrieve detailed information about a player. Most commonly, this method is invoked by BETCORE to obtain additional user data, such as the current balance, which can then be displayed or used for further processing within the Partner's system.

The main objectives of the Data method are:

User Data Retrieval: The primary goal of this method is to obtain up-to-date user information. This includes critical data such as the player’s balance, which is essential for ensuring accurate display of account details.
Secure Data Exchange: The request requires a valid JWT payload along with a PartnerUserId. This ensures that only authenticated and authorized requests can access sensitive user data, maintaining the overall security of the integration.
Support for Custom Integration: The method accepts additional parameters like TagId (used for identifying embedded WebFrame components) and optional ExtraData. This allows Partners to tailor the data retrieval process to their specific requirements and interface setups.

Request Parameters

Parameter		Data type	Description	Required
JWT payload
data		json string	Request data.	Yes
	PartnerUserId	string	Partner's player ID.	Yes
	TagId	number	Identification tag for an embedded iFrame page element; relevant for Partners using WebFrame as a client. See more on Tags.	Yes
	ExtraData	object	Additional data at the Partner's request.	No

Add the parameter

Authorization

to Headers，whose value is to concatenate the Token after the Bearer.

Example:

Authorization: Bearer ********************

Responses

🟢200Success

application/json

Body

ErrorCode

number

required

Error code of the response.

Message

string

required

Code description.

Value

object

optional

Balance

string

required

User balance.

Example

{
    "ErrorCode": 200,
    "Message": "Success",
    "Value": {
        "Balance": "7100.5"
    }
}

⚪102145User not found

Overview

Request Parameters

Request

Request samples

Responses