Skip to main content

Base URL

api.susaplay.com serves these route prefixes: /catalog, /publicCatalog, /save, /engagement, /analytics, /webhooks, /ai, /partners, /widgets, and the SDK’s /economy routes. Other routes are served at https://europe-west1-susaplay-2e8e3.cloudfunctions.net/{function}.

Authentication

Player and developer calls send a bearer token: a Firebase ID token, or the SusaPlay game-session token the SDK uses.
When App Check is enforced, player routes also need an X-Firebase-AppCheck header; the SusaPlay page supplies it. Developer endpoints — reading games, versions, Addressables and analytics, build uploads, preview links, Addressables upload, publish and rollback, and adding store items and achievements — also accept a developer API key, for pipelines and AI tools:
A key holds some of six permissions: games:read, analytics:read, builds:write, addressables:write, addressables:publish and game-config:write. See API Keys. Partner endpoints use a partner key:

Response format

Success

Error

Timestamps are ISO 8601 strings, except expiresAt fields, which are Unix seconds.

Error codes

CORS

Allowed origins are configured per deployment. Custom origins, including partner integrations, must be approved by SusaPlay before they can call the API.