Log In Using Custom ID¶
Log the Player in using a custom unique identifier. Returns a JWT token that is tied to the player and should be used to authenticate on subsequent requests.
Note
A Player will automatically be created if they do not exist.
HTTP request¶
POST https://megamify.com/api/v1/player/login/custom/
Headers¶
See Security section of the API Reference.
Body¶
| Name | Required | Type | Description |
|---|---|---|---|
| game | True | int | The Game ID to login to |
| custom_id | True | int | The Player’s Custom ID |
Response¶
| Name | Type | Description |
|---|---|---|
| token | string | The JWT token |
| user | User object | The User object |
Important
To make any Client API call (apart from login), the client must be signed into Megamify, but you can do that with zero-friction sign-in calls using Device ID or a locally generated GUID (Custom ID). Each unique player must sign into a distinct account, but by using logins that can cross devices (like Facebook, Google, etc.), you can consistently sign the player into the same account from any device.