Sentinel Network uses API keys for authentication. Every request must include your API key as a Bearer token. The gateway validates the key, resolves your publisher identity and permissions, and routes the request to the API.

​
Getting Your API Key

  1. Sign up or log in at the Sentinel Dashboard
  2. Create or select a publisher
  3. Navigate to API Keys and generate a new key
  4. The key is shown once — store it securely
API keys use the prefix sni_ (e.g., sni_live_abc123...). Include the full key in the Authorization header as a Bearer token.

​
Request Headers

Every request requires an Authorization header with your API key, and game-scoped operations require X-Game-Id:

​
Example Request

​
Scopes

Scopes control which API operations an API key can perform. Scopes are configured when creating or editing a key in the Dashboard.
The bans:global scope is an additional permission required on top of bans:write to create bans with "scope": "global". This prevents accidental network-wide bans.

​
Environments

Sandbox and production use separate API keys. Generate sandbox keys from the Dashboard by switching to sandbox mode.

​
Dashboard Authentication

The Sentinel Dashboard uses OAuth 2.0 (Google and GitHub) for authentication. See the Dashboard section for details on signing in and managing your account.