DurFloors.mindur

Low end of the duration range, in seconds as in the spec's own example. If absent, the range has no lower bound. Each entry needs at least one of DurFloors.mindur and DurFloors.maxdur.

CurrentintegerOptionalSince 2.6-202309

Field facts

Path: imp.audio.durfloors.mindur, imp.video.durfloors.mindur, imp.pmp.deals.durfloors.mindur
Object: DurFloors
Type: integer
Requirement: Optional
Added: OpenRTB 2.6-202309
Spec section: 3.2.35

How it is used

The spec's wording can be read as allowing only one bound per entry, but its own example of a 16 to 30 second range needs both, so closed ranges are normal. That example also uses whole-second ranges that meet without overlapping, such as 1 to 15 and 16 to 30.

Example

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

{
  "id": "req-1",
  "imp": [
    {
      "audio": {
        "durfloors": [
          {
            "mindur": 16
          }
        ]
      }
    }
  ]
}

Common mistakes

Omitting both bounds, which leaves an entry that matches every duration.
Writing ranges that share an endpoint, such as 1 to 15 and 15 to 30. The spec does not say whether bounds are inclusive, so a 15 second creative may match both floors.

Version history

Added in OpenRTB 2.6-202309, 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-202309 to 2.6-202606	integer	No	No

Related fields

Other DurFloors fields

For a walkthrough of the whole object, read Bid floors.