This webhook is called when Pley needs to know which Pley game user to use based on a scope user ID. This happens for example when a game is launched.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
New!
Pley is currently experimenting with allowing multi-enviroment testing for the
allocate-game-userwebhook, so you can see in the release track in the header.
X-Pley-ReleaseTrackis a header with three possible values:production,open-testingorclosed-testingdepending on which release track the game is currently running on.This allows you to test the full flow without creating a testing game in the Game Manager by setting up a proxy that forwards requests to the correct enviroment depending on the header values.
Webhook Info
Pley uses the 'Standard Webhook"-specification format.
Webhook Cache
Webhook calls to Pley are cached for 24 hours, meaning Pley does not call the endpoint with the same parameter within 24 hours (caching happens for any 200 OK respose).
Webhook Caching can be disabled in the Game Manager under Release Track -> Webhook. This setting is per release track. Disabling caching on open-testing does not affect the production track.