OpenRTB Object & Enum Reference
Look up every OpenRTB 2.x enumerated list — each integer code with its meaning — and search across all of them in your browser.
The OpenRTB Object & Enum Reference bundles every enumerated list with the page, so all lookups and searches run in your browser. Any bid request snippet you paste to decode a code stays on your device and is never uploaded to ArrayKit.
Open the OpenRTB Bid Request Validator
About OpenRTB Enum Reference
The OpenRTB Object & Enum Reference is a searchable lookup for the enumerated lists in the IAB Tech Lab OpenRTB 2.x spec. Every list — devicetype, connectiontype, api, protocols, linearity, playbackmethod, plcmt, placement, pos, banner.btype and battr, contentcontext, video.delivery, feed, volume normalization and more — is bundled with its integer code, plain-English meaning, owning object and dotted attribute path. Type a code, a name, or a synonym like CTV or wifi and it matches across every list at once, so you can decode a bid request field without hunting through the PDF. Ad-ops engineers, SSP and DSP developers, and QA teams can map codes to meanings while building, validating, or debugging traffic. Everything runs in your browser, so bid request snippets you paste stay on your device.
Features
- Covers every OpenRTB 2.x enumerated list from at and devicetype to protocols, plcmt and battr
- Each value shows its integer code beside a plain-English meaning and note
- Global search matches by code, name, or synonym (search CTV to find devicetype 3)
- Filter chips jump straight to any list — devicetype, protocols, playbackmethod, contentcontext
- Copy a paste-ready "attr": code snippet for any value to drop into a bid request
- Shows the owning object and dotted attribute path, e.g. device.devicetype
- Includes OpenRTB 2.6 additions (VAST 4.2, 5G, OOH device, plcmt) and flags deprecations
- Runs entirely in your browser — bid request data you paste never leaves your device
How to use the OpenRTB Enum Reference
- Type a code, name, or synonym like CTV or wifi into the search box to match across all lists
- Or pick a list from the filter chips to browse it from top to bottom
- Read each integer code next to its meaning, note, and dotted attribute path
- Copy the "attr": code snippet and paste it straight into your OpenRTB bid request
Example
Input
{ "device": { "devicetype": 3, "connectiontype": 2 } }
Output
devicetype 3 = Connected TV
connectiontype 2 = Wi-Fi
Decode the integer codes in a bid request into their OpenRTB meanings.
Common errors & troubleshooting
- A partner sends devicetype 8 and your pipeline rejects it as invalid. — devicetype 8 is OOH Device, added in OpenRTB 2.6. Update your allowed set to accept the newer codes (5G, VAST 4.2, plcmt) too.
- You set video.placement but the SSP ignores the signal. — placement (Video Placement Types) is deprecated in OpenRTB 2.6. Send plcmt (Plcmt Subtypes — Video) instead: 1 Instream, 2 Accompanying Content, 3 Interstitial, 4 Standalone.
- protocols 13 fails your validator. — protocols 13 is VAST 4.2, an OpenRTB 2.6 addition. Confirm both ends target 2.6, or restrict protocols to the versions your player supports.
- at=3 confuses your bidding logic. — Auction type 3 means the bidfloor is the agreed-upon deal price. Values 1 and 2 are First Price and Second Price Plus; 500 and greater are exchange-specific.
Frequently asked questions
- What is the OpenRTB Object & Enum Reference?
- It is a searchable index of the enumerated lists in the IAB OpenRTB 2.x specification. Each value in each list — such as devicetype, protocols, or plcmt — is shown with its integer code, meaning, owning object, and dotted attribute path so you can decode bid request fields quickly.
- Which OpenRTB version do these enumerated lists cover?
- The tables follow OpenRTB 2.5 and 2.6. Values added in 2.6, like connectiontype 7 (5G), devicetype 8 (OOH Device), protocols 13/14 (VAST 4.2), and the plcmt subtypes, are included and noted, and deprecated entries like the placement list are flagged.
- What is the difference between OpenRTB placement and plcmt?
- placement is the legacy Video Placement Types list (In-Stream, In-Banner, In-Article, In-Feed, Interstitial), deprecated in OpenRTB 2.6. plcmt is the newer Plcmt Subtypes — Video list (Instream, Accompanying Content, Interstitial, Standalone) that replaces it. Both are listed side by side here.
- What does devicetype 3 mean in an OpenRTB bid request?
- devicetype 3 is Connected TV — a big-screen CTV or OTT device. Search CTV or 3 in this reference and it resolves to the Connected TV entry, along with the other device types like Phone (4), Tablet (5), and OOH Device (8).
- How do I search these OpenRTB lists by code or synonym?
- Type into the search box: an integer like 429, a phrase like second price, or a synonym like CTV or wifi. The reference matches across every list at once and groups the results by list, so you do not need to know which object the field belongs to.
- Does this OpenRTB reference send my bid request data anywhere?
- No. The enumerated lists are bundled with the page and every lookup happens in your browser. Any bid request JSON you paste to check a code stays on your device and is never uploaded to ArrayKit.
Related tools
All ArrayKit tools