anchor.diff:      time. Defaults to unset, which means results are not
       limited to specific timestamps.
   
  -`from`::
  +`job_id`::
  +    (Optional, string) Specifies to get events for a specific {anomaly-job}
  +    identifier or job group. It must be used with a calendar identifier of `_all`
  +    or `*`.
  +
  +`page.from`::
       (Optional, integer) Skips the specified number of events. Defaults to `0`.
   
  -`size`::
  +`page.size`::
       (Optional, integer) Specifies the maximum number of events to obtain.
       Defaults to `100`.
   
   `start`::
       (Optional, string) Specifies to get events with timestamps after this time.
  -    Defaults to unset, which means results are not limited to
  -    specific timestamps.
  +    Defaults to unset, which means results are not limited to specific
  +    timestamps.
   
   [[ml-get-calendar-event-results]]
   == {api-response-body-title}
  
positive.code: // TESTRESPONSE[s/LS8LJGEBMTCMA-qz49st/$body.$_path/]
  // TESTRESPONSE[s/Li8LJGEBMTCMA-qz49st/$body.$_path/]
  // TESTRESPONSE[s/Ly8LJGEBMTCMA-qz49st/$body.$_path/]
  
negative.code: 
  You can get scheduled event information for multiple calendars in a single
  API request by using a comma-separated list of ids or a wildcard expression.
  You can get scheduled event information for all calendars by using `_all` or `*`
  as the `<calendar_id>`.
  
  For more information, see
  {ml-docs}/ml-ad-finding-anomalies.html#ml-ad-calendars[Calendars and scheduled events].
  