The specification, for integration engineers.
This page is written for the engineer who will wire the seat, not for the media plan. Protocol, request structure, transparency fields, deal mechanics, scoping and the integration process, in one place.
Per-seat endpoints · sandbox first
OpenRTB 2.6 over HTTPS.
| Aspect | Specification |
|---|---|
| Protocol version | OpenRTB 2.6, JSON serialization over HTTPS POST |
| Endpoints | Per-seat endpoints issued at provisioning; one sandbox, one production |
| Serialization | JSON; protobuf is supported where agreed during integration |
| Transport | HTTPS with keep-alive; gzip request bodies accepted |
| Timeouts | Bid response deadlines are set per impression type and shared at provisioning, with CTV pod deadlines distinct from mobile |
| Consent signals | TCF v2.2 and GPP strings passed in the request; enforcement applied before the request is sent |
What arrives on every request.
The app object
Declared bundle ID, store URL, app name and category, checked against the store listing before the app is allowed to monetize. Publisher and account identifiers match the seller registry behind our supply.
The content object
Content series, genre and season or episode identifiers where the platform provides them, plus pod position and slot in the pod via the OpenRTB 2.6 imp fields, so bidders price position honestly.
Impression types
Interstitial, rewarded, banner, native, playable and offerwall on mobile; pre-roll, mid-roll, post-roll and pause on CTV. Video protocols VAST, with client-side and server-side variants declared per impression.
Every request carries its provenance.
Open auction
All eligible impressions, cleared on price. Floors and category screens apply before your seat sees the request.
PMP and PG mechanics
PMP impressions carry the deal ID with a deal floor; programmatic guaranteed commitments arrive as pre-committed impressions with pacing owned by the platform. Deal IDs are assigned at setup and trafficked in the console.
What mismatches mean
If the schain does not resolve to an authorized path, the request does not reach you. That filtering is the enforcement of the authorized-sellers-only policy on our supply.
Scoping and the integration process
Scope the seat
Query volume, queries per second (QPS), is managed with filters: geography, platform, format, content category and deal membership. Scope changes are applied at the seat without re-integration.
Sandbox
Sandbox endpoints return synthetic requests covering every impression type, including CTV pod structures, so parsers are built against real shapes.
Test traffic
Live test traffic runs at agreed QPS; response times are measured against the deadline budgets shared at provisioning.
Go live
Production endpoints issue after test acceptance: parsing complete, response times inside budget, deals trafficked. Ramp is scheduled, not flipped.
What you receive back
Win and loss reasons per auction, spend by deal and impression type, and settlement reporting that reconciles to your console. Creative status and review state come from the demand console, including rejection reasons when policy review fails a creative.
Verify us first
Read the seller registry behind every account ID, ours included, then read the schain node on real test traffic before production ramps.
Wire the seat. Verify everything.
Send your OpenRTB capabilities and target QPS. The integration team provisions sandbox access and the scoping call.
OpenRTB 2.6 · JSON · schain · sandbox first