Docs
OpenRTB examples
Valid, annotated OpenRTB payloads you can copy, adapt, and validate. Every example passes the current spec snapshot clean and opens directly in the tester.
OpenRTB banner bid request example
A minimal, valid display bid request: one banner impression with primary and fallback sizes, a site object with publisher, and an explicit floor.
View the payload →OpenRTB video bid request example
A valid instream video request: mimes, duration bounds, and the modern plcmt declaration.
View the payload →CTV ad pod bid request example
A connected-TV ad pod request using the 2.6 pod bidding fields: pod identity, slot sequencing, and exact-duration requirements.
View the payload →OpenRTB native bid request example
A valid native impression showing the trickiest encoding in OpenRTB: the Native Markup Request as a JSON string encoded exactly once.
View the payload →Bid request example with GDPR and GPP consent
A mobile banner request carrying privacy signals at their OpenRTB 2.6 paths: regs.gdpr, user.consent, and the GPP pair.
View the payload →DOOH bid request example
A digital out-of-home request: the dooh distribution channel added in 2.6-202211, with quantity-based impression counting.
View the payload →OpenRTB 3.0 bid request example
A layered 3.0 request: the openrtb envelope, item in place of imp, and the AdCOM placement under item.spec.
View the payload →OpenRTB video bid response example
A realistic CTV video bid response: VAST markup inline in adm, mtype declared, and win/billing/loss notices carrying macros.
View the payload →Matched bid request and response example
A request/response pair that cross-validates clean: seat allowed, deal echoed, currency permitted, and markup matching the offer.
View the payload →How to use these
Each payload is a starting shape, not a template to ship verbatim: swap the ids, domains, and bundles for yours, then validate the result in the tester or in CI with the CLI. The bid request and bid response references explain every field these examples touch.