An overview of what the Mokito REST API offers and how it is structured.
The Mokito REST API is available exclusively to servers with an active Mokito Premium subscription. Every request is authenticated with a per-guild API token and rate-limited to ensure fair usage.
The API is stateless — no sessions, no cookies. Every request carries its own Bearer token in the Authorization header. Responses are always JSON; the API never returns HTML.
The API exposes read-only endpoints organized by resource. Each resource lives under its own subcategory in this documentation — see the left sidebar for the full list. The first available resource is Steam Links, which lets you query Steam-linked player data for your Discord server.
All endpoints are scoped to the guild your API token belongs to. The API never returns data about members of other servers, even if you know their IDs.
https://mokito.bippymiester.dev/api/v1All API routes live under /api/v1/.... Each resource adds its own prefix — for example, the Steam Link routes live under /api/v1/steam-link/.... The full URL for a Steam Link endpoint, for example, is https://mokito.bippymiester.dev/api/v1/steam-link/player-profile.
The API uses URL versioning. The current version is v1. When a breaking change is introduced, a new version (/api/v2/) will be published alongside the old one, and the deprecated version will respond with Deprecation and Sunset headers before being removed.
Non-breaking changes — adding a new optional query parameter, adding a new field to a response object, adding a new endpoint — are shipped under the current version without bumping it. Always parse JSON responses defensively (ignore unknown fields) so additive changes do not break your integration.