OpenRTB
OpenRTB is the open IAB protocol that standardizes the structure of bid requests and responses in real-time bidding auctions.

OpenRTB is the open, industry-standard protocol that defines how bid requests and bid responses are structured in programmatic auctions, so that supply-side and demand-side platforms can integrate with each other more easily. The IAB Tech Lab maintains it (see the OpenRTB 2.x specification), and it is the common language of the real-time bidding ecosystem. It does not remove integration work: the specification describes its aim as making integration easier without regulating how each business operates, and it lets exchanges define their own extensions.
How it works#
When an impression is offered for sale, an exchange or other supply source sends a bid request to bidders, normally as JSON over HTTP POST. Depending on what the sender includes, the request carries standardized fields such as the impression details, device and user signals, the site or app, a floor price and a supply chain object. Buyers parse it, decide whether and how much to bid, and reply with an OpenRTB bid response. Because the schema is shared, an Ad Exchange can broadcast one request to many buyers and evaluate their responses under its own auction rules, which OpenRTB leaves to the exchange. The version in use is signalled in a request header (for example 2.6), exchanges can add their own extension fields, and the specification is updated through dated releases (the latest tag checked on 7 October 2026 was 2.6-202606), so two parties still need to agree on what they support.
Why it matters#
OpenRTB aims to reduce the custom integration work between exchanges and bidders in Real-Time Bidding (RTB): its specification describes the goal as a common language between buyers and sellers that makes integration between them easier. Version 2.6 made the SupplyChain Object (schain) a standard part of the bid request. It lists the entities declared as taking part in the direct flow of payment for the inventory, and its complete flag says whether the chain claims to reach back to the owner of the site or app (see the IAB schain specification). It is declared by the parties involved, so it does not prove every technical hop or that each listed seller is legitimate, and buyers can cross-check its nodes against ads.txt and sellers.json files.
For anyone analyzing how an ad reached a page, OpenRTB messages describe what a sender declared in one auction request. They pass between ad-tech systems, so a captured ad does not include them, and they are not a complete record of how an ad reached a page. They underlie Programmatic Advertising, but a researcher outside the transaction typically has to rely on other evidence, such as an ad's redirect trail and published declarations like ads.txt and sellers.json.
Related terms: Real-Time Bidding (RTB), SupplyChain Object (schain), and Programmatic Advertising.




