TheMonetizr · Authentication Profile

Themonetizr Authentication

Authentication

TheMonetizr secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyAdvertisingGamingIn-Game AdvertisingMonetizationMobileRewardsAd TechProgrammaticUnity
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

themonetizr-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: derived
source: The-Monetizr-Campaigns-Unity-SDK (Assets/MonetizrCampaigns/Scripts/Networking/NetworkingUtils.cs, MonetizrHttpClient.cs)
summary:
  types: [http]
  http_schemes: [bearer]
  api_key_in: []
  oauth2_flows: []
schemes:
  - name: bearerAuth
    type: http
    scheme: bearer
    description: >-
      The Monetizr Campaigns API authenticates with a per-game API key sent as an
      HTTP Bearer token (Authorization: Bearer <apiKey>). The key is provisioned
      per game/application in the Monetizr console and configured in the SDK
      MonetizrSettings.
    sources:
      - The-Monetizr-Campaigns-Unity-SDK/NetworkingUtils.cs
context_headers:
  - name: player-id
    description: Device/player identifier used for campaign targeting and reward attribution.
  - name: ad-id
    description: Platform advertising identifier (IDFA/GAID).
  - name: sdk-version
    description: Monetizr SDK version string.
  - name: os-group
    description: Coarse OS group of the requesting device.
  - name: device-group
    description: Coarse device-size/class group.
notes:
  - No OAuth2 or OpenID Connect surface is present; auth is a static per-game Bearer API key.
  - The provider publishes no OpenAPI/security scheme document; this profile is derived from the first-party Unity SDK source.