Bid requests in, revenue data out.
The platform speaks the standards your stack already speaks: OpenRTB 2.6 for auctions, VAST for players, a REST reporting API for everything the console shows. Documented end to end, sandbox included.
Five doors, one building.
| METHOD | PATH | PURPOSE |
|---|---|---|
| POST | /rtb/v2/bid | OpenRTB 2.6 auction requests, JSON over HTTPS |
| GET | /vast/v4/tag | VAST 4.x XML endpoints for video players |
| GET | /vast/v2/tag | VAST 2.6 / 3.0 for legacy players and SDKs |
| POST | /report/v1/query | Analytics queries, ten-minute grain |
| GET | /report/v1/dimensions | Available dimensions and metrics |
Copy, paste, adapt.
POST /rtb/v2/bid
{
"id": "req-8f31c2",
"imp": [{
"id": "1",
"banner": { "w": 970, "h": 250 },
"bidfloor": 1.20,
"secure": 1
}],
"tmax": 140
} GET /vast/v4/tag
?placement=om-77412
&dur=15
&pod=3
&ssai=1
# returns a VAST 4.2 XML document,
# stitched server side when ssai=1 GET /report/v1/query
?dim=placement,country
&metrics=revenue,cpm,fill
&grain=10m
&window=7d
# JSON rows, same numbers as the
# console, ten minutes delayed Sample top CPMs by market.
SAMPLE FIGURES FOR ILLUSTRATION. FULL COVERAGE ACROSS NA, SA, EMEA AND APAC.
API FAQ.
No. Campaigns run through your DSP seat, a direct line or the managed stack. The API exists for teams that want reporting and controls in their own tooling.
Yes. A sandbox feed with synthetic OpenRTB requests runs continuously, so integration and load testing never touch real supply. Most partners move from sandbox to live traffic inside a week.
Everything the console shows: revenue, CPM, fill, requests, pageviews, video detail, countries and devices, at ten-minute grain across a ninety-day window.
Build on supply worth building on.
Ask for a key and a sandbox feed. The docs travel with them.