FOR DEMAND PARTNERS

Relevant opportunities. Clearly defined.

A protocol-first partnership, from the first test request to controlled traffic.

Read integration guide
Conceptual traffic routing sculpture

Selected traffic

Country, platform, format and app context inform routing. Independent per-DSP controls define eligible traffic.

Your endpoint, explicit auth

Configure a verified HTTPS endpoint with no authentication, Bearer or a custom header. SSP credentials are never forwarded.

A bounded bidding window

Requests carry the remaining time budget. Parallel demand calls stay inside the overall auction deadline.

Transparent bid requirements

Return USD CPM, matching request and impression IDs, inline creative markup and the metadata needed for screening.

A practical path to integration.

Agree the contract. Verify the request. Start with controlled traffic.

  1. Review supported fields and constraints
  2. Agree endpoint, authentication and formats
  3. Verify examples, errors and timeout behavior
  4. Complete partner testing before increasing traffic
View the full checklist

Search documentation

Search fields, guides and examples.