Loot Rush Games · Authentication Profile

Loot Rush Games Authentication

Authentication

Loot Rush Games secures its APIs with apiKey and http across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyCryptocurrencyBlockchainGamingFintechWalletsCardsPaymentsWithdrawalsMCPAgent-Ready
Methods: apiKey, http Schemes: 2 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer
apiKeyAuth apiKey
· in: header (x-api-key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: openapi/loot-rush-games-partner-openapi.json
docs: https://docs.lootrush.com/
notes: >-
  Withdraw, History and MCP surfaces use Bearer token auth (account API key from
  Settings -> API Key). Connect uses the x-api-key integration key issued during
  Connect registration. The MCP surface additionally enforces key scopes (`mcp`,
  `mcp_card_reveal`). No OAuth2 scheme is declared.
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: 'API token issued by your LootRush account manager. Sent as `Authorization: Bearer
    <token>`.'
  sources:
  - openapi/loot-rush-games-partner-openapi.json
- name: apiKeyAuth
  type: apiKey
  in: header
  parameter: x-api-key
  description: Integration API key provided by LootRush during Connect registration.
  sources:
  - openapi/loot-rush-games-partner-openapi.json