Video.minduration

The shortest ad the slot accepts, in seconds. Recommended, it defaults to 0 since 2.6 and must not appear on the same Video object as Video.rqddurs.

CurrentintegerOptionalSince 2.0

Field facts

Path: imp.video.minduration
Object: Video
Type: integer
Default: 0 recommended
Requirement: Optional
Added: OpenRTB 2.0
Spec section: 3.2.7

How it is used

With Video.maxduration it forms a duration range. A minimum above zero keeps out bumpers and six second spots the publisher does not want. OpenRTB 2.0 through 2.2 required both bounds; from 2.3 they became recommended, and 2.6 made them mutually exclusive with the exact-duration list.

Example

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

{
  "id": "req-1",
  "imp": [
    {
      "video": {
        "minduration": 5
      }
    }
  ]
}

Common mistakes

Sending it together with Video.rqddurs. The spec forbids the combination, and the validator reports openrtb.fields.mutually_exclusive.
Setting it higher than Video.maxduration, which leaves no creative length that fits.
Sending milliseconds, such as 15000, where the field expects seconds.

Version history

Added in OpenRTB 2.0, 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.0	integer, default - secon	Yes	No
2.1 to 2.2	integer	Yes	No
2.3 to 2.4	integer	Recommended	No
2.5	integer	Recommended	No
2.6-202210 to 2.6-202606	integer, default 0 recommended	No	No