Comment on page
API protocol description and utilities for Desktop integration
Each game will receive a
rei keywhen launched under the
rei keywill be required to get the user session
JWTon a separate request. The player session will be kept alive by the Game Developer using the
Get Refresh Tokenrequest.
JWTwill be required
Bearer Tokenon every request.
The following methods will be used only for
Elixir Launcher Gamesto keep a user session.
As described above, some will notice a dependency on Elixir Launcher to test the complete integration. But for local development, we facilitate the following endpoint, restricted only for Development Keys. That allows game developers to generate verifiable reikeys for development purposes.
Note that the reikey generated with this endpoint will grant access to the Game Owner account. So any modification applied to this account (new username, new wallet, friends...) will be accessible in development mode. This accelerates integration and removes dependencies.
You can also log in with different accounts. To do so, you'll need to ask the Support Team to whitelist any of your developers and provide you with their
playerId. Two use cases can be extrapolated from this utility:
- For those games that need to log in several users to test multiplayer features or have an anti-cheat system that uses OpenID.
- For bugs and tickets from your community. You'll be able to log in with bugged accounts to fix the issue.
Get User Credentials
Refresh User token