Website
Profiles, capes, leaderboards, community, support and account surfaces.
PLATFORM API V1
One data layer.
Every Leviathan screen.
The versioned Platform API lets Web, Launcher, Client, Mobile and TV use the same public cape, profile and leaderboard data while each surface keeps the navigation and interaction patterns that fit its device.
Shared Surface Manifest
Website first. Native where it helps.
Consistent content without embedding webpages as the product UI.
BOOTSTRAP/api/v1/bootstrap
web · launcher · client · mobile · tv
CAPESShared
LEADERBOARDSShared
THEMESynced
SURFACES
Same language, device-specific navigation.
Each client requests a surface manifest. Labels, states, design tokens and content endpoints stay consistent, while mobile and TV can use native bottom navigation, focus navigation and Cast controls instead of desktop layouts.
Launcher
Play, instances, servers, Discover, Capes, Leaderboards, Store, Downloads and Settings.
Client
Modules, cosmetics, capes, leaderboards, social, servers and settings.
Mobile
Social, Wardrobe, Capes, Leaderboards, Servers, Downloads, Devices & Cast, Wallet, Notifications, Support, Security and Settings.
TV
Remote-friendly Home, Cast, Wardrobe, Capes, Discover, Leaderboards, Servers and Settings.
PUBLIC READ API
Small, versioned endpoints.
Public endpoints support CORS and can be cached by native clients. Observation data is labelled as observation data rather than authoritative ownership.
Bootstrap
GET /api/v1/bootstrap?surface=mobile
Navigation, capabilities, design tokens, endpoint discovery and offline behavior.
Capes
GET /api/v1/capes
Paginated observed cape textures, catalog names, wearer counts and texture URLs.
Cape detail
GET /api/v1/capes/{hash}
One cape plus recent observed wearers and acquisition-safe observation wording.
Leaderboards
GET /api/v1/leaderboards/capes
Capes, skins, names, profile views and public Leviathan accounts.
Profiles
GET /api/v1/profiles/{uuid}
Public profile summary, current textures and observed counters.
Health
GET /api/v1/health
Simple API-version and service availability check for clients.
SECURITY BOUNDARY
Public content and account authority stay separate.
The v1 API is deliberately read-only. Native Launcher, Client, Mobile and TV apps must not copy browser session cookies or store Microsoft/Xbox/Minecraft service tokens. Account writes will use a separate device-bound bearer-token flow.
✓Public readsCapes, profiles, leaderboards, navigation and texture discovery can be cached safely.
✓Versioned schemasClients can pin API/schema versions and fail gracefully when features are unavailable.
✓Offline awareLauncher, mobile and TV can keep the last known bootstrap and public catalog for degraded/offline states.
!Private actionsPurchases, account changes, support replies and ownership-changing actions require authenticated APIs, not public CORS endpoints.
Example bootstrap requestPublic
GET
/api/v1/bootstrap?surface=tv
200UI
Navigation manifestRemote-friendly TV routes
SharedAPI
Content endpointsCapes · leaderboards · profiles
V1OFF
Cached bootstrapLast-known public configuration
SafeBuild once. Present it correctly everywhere.
The API supplies shared truth. Launcher, Client, Mobile and TV still render native Leviathan interfaces rather than loading the website inside a browser shell.