Game Player Accounts API
Give players an identity in minutes: anonymous device login now, an upgrade to a real username/password account later. A player token proves who they are, so their saves and scores are theirs alone — from any engine, or an AI agent.
Anonymous, then upgraded
Start with zero-friction device login; let the player attach a username + password later without losing progress.
A token that proves identity
Auth returns a player token; pass it and a client can only touch its own saves, scores and inventory — no spoofing.
No SDK, any engine
Plain HTTP from Unity, Godot, Unreal, web or a server.
Free to start
Unlimited accounts. You pay only for monthly active players.
Player identity without a login server
Most games need a player to be the same player across sessions and devices, and to keep their own progress private. Backline player accounts is one endpoint: POST a device id for instant anonymous login, or a username and password for a real account, and get back a player token. Pass that token on saves and score submits and a client can only act as itself. Link a device player to a username later and the anonymous progress carries over. It works from Unity C#, Godot GDScript, a web build, or an AI agent.
Frequently asked questions
How do I add player login to my Unity or Godot game?
POST a device id to /api/backline/v1/players/auth for instant anonymous login, or a username and password, and store the returned playerToken. Pass playerToken on saves and score submits so the player can only touch their own data. Plain HTTP from any engine or an AI agent.
Is player auth free?
Yes. Accounts and auth are unlimited and free — you pay only for monthly active players (10,000 free, then $0.01 each).
Can a player start anonymous and make an account later?
Yes. Device login creates an anonymous player instantly; POST /players/link with the player token plus a username and password to upgrade — their existing saves, scores and inventory carry over.
How does the token stop spoofing?
Auth returns a player token tied to that player. Self-scoped calls (saving, submitting a score) accept the token and resolve identity from it, so a client can't claim to be another player. Server-authoritative flows can still pass a trusted player id directly.
Can an AI agent wire this up?
Yes — device auth, register, login and link are all documented REST calls an AI coding agent can drive end-to-end.