Skip to main content

Players Migration

POST 
/api/players-data/v1/migrate/batch

The CRM depends on a minimum of information from the player for its correct operation.

Data players Microservice is in charge of storing all that information to be consumed by the different services of the platform. Also, every event that updates the player’s data; triggers events to the service that depends on this data. For this reason, it is necessary to migrate for the first time all the minimum information of the players; this will be necessary only once since later it will be updated through endpoints when the user executes some action, such as registration, data update, and so on.

It is necessary that the Casino sends us the players' information through the endpoint enabled in the Platform API Gateway.

Chunk Size

The recommended chunk size is 20,000 players. This value can change.

When this piece of players is received, they will be validated and a response object will be sent with the players that were validated correctly, and those that were not, errors will be sent with their respective property names. The players that were validated correctly will start processing in the background and will be saved in the database.

Compression

To reduce data size and accelerate data transfer, the data must be compressed using Gzip or Brotli. The Content-Encoding header is specified in the request:
  • Accept-Encoding: gzip
  • Accept-Encoding: br

Request​

Responses​

Ok