mocop
Browse · Docs · Guide · Analyze

Betacade API

API by Betacade · rest

Playtest hosting for web games: deploy a build (Unity WebGL, Godot web export or plain HTML/JS), share a link that plays it, and see who played, for how long, and what broke. [Docs, for doing it by hand](/docs) · [The agent guide (/llms.txt)](/llms.txt) · [Changelog](/changelog) · [The studio](https://studio.betacade.com) · [betacade.com](https://betacade.com) AI agents: start at the agent guide, /llms.txt. It walks through every step below. Workflows 1. Sign in. An agent or CLI uses [device sign-in](/device): it starts it, its human approves in a browser, and it collects a token. Or make a [personal access token](/api-keys) in the studio. 2. Put a game up. [Create a game, upload a build and finalize it](/hosting). The game's playUrl always plays its latest ready build. ([Getting started](/docs/getting-started), [uploading a build](/docs/uploading-a-build)) 3. Share it. Hand out the play link, or a tracked link that counts the players it…

Endpoint: https://api.betacade.com/

Verification: observed. Source: crawl.

Capabilities (78)

  • Start an agent device sign-in
  • Collect the token for a device sign-in
  • Discord's interactions ("Send to Betacade")
  • Discord sent the browser back
  • Accept the terms or confirm a link and finish a Discord sign-in
  • Start Sign in with Discord
  • Email a player a sign-in code
  • Hand this browser's sign-in to the studio
  • Sign this browser in with a code from the studio
  • Sign a player out of this browser
  • Sign out on every device
  • Sign a player in
  • Whether this player may play a build
  • Ask a player to sign in from a game on another host
  • A sign-in request for the page that approves it
  • Approve or deny a sign-in request (signed in from the play page)
  • How a sign-in request stands (the asking browser only)
  • Who's playing from a game running as a Discord Activity
  • The games in Betacade's Discord app
  • Send the developer feedback
  • An aggregate of a game's custom events that it declared public
  • The jams a game is on (public)
  • A game's top scores (public)
  • A board entry's picture
  • The Supporters wall and credits of a game's studio (public)
About · Contact · Privacy