Video.rqddurs

The exact creative durations the slot accepts, in seconds, for cases such as live TV where an ad that runs short or long leaves dead air. Mutually exclusive with Video.minduration and Video.maxduration. Added in 2.6.

Currentinteger arrayOptionalSince 2.6-202204

Field facts

Path: imp.video.rqddurs
Object: Video
Type: integer array
Requirement: Optional
Added: OpenRTB 2.6-202204
Spec section: 3.2.7

How it is used

Send [15, 30] when a slot takes a 15 or a 30 second spot and nothing in between; a buyer holding only a 20 second cut passes. When the player can absorb any length inside a range, send Video.minduration and Video.maxduration instead. Bidders state each creative's length in Bid.dur.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "imp": [
    {
      "video": {
        "rqddurs": [
          15,
          30
        ]
      }
    }
  ]
}

Common mistakes

Sending it together with Video.minduration or Video.maxduration. The spec forbids it, and the validator reports openrtb.fields.mutually_exclusive.
Sending an empty array, which permits no duration. The validator warns with openrtb.video.pod.rqddurs_empty.
Using it for the length of the whole break, which is Video.poddur.

Version history

Added in OpenRTB 2.6-202204, and present in the latest snapshot. The table shows how each version's spec text types the field.

Versions	Type in the spec	Required	Deprecated
2.6-202204	Added in the first 2.6 release, published without a structured text archive; the 2.6-202210 republication is the first tagged text.
2.6-202210 to 2.6-202606	integer array	No	No

Versioned rules that name this field

openrtb.2.6.imp.video_audio.rqddurs OpenRTB 2.6 added exact-duration requirements for video and audio creatives.