specter

Specter — Game Backend as a Service

Specter is a backend platform for games. Instead of building your own backend, your game calls Specter's REST APIs (and WebSocket server for multiplayer) for accounts, virtual economy, missions/achievements, leaderboards, tournaments and matchmaking. Game content (currencies, items, tasks, leaderboards…) is configured in the Specter dashboard at https://console.specterapp.xyz; your game then reads and acts on that content via the client API.

Base URLs

Environment	Client REST API	Multiplayer (Socket.io)
Production	https://api.specterapp.xyz/v2/client	https://multiplayer.specterapp.xyz
Staging	https://client.staging.specterapp.xyz/v2/client	https://staging.multiplayer.specterapp.xyz

Quick connectivity check: POST {base}/app/welcome. Always use the v2 client API. v1 exists but is legacy — do not build new integrations on it.

The two credentials (read this first)

1. api-key header — required on every request. Issued per project + environment in the dashboard (dev / qa / production keys are different). Identifies which game/project the call is for.
2. Authorization: Bearer <accessToken> header — required for player-scoped endpoints (anything player/me/*, purchases, inventory changes, score posts…). Obtained from any auth/login-* or auth/signup-* endpoint. The JWT embeds userId + projectId and expires in ~1 hour — refresh with auth/refresh-token.

Endpoints listed as "API Key" auth in the references work without a user token (app-level catalog reads, plus server-to-server lookups of other players' data).

All client endpoints use POST with a JSON body — even reads. Filters, pagination (offset/limit) and the attributes array (opt-in response fields) go in the body.

Response envelope

Every endpoint returns the same shape — branch on status/code, read payload from data:

{
  "status": "success",
  "code": 200,
  "message": "Items list",
  "data": { ... },
  "errors": []
}