Rejecting a Game Hub login
What's new
POST /v1/users/authorize/reject ends a Game Hub login attempt that cannot go ahead. The game server posts a required reason — not_eligible, banned, or rejected — along with the nonce from the authorization deep link, and gets back an error_url that explains the failure to the player.
The three reasons cover the cases a game server turns a login down for: the player hasn't unlocked hub access yet, the game account is suspended, or the server declined for some other reason.
Impact
Passing the nonce cancels the waiter on the Game Hub page, so a declined login ends right away instead of hanging until the page times out. Opening the returned error_url is optional — the game client can show its own error and the login still resolves as rejected.
Changes
| Resource | Change |
|---|---|
| reject_authorization | New endpoint. Takes a required reason and an optional nonce (up to 255 characters), returns error_url |
| Components | Added the RejectAuthorizationRequest and RejectAuthorizationResponse schemas and the RejectAuthorizationReason enum (not_eligible, banned, rejected) |
Upgrade
- No action required. Existing authorize_user calls are unaffected.
- Call the endpoint wherever your server already refuses a hub login, and pick the reason that matches:
not_eligiblefor players without hub access,bannedfor suspended accounts,rejectedfor anything else. - Send the
noncefrom the deep link whenever you have it. The call succeeds without it, but the hub page then waits out its own timeout rather than failing immediately.
Need help?
Contact our integration team at [email protected]