LoopMe · Authentication Profile

Loopme Authentication

Authentication

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

CompanyAdvertisingAdTechMobile AdvertisingCTVReportingProgrammaticAi Enterprise SoftwareSDK
Methods: apiKey Schemes: 1 OAuth flows: API key in: query

Security Schemes

api_auth_token apiKey
· in: query (api_auth_token)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: openapi/loopme-reporting-openapi.yml
docs: https://wiki.loopme.cool/publishers/reporting-api
summary:
  types:
  - apiKey
  api_key_in:
  - query
  notes: >-
    The Reporting API authenticates with a 16-character api_auth_token passed as
    a query parameter, enabled per-account in the LoopMe dashboard
    Account/Settings. The S2S ad request API is not token-authenticated; requests
    are identified by the appId LoopMe provisions to the publisher. Mobile
    integrations use the United SDK with an app key.
schemes:
- name: api_auth_token
  type: apiKey
  in: query
  parameter: api_auth_token
  description: 16-character API authentication token generated by LoopMe. Enable Reporting API
    access in the dashboard Account/Settings to obtain it.
  sources:
  - openapi/loopme-reporting-openapi.yml