Completes a remote-login lease with the signed-in publisher session: it exchanges the publisher session for a game session of the game the lease belongs to, and authorizes the lease, so the consumer that created the lease receives the session by polling it. The game is the one the lease was created for, resolved server-side from the game key that created it; it is never named in the body. The token field is the publisher session token, sent the way every other publisher-account endpoint sends it. The game session token is not returned: the consumer polls the lease for it, and a token in a page body is the leak this flow exists to avoid. Only a lease created for signing in, whose code no other client claimed and which carries no player yet, is completed: a lease minted for linking, one already bound to a player by another flow, or one whose code was claimed is refused with 409 rather than authorized over the player it already has.The lease names the login the player is meant to use, and this endpoint completes it only through that login: a lease minted for the publisher login needs a publisher-tier session, and a lease minted for a franchise login needs a session of that same franchise. A session of the other tier, or of another franchise, is refused with 403 and a sentence telling the player to sign in to the login the game sent them to. A lease that names no login, which is every lease created before a login could be named, is completed from either tier.
Request
Body Params application/jsonRequired
Examples
Responses
🟢200Authorized
application/json
The lease is authorized. The browser is signed in to game_id, and the consumer that created the lease receives the game session by polling it. Completing a lease this session already completed answers the same, with is_new false.