Metamarkets · Authentication Profile

Metamarkets Authentication

Authentication

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

CompanyAdvertisingAdTechAnalyticsReal TimeData IngestionProgrammatic AdvertisingOpenRTBBusiness Intelligence
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

basicAuth http
scheme: basic · in: header ()

Source

Authentication Profile

metamarkets-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://docs.metamarkets.com/docs/real-time-data-delivery
note: >-
  The Metamarkets RDI ingestion endpoints are protected by HTTP Basic
  authentication. Each customer receives a username, password, and one or more
  endpoint URLs from their Metamarkets data engineer / account representative;
  credentials are not self-service. HTTPS is required so credentials are sent
  encrypted. Documented via the RDI client library and the real-time delivery
  curl example (`--user <username>:<password>`).
summary:
  types: [http]
  http_schemes: [basic]
  self_service: false
schemes:
  - name: basicAuth
    type: http
    scheme: basic
    in: header
    header: Authorization
    transport: https-required
    credential_source: >-
      username + password issued by a Metamarkets data engineer / account
      representative (per-endpoint)
    sources:
      - https://docs.metamarkets.com/docs/real-time-data-delivery
      - https://docs.metamarkets.com/docs/rdi-client-library