cloudflare 7.0.0 → 7.1.0

package/src/resources/radar/dns/timeseries-groups.ts

@@ -1629,6 +1629,9 @@ export interface TimeseriesGroupCacheHitParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -1648,19 +1651,35 @@ export interface TimeseriesGroupCacheHitParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -1812,7 +1831,10 @@ export interface TimeseriesGroupCacheHitParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -1822,6 +1844,9 @@ export interface TimeseriesGroupDNSSECParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -1841,19 +1866,35 @@ export interface TimeseriesGroupDNSSECParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -2005,7 +2046,10 @@ export interface TimeseriesGroupDNSSECParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -2015,6 +2059,9 @@ export interface TimeseriesGroupDNSSECAwareParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -2034,19 +2081,35 @@ export interface TimeseriesGroupDNSSECAwareParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -2198,7 +2261,10 @@ export interface TimeseriesGroupDNSSECAwareParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -2208,6 +2274,9 @@ export interface TimeseriesGroupDNSSECE2EParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -2227,19 +2296,35 @@ export interface TimeseriesGroupDNSSECE2EParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -2391,7 +2476,10 @@ export interface TimeseriesGroupDNSSECE2EParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -2401,6 +2489,9 @@ export interface TimeseriesGroupIPVersionParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -2420,19 +2511,35 @@ export interface TimeseriesGroupIPVersionParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -2584,7 +2691,10 @@ export interface TimeseriesGroupIPVersionParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -2594,6 +2704,9 @@ export interface TimeseriesGroupMatchingAnswerParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -2613,19 +2726,35 @@ export interface TimeseriesGroupMatchingAnswerParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -2777,7 +2906,10 @@ export interface TimeseriesGroupMatchingAnswerParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -2787,6 +2919,9 @@ export interface TimeseriesGroupProtocolParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -2806,19 +2941,35 @@ export interface TimeseriesGroupProtocolParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -2965,7 +3116,10 @@ export interface TimeseriesGroupProtocolParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -2975,6 +3129,9 @@ export interface TimeseriesGroupQueryTypeParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -2994,19 +3151,35 @@ export interface TimeseriesGroupQueryTypeParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -3018,7 +3191,8 @@ export interface TimeseriesGroupQueryTypeParams {
   /**
    * Limits the number of objects per group to the top items within the specified
    * time range. When item count exceeds the limit, extra items appear grouped under
-   * an "other" category.
+   * an "other" category. Only supported on high-cardinality dimensions; otherwise
+   * the request is rejected. Minimum value is 2.
    */
   limitPerGroup?: number;
 
@@ -3070,7 +3244,10 @@ export interface TimeseriesGroupQueryTypeParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -3080,6 +3257,9 @@ export interface TimeseriesGroupResponseCodeParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -3099,19 +3279,35 @@ export interface TimeseriesGroupResponseCodeParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -3123,7 +3319,8 @@ export interface TimeseriesGroupResponseCodeParams {
   /**
    * Limits the number of objects per group to the top items within the specified
    * time range. When item count exceeds the limit, extra items appear grouped under
-   * an "other" category.
+   * an "other" category. Only supported on high-cardinality dimensions; otherwise
+   * the request is rejected. Minimum value is 2.
    */
   limitPerGroup?: number;
 
@@ -3245,7 +3442,10 @@ export interface TimeseriesGroupResponseCodeParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }
@@ -3255,6 +3455,9 @@ export interface TimeseriesGroupResponseTTLParams {
    * Aggregation interval of the results (e.g., in 15 minutes or 1 hour intervals).
    * Refer to
    * [Aggregation intervals](https://developers.cloudflare.com/radar/concepts/aggregation-intervals/).
+   * When omitted, the interval is auto-selected from the requested date range; finer
+   * intervals are only available for shorter ranges. If the requested interval is
+   * too granular for the date range, the request is rejected.
    */
   aggInterval?: '15m' | '1h' | '1d' | '1w';
 
@@ -3274,19 +3477,35 @@ export interface TimeseriesGroupResponseTTLParams {
   continent?: Array<string>;
 
   /**
-   * End of the date range (inclusive).
+   * End of the date range (inclusive). Alternative to `dateRange`; provide together
+   * with `dateStart`. When requesting comparison series, every series must resolve
+   * to the same duration as the main series. Each `dateStart`/`dateEnd` is floored
+   * to the nearest 15 minutes before evaluation, so windows whose durations match
+   * only before alignment may be rejected.
    */
   dateEnd?: Array<string>;
 
   /**
-   * Filters results by date range. For example, use `7d` and `7dcontrol` to compare
-   * this week with the previous week. Use this parameter or set specific start and
-   * end dates (`dateStart` and `dateEnd` parameters).
+   * Filters results by relative date range ending at the current time, with each
+   * value producing a separate series. Use `<n>d` for days (up to `364d`) or `<n>w`
+   * for weeks (up to `52w`). Append `control` to request the equivalent previous
+   * period for comparison: the comparison window is shifted back by the current
+   * window's length rounded up to a whole number of weeks, so it keeps the same
+   * weekday alignment and does not overlap the current window (e.g. `7dcontrol`
+   * covers days -14 to -7, `10dcontrol` covers days -24 to -14). For example, pass
+   * `7d` and `7dcontrol` to compare this week with the previous week. All series
+   * must resolve to the same duration as the main series; relative ranges (including
+   * `control`) satisfy this automatically. Use this parameter or set specific start
+   * and end dates (`dateStart` and `dateEnd` parameters).
    */
   dateRange?: Array<string>;
 
   /**
-   * Start of the date range.
+   * Start of the date range. Alternative to `dateRange`; provide together with
+   * `dateEnd`. When requesting comparison series, every series must resolve to the
+   * same duration as the main series. Each `dateStart`/`dateEnd` is floored to the
+   * nearest 15 minutes before evaluation, so windows whose durations match only
+   * before alignment may be rejected.
    */
   dateStart?: Array<string>;
 
@@ -3438,7 +3657,10 @@ export interface TimeseriesGroupResponseTTLParams {
   >;
 
   /**
-   * Filters results by top-level domain.
+   * Filters results by top-level domain. Incompatible with the `ipVersion`,
+   * `protocol`, `dnssecE2e`, `dnssecAware`, `responseTtl`, and `cacheHit`
+   * filters/dimensions; this restriction does not apply to country-code TLDs
+   * (2-letter, e.g. `uk`).
    */
   tld?: Array<string>;
 }