Pular para o conteúdo principal

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

The request body must be compressed. A plain, uncompressed JSON request will be rejected. Compress the JSON array of players with Gzip or Brotli, send the compressed bytes as the raw (binary) request body, and set the Content-Encoding request header to match:
  • Content-Encoding: gzip
  • Content-Encoding: br
Most API clients (including Postman) do not compress the body for you. Setting the header alone only labels an uncompressed payload and the request will fail. Compress the body first (for example with the gzip CLI or a small script), then send the compressed file as the binary body.

Request​

Responses​

Ok