Beamable · Authentication Profile

Beamable Authentication

Authentication

Beamable secures its APIs with apiKey and http across 4 declared security schemes, as derived from its OpenAPI definitions.

Game BackendLiveOpsPlayer AccountsVirtual CurrencyInventoryLeaderboardsMatchmakingMicroservicesUnityUnrealGame EconomyAnalytics
Methods: apiKey, http Schemes: 4 OAuth flows: API key in: header

Security Schemes

server apiKey
· in: header (X-DE-SIGNATURE)
user http
scheme: bearer
userRequired apiKey
· in: header (X-DE-GAMERTAG)
scope apiKey
· in: header (X-DE-SCOPE)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/beamable-leaderboards-openapi.yml, openapi/beamable-live-events-openapi.yml,
  openapi/beamable-microservices-openapi.yml, openapi/beamable-player-accounts-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: server
  type: apiKey
  in: header
  parameter: X-DE-SIGNATURE
  description: Signed Request authentication using project secret key.
  sources:
  - openapi/beamable-leaderboards-openapi.yml
  - openapi/beamable-live-events-openapi.yml
  - openapi/beamable-microservices-openapi.yml
  - openapi/beamable-player-accounts-openapi.yml
- name: user
  type: http
  scheme: bearer
  bearerFormat: Bearer <Access Token>
  description: Bearer authentication with a player access token in the Authorization header.
  sources:
  - openapi/beamable-leaderboards-openapi.yml
  - openapi/beamable-live-events-openapi.yml
  - openapi/beamable-microservices-openapi.yml
  - openapi/beamable-player-accounts-openapi.yml
- name: userRequired
  type: apiKey
  in: header
  parameter: X-DE-GAMERTAG
  description: Gamer Tag of the player.
  sources:
  - openapi/beamable-live-events-openapi.yml
- name: scope
  type: apiKey
  in: header
  parameter: X-DE-SCOPE
  description: Customer and project scope. This should contain the '<customer-id>.<project-id>'.
  sources:
  - openapi/beamable-live-events-openapi.yml