anchor.diff:  the `Content-Type` header. The value of this header must map to one of
   the supported formats that the API supports. Most APIs support JSON,
   YAML, CBOR, and SMILE. The bulk and multi-search APIs support NDJSON,
  -JSON and SMILE; other types will result in an error response.
  -
  -Additionally, when using the `source` query string parameter the
  +JSON, and SMILE; other types will result in an error response.
  +
  +Additionally, when using the `source` query string parameter, the
   content type must be specified using the `source_content_type` query
   string parameter.
   
  
positive.code: [float]
  === Flat Settings
  
  The `flat_settings` flag affects rendering of the lists of settings. When
  `flat_settings` flag is `true` settings are returned in a flat format:
  
  [source,js]
  --------------------------------------------------
  
negative.code: date string ending with `||`. This anchor date can optionally be followed by
  one or more maths expressions:
  
  * `+1h`: Add one hour
  * `-1d`: Subtract one day
  * `/d`: Round down to the nearest day
  
  The supported time units differ from those supported by <<time-units, time units>> for durations.
  The supported units are:
  
  [horizontal]
  `y`:: Years
  `M`:: Months
  `w`:: Weeks
  `d`:: Days
  `h`:: Hours
  `H`:: Hours
  `m`:: Minutes
  `s`:: Seconds
  
  Assuming `now` is `2001-01-01 12:00:00`, some examples are:
  
  [horizontal]
  `now+1h`:: `now` in milliseconds plus one hour. Resolves to: `2001-01-01 13:00:00`
  `now-1h`:: `now` in milliseconds minus one hour. Resolves to: `2001-01-01 11:00:00`
  `now-1h/d`:: `now` in milliseconds minus one hour, rounded down to UTC 00:00. Resolves to: `2001-01-01 00:00:00`
   `2001.02.01\|\|+1M/d`:: `2001-02-01` in milliseconds plus one month. Resolves to: `2001-03-01 00:00:00`
  
  [float]
  