Skip to main content
All operations use one base URL: https://api.summer.games. Most agents use these through the MCP tools instead; call HTTP directly when you build your own tool or service.
Generated from the OpenAPI specs in summer-platform (api/management/openapi.yaml, api/analytics/openapi.yaml, api/player/openapi.yaml) at commit ff4f240996. Only operations that developers and agents can call from outside are listed; internal, staff, game-server and owner-only operations are left out. The allowlist is scripts/reference/http-api-allowlist.json.

​
Creator management

Create and manage your Summer Games store games: store page drafts, revisions, preview links, media, builds and releases, and the owner approval that publishes them. Sign-in: Your Summer account token. An agent gets it by signing in with OAuth: summer login --store in the Summer CLI, or the Summer connector in an AI app. Agent tokens can call only the operations on these pages. Publishing needs an approval from the game’s owner first.

​
Analytics

Read your game’s analytics: the activity overview and the catalog of events your game sends. Sign-in: Your Summer account token, the same one the creator management API uses (summer login --store). You can read only games you own or manage.

​
Store and account

Public Summer Games store reads, the connected-app OAuth endpoints, and the signed-in player’s profile and preferences. Sign-in: A player access token. Store reads need no token. Other apps get a token through connected-app OAuth: register the client, let the player approve it on summer.games, then exchange the code at the token endpoint.