Video.maxduration

The longest ad the slot accepts, in seconds. Recommended, and since 2.6 mutually exclusive with Video.rqddurs, so a request carries either a duration range or an exact list.

CurrentintegerRecommendedSince 2.0

Field facts

Path: imp.video.maxduration
Object: Video
Type: integer
Requirement: Recommended
Added: OpenRTB 2.0
Spec section: 3.2.7

How it is used

Bidders drop creatives longer than this before pricing. In a structured pod it limits each slot, while Video.poddur limits the whole break. Video.maxextended can allow play beyond this value for ads that extend. Required in OpenRTB 2.0 through 2.2 and recommended since 2.3.

Example

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

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

Common mistakes

Leaving it out on CTV. Bidders then guess, and a 60 second creative sent into a 30 second slot can fail after the auction is already won.
Sending it together with Video.rqddurs, reported as openrtb.fields.mutually_exclusive.
Sending milliseconds instead of 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 to 2.6-202606	integer	Recommended	No