Skip to main content
User lifecycle is how your game connects a player to a HyperX user inside your project.

Choose a Login Method

Start a Guest User

StartGuestSession signs in instead of creating a duplicate user when the same guest token already exists, then returns a PlayerSession. For shipped games, choose a guest token strategy that matches your recovery policy. If players need recovery after device changes, provide social login or custom account linking. The existing token-based API remains available for advanced migration flows and compatibility adapters that manage access tokens directly.

Custom Accounts

Usernames must be unique within the project. Duplicate names, invalid passwords, and invalid values fail with HyperXServerException.

Social Login

Google, Apple, and Facebook login pass short-lived tokens from provider SDKs to HyperX. HyperX validates them with credentials registered in Console.
You can link a social identity to an existing HyperX user.
See Provider Integrations for provider app setup and Console credentials.

Refresh a Session

Login responses include AccessToken for API calls and RefreshToken for session renewal.
Store refresh tokens securely. If the refresh token expires, sign in again.

Current User

You can confirm the same user in Console on the Users page.

Name and Characters

The representative character is used for profile display and the default Character Data convenience APIs. Data for non-representative characters can be saved and loaded by passing the character ID explicitly.

Logout

To end every active session:

Account Deletion and Recovery

When a player requests account deletion, the account status changes to deletion_requested and HyperX records the scheduled deletion time. Operators can review the request in Console Users, then finalize or cancel it according to your retention policy.
Canceling a deletion request requires a recovery token. Deliver that token through your authentication or support flow.
If the current signed-in session receives the token, it can cancel deletion directly.
Finalized deleted accounts cannot sign in or refresh sessions. Purchases, refunds, audit logs, and other retention-sensitive records can remain according to the project’s data policy.