Developer documentation
Welcome to the AllGame Club developer docs. This is everything you need to build a game that runs on the Club, or to talk to the platform from your own code.
What the platform does for you
- Accounts. Players register, verify their email, upload an avatar and log in. You never handle passwords.
- The daily play pass. Free players get 15 minutes a day across all games. The play shell measures time and shows the Unlimited upsell. Your game only needs to react to
pause/resume. - Save states. Up to 10 JSON save slots per player per game, versioned, synced across devices.
- Scores and leaderboards. Submit scores to named boards, read all-time / monthly / weekly / daily rankings.
- Membership and payments. Subscriptions, invoices, webhooks. Games never see payment data; they only see whether a player is Unlimited.
Two ways to integrate
| When to use | Auth | |
|---|---|---|
Client SDK (/sdk/allgame.js) | Inside your game, running in the portal's play shell | Portal session cookie, automatic |
REST API (/api/v1) | Companion apps, your own game backend, tooling | Player token agp_… or developer key agk_… |
Both talk to the same REST endpoints; the SDK is a thin convenience layer.
Where to go next
- Getting started: a working game in ten minutes.
- Game modules: folder layout and how files are served.
- game.json reference: every manifest field.
- SDK reference and play sessions.
- REST API, also available as OpenAPI 3.0.
Last updated October 11, 2026.