BidMachine · Authentication Profile

Bidmachine Io Authentication

Authentication

BidMachine's REST APIs use HTTP authentication only — no API keys, no OAuth 2.0, no OIDC. The credentials are the publisher's dashboard login and password. The Reporting API takes them as HTTP Basic on every request (a 401 answers WWW-Authenticate: Basic realm="Reporting API"). The Placement Management API exchanges the same Basic credentials at POST /auth for a short-lived bearer token ({token, expires}) and requires Authorization: Bearer on every placement call; when a call returns 401 the token has expired and the client re-authenticates. All placement operations are scoped to sources the authenticated publisher owns (403 otherwise). No token revocation endpoint, no scopes and no service accounts are documented. The OpenRTB auction surface authenticates by source id in the endpoint path (https://api-eu.bidmachine.io/auction/prebid/${source_id}) issued per partner, not by a header.

BidMachine secures its APIs with http across 2 declared security schemes, as derived from its OpenAPI definitions.

AdvertisingAdTechMobile AdvertisingAd ExchangeAd MediationIn-App BiddingOpenRTBApp MonetizationProgrammatic AdvertisingMobile SDKReportingCompany
Methods: http Schemes: 2 OAuth flows: API key in:

Security Schemes

basicAuth http
scheme: basic
bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑
generated: '2026-09-19'
method: searched
source: openapi/bidmachine-io-placement-management-openapi.yml, openapi/bidmachine-io-reporting-openapi.yml
docs: https://developers.bidmachine.io/api/get-access-token
description: >-
  BidMachine's REST APIs use HTTP authentication only — no API keys, no OAuth 2.0, no OIDC. The
  credentials are the publisher's dashboard login and password. The Reporting API takes them as HTTP
  Basic on every request (a 401 answers WWW-Authenticate: Basic realm="Reporting API"). The Placement
  Management API exchanges the same Basic credentials at POST /auth for a short-lived bearer token
  ({token, expires}) and requires Authorization: Bearer <token> on every placement call; when a call
  returns 401 the token has expired and the client re-authenticates. All placement operations are
  scoped to sources the authenticated publisher owns (403 otherwise). No token revocation endpoint,
  no scopes and no service accounts are documented. The OpenRTB auction surface authenticates by
  source id in the endpoint path (https://api-eu.bidmachine.io/auction/prebid/${source_id}) issued
  per partner, not by a header.
summary:
  types:
    - http
  http_schemes:
    - basic
    - bearer
  api_key_in: []
  oauth2_flows: []
  credential: dashboard login and password (https://dashboard.bidmachine.io/sign-in)
  token_lifetime: short-lived; `expires` (date-time) is returned with the token, the exact TTL is not published
  observed:
    - {url: 'https://api-eu.bidmachine.io/api/v1/report/ssp?start=2026-09-01&end=2026-09-02', status: 401, www_authenticate: 'Basic realm="Reporting API"'}
    - {url: 'https://api-eu.bidmachine.io/api/v1/publisher/sources/1/placements', status: 401, body: 'HTML "Authentication required"'}
schemes:
  - name: basicAuth
    type: http
    scheme: basic
    docs: https://developers.bidmachine.io/api/bidmachine-reporting-api
    used_by:
      - openapi/bidmachine-io-placement-management-openapi.yml#getAccessToken
      - openapi/bidmachine-io-reporting-openapi.yml#retrieveSspReportData
      - openapi/bidmachine-io-reporting-openapi.yml#retrieveBidderReportData
      - openapi/bidmachine-io-reporting-openapi.yml#retrieveP2pRevenueReportData
    sources:
      - openapi/bidmachine-io-placement-management-openapi.yml
      - openapi/bidmachine-io-reporting-openapi.yml
  - name: bearerAuth
    type: http
    scheme: bearer
    docs: https://developers.bidmachine.io/api/get-access-token
    token_endpoint: POST https://api-eu.bidmachine.io/api/v1/auth (Basic credentials in; {token, expires} out)
    used_by:
      - openapi/bidmachine-io-placement-management-openapi.yml#listPlacements
      - openapi/bidmachine-io-placement-management-openapi.yml#createPlacement
      - openapi/bidmachine-io-placement-management-openapi.yml#updatePlacement
      - openapi/bidmachine-io-placement-management-openapi.yml#deletePlacement
    sources:
      - openapi/bidmachine-io-placement-management-openapi.yml
related:
  conventions: conventions/bidmachine-io-conventions.yml
  errors: errors/bidmachine-io-problem-types.yml

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/bidmachine-io-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.