Players Migration Feedback
POST/api/players/v1/migration/feedback
This is a webhook endpoint implemented by the operator, Gamanza Engage calls it to deliver the result of a completed player migration batch. The request body includes the migrationTasksId (matching the task returned when the batch was submitted), a count of successfully stored players, a count of errors, and a detailsURL pointing to a streamed, Gzip-encoded JSON file with per-player error details. The operator must return HTTP 204 No Content to acknowledge receipt; any other response is treated as a failure. If errorsTotal is greater than zero, the operator should retrieve and process the error details from detailsURL to identify players that failed validation and may need to be resubmitted. Migration progress is not surfaced in the Gamanza Engage dashboard, however, once a batch completes successfully, the migrated players will become visible in the platform's CRM player list.
Request
Responses
- 204
- 400
- 401
- 404
- default
No content
Bad Request
Unauthorized
Not Found
An unexpected error response.