What is OpenRTB?
OpenRTB is the open standard ad exchanges and bidders use to buy and sell ad impressions in real time. IAB Tech Lab maintains it. It defines the JSON an exchange sends to offer an impression (the bid request), the JSON a bidder sends back to buy it (the bid response), and the notices that close the loop. Nearly every programmatic connection between a supply-side platform and a demand-side platform speaks it, most of them OpenRTB 2.5 or 2.6.
What OpenRTB standardizes
Before OpenRTB, every exchange had its own bidding API and every buyer wrote a separate integration for each one. OpenRTB 2.0, published in January 2012, replaced that with one object model. Today it standardizes four things:
- The bid request. One JSON object per auction, sent by HTTP POST, that describes the impressions for sale and their context.
- The bid response. The bidder's answer: bids grouped by seat, each with a price and the ad markup or a way to fetch it, or a decline.
- Auction rules the request declares. First or second price in
BidRequest.at, the deadline inBidRequest.tmax, currencies, floors, and deal terms. - Notices and macros. Win, billing, and loss notice URLs the exchange calls after the auction, with substitution macros such as
${AUCTION_PRICE}filled in.
It does not define how ads are served or measured, the creative formats themselves (VAST for video, MRAID for rich media, and the Native Ads spec cover those), how a bidder decides what to pay, or how a header bidding wrapper such as Prebid.js runs in the page.
Who maintains OpenRTB
IAB Tech Lab owns the specification and develops it in its Programmatic Supply Chain Working Group, with exchanges, DSPs, and publishers contributing. Versions 2.0 through 2.5 were published as PDFs. Since OpenRTB 2.6 in April 2022 the spec lives in the public openrtb2.x repository, revised through dated snapshots such as 2.6-202303 and 2.6-202606. The specification versions page links every version to its official text.
How one auction works
tmax, usually a few hundred milliseconds.- A user opens a page, an app screen, or a stream with an ad break. The publisher's ad code or SDK asks its exchange to sell the slot.
- The exchange builds a bid request and sends it to many bidders at once, each over its own HTTP connection.
- Each bidder parses the request, decides whether and how much to bid, and replies before
BidRequest.tmaxruns out. A bidder that does not want the impression returns HTTP 204 or a response with a no-bid reason. - The exchange discards late and invalid bids, applies floors, and picks the winner by the auction type in
BidRequest.at. It calls the winner's win notice and, when the ad is actually billable, its billing notice. Losers can receive a loss notice with a reason code. - The winning markup renders on the device.
The auction lifecycle walkthrough follows one impression through these steps with timings.
The bid request
A bid request is one JSON object. Only two fields are required: BidRequest.id, the exchange's ID for the auction, and BidRequest.imp, an array with at least one impression. In practice buyers expect much more, because they cannot price what they cannot see.
{
"id": "4f2a9c1e-77b0-4c1f-9d2e-1b8f0c6d5a31",
"imp": [
{
"id": "1",
"banner": { "format": [{ "w": 300, "h": 250 }, { "w": 320, "h": 50 }] },
"bidfloor": 0.75,
"bidfloorcur": "USD",
"secure": 1
}
],
"site": {
"domain": "news.example",
"page": "https://news.example/sports/match-report",
"publisher": { "id": "pub-8841" }
},
"device": { "ua": "Mozilla/5.0 ...", "ip": "203.0.113.0", "devicetype": 2, "language": "en" },
"user": { "id": "u-51e2" },
"regs": { "gdpr": 1 },
"at": 1,
"tmax": 300,
"cur": ["USD"]
}| Object | What it describes |
|---|---|
BidRequest.imp | Each slot for sale, with its format (Imp.banner, Imp.video, Imp.audio, or Imp.native), floor, and deals. |
BidRequest.site, BidRequest.app, BidRequest.dooh | Where the ad appears: a website, a mobile or CTV app, or a digital out-of-home screen. Send exactly one. |
BidRequest.device | The device: user agent, IP, type, operating system, advertising ID, location. |
BidRequest.user | The person, as far as consent allows: IDs, consent string, extended IDs. |
BidRequest.regs | Regulatory signals: GDPR, GPP, US privacy, COPPA. |
BidRequest.source | Who is selling, including the supply chain of every reseller in Source.schain. |
The bid request reference covers every object, and the field reference has a page per field with its type, default, and version history.
The bid response
The bidder echoes the request BidResponse.id and groups bids by buyer seat in BidResponse.seatbid. Each bid names the impression it targets in Bid.impid, the price in CPM, and the ad in Bid.adm or behind the win notice.
{
"id": "4f2a9c1e-77b0-4c1f-9d2e-1b8f0c6d5a31",
"cur": "USD",
"seatbid": [
{
"seat": "buyer-42",
"bid": [
{
"id": "b-1",
"impid": "1",
"price": 1.32,
"adm": "<div>...creative markup...</div>",
"adomain": ["brand.example"],
"crid": "cr-7781",
"w": 300,
"h": 250,
"mtype": 1,
"nurl": "https://dsp.example/win?p=${AUCTION_PRICE}"
}
]
}
]
}Versions in use
- OpenRTB 2.5 (December 2016) added header bidding support, metrics, and the loss and billing notices. Many SDKs and older contracts still run it.
- OpenRTB 2.6 (April 2022) added CTV ad pods, structured user agents, and first-class GDPR and supply chain fields. Its dated snapshots, up to 2.6-202606, are the current standard.
- OpenRTB 3.0 is a layered redesign built on AdCOM. It is not backward compatible and has little production adoption.
The 2.5 versus 2.6 guide lists what changed and how to migrate.
Standards that travel with OpenRTB
- AdCOM holds the enumerated lists 2.6 points to, such as device types and video placement.
- The Native Ads spec defines the JSON inside
Native.request. - VAST is the markup a video bid returns.
- GPP, TCF, and US Privacy strings carry consent.
- ads.txt, sellers.json, and schain let buyers verify who is selling.
- Prebid runs header bidding and speaks OpenRTB to its demand partners.
Questions people ask
What is OpenRTB?
OpenRTB is the IAB Tech Lab standard that defines how an ad exchange offers an impression to bidders and how they answer, in real time. The exchange sends a JSON bid request over HTTP POST describing the impression, the site or app, the device, the user, and privacy signals; each bidder answers within the tmax deadline with a bid response carrying a price and the ad, or declines.
Who maintains OpenRTB?
IAB Tech Lab maintains OpenRTB through its Programmatic Supply Chain Working Group. Versions 2.0 to 2.5 were published as PDFs; the current 2.6 line is published in the openrtb2.x GitHub repository as dated snapshots, and OpenRTB 3.0 lives in the openrtb repository.
Which OpenRTB version is current?
OpenRTB 2.6 is the current version, revised through dated snapshots; the latest is 2.6-202606. OpenRTB 2.5 from 2016 is still common in older integrations. OpenRTB 3.0 is a separate, non-backward-compatible design with little adoption.
Check a payload
Paste a bid request or response into the tester to see which fields break the spec for the version you target. The OpenRTB FAQ answers the common questions in one place.