@opusdns/api 1.184.0 → 1.186.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/package.json +1 -1
  2. package/src/helpers/constants.ts +2 -0
  3. package/src/openapi.yaml +152 -153
  4. package/src/schema.d.ts +263 -251
package/src/schema.d.ts CHANGED
@@ -5695,7 +5695,7 @@ export interface components {
5695
5695
  * DomainAttributeKey
5696
5696
  * @enum {string}
5697
5697
  */
5698
- DomainAttributeKey: "auto_renew_period" | "music_registrant_attestation" | "nic_it_compliance_confirmation" | "travel_industry_acknowledgement" | "verification_required" | "de_general_request_contact" | "de_abuse_contact" | "nor_id_applicant_version" | "nor_id_applicant_accept_name" | "nor_id_applicant_accept_date" | "nor_id_declaration" | "nor_id_declaration_token" | "punktum_dk_terms_acceptance" | "punktum_dk_tracking_no" | "internet_ee_registrant_agreement" | "promotion" | "promotion_eligibility" | "domain_contact_attributes";
5698
+ DomainAttributeKey: "auto_renew_period" | "music_registrant_attestation" | "nic_it_compliance_confirmation" | "travel_industry_acknowledgement" | "verification_required" | "de_general_request_contact" | "de_abuse_contact" | "nor_id_applicant_version" | "nor_id_applicant_accept_name" | "nor_id_applicant_accept_date" | "nor_id_declaration" | "nor_id_declaration_token" | "punktum_dk_terms_acceptance" | "punktum_dk_tracking_no" | "internet_ee_registrant_agreement" | "promotion" | "promotion_eligibility" | "domain_contact_attributes" | "registry_reseller_id";
5699
5699
  /** DomainAvailability */
5700
5700
  DomainAvailability: {
5701
5701
  /** Domain */
@@ -5798,8 +5798,9 @@ export interface components {
5798
5798
  * Boolean keys also accept `1` and `yes`.
5799
5799
  *
5800
5800
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
5801
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
5802
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
5801
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
5802
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
5803
+ * `contacts` entry instead.
5803
5804
  *
5804
5805
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
5805
5806
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -5909,8 +5910,9 @@ export interface components {
5909
5910
  * Boolean keys also accept `1` and `yes`.
5910
5911
  *
5911
5912
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
5912
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
5913
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
5913
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
5914
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
5915
+ * `contacts` entry instead.
5914
5916
  *
5915
5917
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
5916
5918
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -5992,8 +5994,9 @@ export interface components {
5992
5994
  * Boolean keys also accept `1` and `yes`.
5993
5995
  *
5994
5996
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
5995
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
5996
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
5997
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
5998
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
5999
+ * `contacts` entry instead.
5997
6000
  *
5998
6001
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
5999
6002
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -6079,8 +6082,9 @@ export interface components {
6079
6082
  * Boolean keys also accept `1` and `yes`.
6080
6083
  *
6081
6084
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
6082
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
6083
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
6085
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
6086
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
6087
+ * `contacts` entry instead.
6084
6088
  *
6085
6089
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
6086
6090
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -7505,8 +7509,9 @@ export interface components {
7505
7509
  * Boolean keys also accept `1` and `yes`.
7506
7510
  *
7507
7511
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
7508
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
7509
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
7512
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
7513
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
7514
+ * `contacts` entry instead.
7510
7515
  *
7511
7516
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
7512
7517
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -7588,8 +7593,9 @@ export interface components {
7588
7593
  * Boolean keys also accept `1` and `yes`.
7589
7594
  *
7590
7595
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
7591
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
7592
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
7596
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
7597
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
7598
+ * `contacts` entry instead.
7593
7599
  *
7594
7600
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
7595
7601
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -7671,8 +7677,9 @@ export interface components {
7671
7677
  * Boolean keys also accept `1` and `yes`.
7672
7678
  *
7673
7679
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
7674
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
7675
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
7680
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
7681
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
7682
+ * `contacts` entry instead.
7676
7683
  *
7677
7684
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
7678
7685
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -7754,8 +7761,9 @@ export interface components {
7754
7761
  * Boolean keys also accept `1` and `yes`.
7755
7762
  *
7756
7763
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
7757
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
7758
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
7764
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
7765
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
7766
+ * `contacts` entry instead.
7759
7767
  *
7760
7768
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
7761
7769
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -7869,8 +7877,9 @@ export interface components {
7869
7877
  * Boolean keys also accept `1` and `yes`.
7870
7878
  *
7871
7879
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
7872
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
7873
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
7880
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
7881
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
7882
+ * `contacts` entry instead.
7874
7883
  *
7875
7884
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
7876
7885
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -7970,8 +7979,9 @@ export interface components {
7970
7979
  * Boolean keys also accept `1` and `yes`.
7971
7980
  *
7972
7981
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
7973
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
7974
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
7982
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
7983
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
7984
+ * `contacts` entry instead.
7975
7985
  *
7976
7986
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
7977
7987
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -8056,8 +8066,9 @@ export interface components {
8056
8066
  * Boolean keys also accept `1` and `yes`.
8057
8067
  *
8058
8068
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
8059
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
8060
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
8069
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
8070
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
8071
+ * `contacts` entry instead.
8061
8072
  *
8062
8073
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
8063
8074
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -8138,8 +8149,9 @@ export interface components {
8138
8149
  * Boolean keys also accept `1` and `yes`.
8139
8150
  *
8140
8151
  * Written by the platform and rejected if supplied: `verification_required`, `promotion`, `promotion_eligibility`,
8141
- * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`. They are never
8142
- * returned under `attributes`; inline contact attributes surface on the matching `contacts` entry instead.
8152
+ * `nor_id_declaration`, `nor_id_declaration_token`, `punktum_dk_tracking_no`, `domain_contact_attributes`,
8153
+ * `registry_reseller_id`. They are never returned under `attributes`; inline contact attributes surface on the matching
8154
+ * `contacts` entry instead.
8143
8155
  *
8144
8156
  * Derived from the signed `.no` applicant declaration and ignored if supplied on create: `nor_id_applicant_version`,
8145
8157
  * `nor_id_applicant_accept_name`, `nor_id_applicant_accept_date`.
@@ -14488,7 +14500,7 @@ export interface components {
14488
14500
  responses: never;
14489
14501
  parameters: {
14490
14502
  /**
14491
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14503
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
14492
14504
  * @example rfc3339
14493
14505
  */
14494
14506
  DatetimeFormatHeader: "rfc3339";
@@ -14504,7 +14516,7 @@ export interface operations {
14504
14516
  query?: never;
14505
14517
  header?: {
14506
14518
  /**
14507
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14519
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
14508
14520
  * @example rfc3339
14509
14521
  */
14510
14522
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -14596,7 +14608,7 @@ export interface operations {
14596
14608
  };
14597
14609
  header?: {
14598
14610
  /**
14599
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14611
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
14600
14612
  * @example rfc3339
14601
14613
  */
14602
14614
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -14679,7 +14691,7 @@ export interface operations {
14679
14691
  query?: never;
14680
14692
  header?: {
14681
14693
  /**
14682
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14694
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
14683
14695
  * @example rfc3339
14684
14696
  */
14685
14697
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -14766,7 +14778,7 @@ export interface operations {
14766
14778
  query?: never;
14767
14779
  header?: {
14768
14780
  /**
14769
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14781
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
14770
14782
  * @example rfc3339
14771
14783
  */
14772
14784
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -14851,7 +14863,7 @@ export interface operations {
14851
14863
  query?: never;
14852
14864
  header?: {
14853
14865
  /**
14854
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14866
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
14855
14867
  * @example rfc3339
14856
14868
  */
14857
14869
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -14935,7 +14947,7 @@ export interface operations {
14935
14947
  header?: {
14936
14948
  "If-Match"?: string | null;
14937
14949
  /**
14938
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14950
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
14939
14951
  * @example rfc3339
14940
14952
  */
14941
14953
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15027,7 +15039,7 @@ export interface operations {
15027
15039
  };
15028
15040
  header?: {
15029
15041
  /**
15030
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15042
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15031
15043
  * @example rfc3339
15032
15044
  */
15033
15045
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15112,7 +15124,7 @@ export interface operations {
15112
15124
  query?: never;
15113
15125
  header?: {
15114
15126
  /**
15115
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15127
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15116
15128
  * @example rfc3339
15117
15129
  */
15118
15130
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15208,7 +15220,7 @@ export interface operations {
15208
15220
  };
15209
15221
  header?: {
15210
15222
  /**
15211
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15223
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15212
15224
  * @example rfc3339
15213
15225
  */
15214
15226
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15293,7 +15305,7 @@ export interface operations {
15293
15305
  query?: never;
15294
15306
  header?: {
15295
15307
  /**
15296
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15308
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15297
15309
  * @example rfc3339
15298
15310
  */
15299
15311
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15382,7 +15394,7 @@ export interface operations {
15382
15394
  query?: never;
15383
15395
  header?: {
15384
15396
  /**
15385
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15397
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15386
15398
  * @example rfc3339
15387
15399
  */
15388
15400
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15472,7 +15484,7 @@ export interface operations {
15472
15484
  };
15473
15485
  header?: {
15474
15486
  /**
15475
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15487
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15476
15488
  * @example rfc3339
15477
15489
  */
15478
15490
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15555,7 +15567,7 @@ export interface operations {
15555
15567
  query?: never;
15556
15568
  header?: {
15557
15569
  /**
15558
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15570
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15559
15571
  * @example rfc3339
15560
15572
  */
15561
15573
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15642,7 +15654,7 @@ export interface operations {
15642
15654
  query?: never;
15643
15655
  header?: {
15644
15656
  /**
15645
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15657
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15646
15658
  * @example rfc3339
15647
15659
  */
15648
15660
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15725,7 +15737,7 @@ export interface operations {
15725
15737
  query?: never;
15726
15738
  header?: {
15727
15739
  /**
15728
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15740
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15729
15741
  * @example rfc3339
15730
15742
  */
15731
15743
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15823,7 +15835,7 @@ export interface operations {
15823
15835
  };
15824
15836
  header?: {
15825
15837
  /**
15826
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15838
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15827
15839
  * @example rfc3339
15828
15840
  */
15829
15841
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15868,7 +15880,7 @@ export interface operations {
15868
15880
  };
15869
15881
  header?: {
15870
15882
  /**
15871
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15883
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15872
15884
  * @example rfc3339
15873
15885
  */
15874
15886
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15919,7 +15931,7 @@ export interface operations {
15919
15931
  };
15920
15932
  header?: {
15921
15933
  /**
15922
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15934
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15923
15935
  * @example rfc3339
15924
15936
  */
15925
15937
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -15967,7 +15979,7 @@ export interface operations {
15967
15979
  };
15968
15980
  header?: {
15969
15981
  /**
15970
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15982
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
15971
15983
  * @example rfc3339
15972
15984
  */
15973
15985
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16022,7 +16034,7 @@ export interface operations {
16022
16034
  };
16023
16035
  header?: {
16024
16036
  /**
16025
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16037
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16026
16038
  * @example rfc3339
16027
16039
  */
16028
16040
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16057,7 +16069,7 @@ export interface operations {
16057
16069
  query?: never;
16058
16070
  header?: {
16059
16071
  /**
16060
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16072
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16061
16073
  * @example rfc3339
16062
16074
  */
16063
16075
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16108,7 +16120,7 @@ export interface operations {
16108
16120
  query?: never;
16109
16121
  header?: {
16110
16122
  /**
16111
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16123
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16112
16124
  * @example rfc3339
16113
16125
  */
16114
16126
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16203,7 +16215,7 @@ export interface operations {
16203
16215
  query?: never;
16204
16216
  header?: {
16205
16217
  /**
16206
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16218
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16207
16219
  * @example rfc3339
16208
16220
  */
16209
16221
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16255,7 +16267,7 @@ export interface operations {
16255
16267
  };
16256
16268
  header?: {
16257
16269
  /**
16258
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16270
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16259
16271
  * @example rfc3339
16260
16272
  */
16261
16273
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16311,7 +16323,7 @@ export interface operations {
16311
16323
  };
16312
16324
  header?: {
16313
16325
  /**
16314
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16326
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16315
16327
  * @example rfc3339
16316
16328
  */
16317
16329
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16362,7 +16374,7 @@ export interface operations {
16362
16374
  query?: never;
16363
16375
  header?: {
16364
16376
  /**
16365
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16377
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16366
16378
  * @example rfc3339
16367
16379
  */
16368
16380
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16438,7 +16450,7 @@ export interface operations {
16438
16450
  };
16439
16451
  header?: {
16440
16452
  /**
16441
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16453
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16442
16454
  * @example rfc3339
16443
16455
  */
16444
16456
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16473,7 +16485,7 @@ export interface operations {
16473
16485
  query?: never;
16474
16486
  header?: {
16475
16487
  /**
16476
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16488
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16477
16489
  * @example rfc3339
16478
16490
  */
16479
16491
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16519,7 +16531,7 @@ export interface operations {
16519
16531
  };
16520
16532
  header?: {
16521
16533
  /**
16522
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16534
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16523
16535
  * @example rfc3339
16524
16536
  */
16525
16537
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16554,7 +16566,7 @@ export interface operations {
16554
16566
  query?: never;
16555
16567
  header?: {
16556
16568
  /**
16557
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16569
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16558
16570
  * @example rfc3339
16559
16571
  */
16560
16572
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16610,7 +16622,7 @@ export interface operations {
16610
16622
  query?: never;
16611
16623
  header?: {
16612
16624
  /**
16613
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16625
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16614
16626
  * @example rfc3339
16615
16627
  */
16616
16628
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16664,7 +16676,7 @@ export interface operations {
16664
16676
  query?: never;
16665
16677
  header?: {
16666
16678
  /**
16667
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16679
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16668
16680
  * @example rfc3339
16669
16681
  */
16670
16682
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16716,7 +16728,7 @@ export interface operations {
16716
16728
  query?: never;
16717
16729
  header?: {
16718
16730
  /**
16719
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16731
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16720
16732
  * @example rfc3339
16721
16733
  */
16722
16734
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16793,7 +16805,7 @@ export interface operations {
16793
16805
  };
16794
16806
  header?: {
16795
16807
  /**
16796
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16808
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16797
16809
  * @example rfc3339
16798
16810
  */
16799
16811
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16863,7 +16875,7 @@ export interface operations {
16863
16875
  };
16864
16876
  header?: {
16865
16877
  /**
16866
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16878
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16867
16879
  * @example rfc3339
16868
16880
  */
16869
16881
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16940,7 +16952,7 @@ export interface operations {
16940
16952
  };
16941
16953
  header?: {
16942
16954
  /**
16943
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16955
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16944
16956
  * @example rfc3339
16945
16957
  */
16946
16958
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -16977,7 +16989,7 @@ export interface operations {
16977
16989
  };
16978
16990
  header?: {
16979
16991
  /**
16980
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16992
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
16981
16993
  * @example rfc3339
16982
16994
  */
16983
16995
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17031,7 +17043,7 @@ export interface operations {
17031
17043
  query?: never;
17032
17044
  header?: {
17033
17045
  /**
17034
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17046
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17035
17047
  * @example rfc3339
17036
17048
  */
17037
17049
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17099,7 +17111,7 @@ export interface operations {
17099
17111
  query?: never;
17100
17112
  header?: {
17101
17113
  /**
17102
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17114
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17103
17115
  * @example rfc3339
17104
17116
  */
17105
17117
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17164,7 +17176,7 @@ export interface operations {
17164
17176
  query?: never;
17165
17177
  header?: {
17166
17178
  /**
17167
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17179
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17168
17180
  * @example rfc3339
17169
17181
  */
17170
17182
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17236,7 +17248,7 @@ export interface operations {
17236
17248
  };
17237
17249
  header?: {
17238
17250
  /**
17239
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17251
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17240
17252
  * @example rfc3339
17241
17253
  */
17242
17254
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17331,7 +17343,7 @@ export interface operations {
17331
17343
  };
17332
17344
  header?: {
17333
17345
  /**
17334
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17346
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17335
17347
  * @example rfc3339
17336
17348
  */
17337
17349
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17417,7 +17429,7 @@ export interface operations {
17417
17429
  query?: never;
17418
17430
  header?: {
17419
17431
  /**
17420
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17432
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17421
17433
  * @example rfc3339
17422
17434
  */
17423
17435
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17485,7 +17497,7 @@ export interface operations {
17485
17497
  query?: never;
17486
17498
  header?: {
17487
17499
  /**
17488
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17500
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17489
17501
  * @example rfc3339
17490
17502
  */
17491
17503
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17578,7 +17590,7 @@ export interface operations {
17578
17590
  query?: never;
17579
17591
  header?: {
17580
17592
  /**
17581
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17593
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17582
17594
  * @example rfc3339
17583
17595
  */
17584
17596
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17704,7 +17716,7 @@ export interface operations {
17704
17716
  };
17705
17717
  header?: {
17706
17718
  /**
17707
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17719
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17708
17720
  * @example rfc3339
17709
17721
  */
17710
17722
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17739,7 +17751,7 @@ export interface operations {
17739
17751
  query?: never;
17740
17752
  header?: {
17741
17753
  /**
17742
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17754
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17743
17755
  * @example rfc3339
17744
17756
  */
17745
17757
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17800,7 +17812,7 @@ export interface operations {
17800
17812
  };
17801
17813
  header?: {
17802
17814
  /**
17803
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17815
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17804
17816
  * @example rfc3339
17805
17817
  */
17806
17818
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17873,7 +17885,7 @@ export interface operations {
17873
17885
  };
17874
17886
  header?: {
17875
17887
  /**
17876
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17888
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17877
17889
  * @example rfc3339
17878
17890
  */
17879
17891
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17940,7 +17952,7 @@ export interface operations {
17940
17952
  query?: never;
17941
17953
  header?: {
17942
17954
  /**
17943
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17955
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17944
17956
  * @example rfc3339
17945
17957
  */
17946
17958
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -17977,7 +17989,7 @@ export interface operations {
17977
17989
  };
17978
17990
  header?: {
17979
17991
  /**
17980
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17992
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
17981
17993
  * @example rfc3339
17982
17994
  */
17983
17995
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18015,7 +18027,7 @@ export interface operations {
18015
18027
  query?: never;
18016
18028
  header?: {
18017
18029
  /**
18018
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18030
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18019
18031
  * @example rfc3339
18020
18032
  */
18021
18033
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18051,7 +18063,7 @@ export interface operations {
18051
18063
  query?: never;
18052
18064
  header?: {
18053
18065
  /**
18054
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18066
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18055
18067
  * @example rfc3339
18056
18068
  */
18057
18069
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18105,7 +18117,7 @@ export interface operations {
18105
18117
  query?: never;
18106
18118
  header?: {
18107
18119
  /**
18108
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18120
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18109
18121
  * @example rfc3339
18110
18122
  */
18111
18123
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18186,7 +18198,7 @@ export interface operations {
18186
18198
  query?: never;
18187
18199
  header?: {
18188
18200
  /**
18189
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18201
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18190
18202
  * @example rfc3339
18191
18203
  */
18192
18204
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18256,7 +18268,7 @@ export interface operations {
18256
18268
  query?: never;
18257
18269
  header?: {
18258
18270
  /**
18259
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18271
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18260
18272
  * @example rfc3339
18261
18273
  */
18262
18274
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18326,7 +18338,7 @@ export interface operations {
18326
18338
  query?: never;
18327
18339
  header?: {
18328
18340
  /**
18329
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18341
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18330
18342
  * @example rfc3339
18331
18343
  */
18332
18344
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18410,7 +18422,7 @@ export interface operations {
18410
18422
  query?: never;
18411
18423
  header?: {
18412
18424
  /**
18413
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18425
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18414
18426
  * @example rfc3339
18415
18427
  */
18416
18428
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18495,7 +18507,7 @@ export interface operations {
18495
18507
  query?: never;
18496
18508
  header?: {
18497
18509
  /**
18498
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18510
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18499
18511
  * @example rfc3339
18500
18512
  */
18501
18513
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18583,7 +18595,7 @@ export interface operations {
18583
18595
  query?: never;
18584
18596
  header?: {
18585
18597
  /**
18586
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18598
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18587
18599
  * @example rfc3339
18588
18600
  */
18589
18601
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18647,7 +18659,7 @@ export interface operations {
18647
18659
  };
18648
18660
  header?: {
18649
18661
  /**
18650
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18662
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18651
18663
  * @example rfc3339
18652
18664
  */
18653
18665
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18714,7 +18726,7 @@ export interface operations {
18714
18726
  query?: never;
18715
18727
  header?: {
18716
18728
  /**
18717
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18729
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18718
18730
  * @example rfc3339
18719
18731
  */
18720
18732
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18818,7 +18830,7 @@ export interface operations {
18818
18830
  query?: never;
18819
18831
  header?: {
18820
18832
  /**
18821
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18833
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18822
18834
  * @example rfc3339
18823
18835
  */
18824
18836
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -18912,7 +18924,7 @@ export interface operations {
18912
18924
  };
18913
18925
  header?: {
18914
18926
  /**
18915
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18927
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
18916
18928
  * @example rfc3339
18917
18929
  */
18918
18930
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19016,7 +19028,7 @@ export interface operations {
19016
19028
  };
19017
19029
  header?: {
19018
19030
  /**
19019
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19031
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19020
19032
  * @example rfc3339
19021
19033
  */
19022
19034
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19120,7 +19132,7 @@ export interface operations {
19120
19132
  };
19121
19133
  header?: {
19122
19134
  /**
19123
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19135
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19124
19136
  * @example rfc3339
19125
19137
  */
19126
19138
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19224,7 +19236,7 @@ export interface operations {
19224
19236
  };
19225
19237
  header?: {
19226
19238
  /**
19227
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19239
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19228
19240
  * @example rfc3339
19229
19241
  */
19230
19242
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19328,7 +19340,7 @@ export interface operations {
19328
19340
  };
19329
19341
  header?: {
19330
19342
  /**
19331
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19343
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19332
19344
  * @example rfc3339
19333
19345
  */
19334
19346
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19432,7 +19444,7 @@ export interface operations {
19432
19444
  };
19433
19445
  header?: {
19434
19446
  /**
19435
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19447
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19436
19448
  * @example rfc3339
19437
19449
  */
19438
19450
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19536,7 +19548,7 @@ export interface operations {
19536
19548
  };
19537
19549
  header?: {
19538
19550
  /**
19539
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19551
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19540
19552
  * @example rfc3339
19541
19553
  */
19542
19554
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19640,7 +19652,7 @@ export interface operations {
19640
19652
  };
19641
19653
  header?: {
19642
19654
  /**
19643
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19655
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19644
19656
  * @example rfc3339
19645
19657
  */
19646
19658
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19746,7 +19758,7 @@ export interface operations {
19746
19758
  };
19747
19759
  header?: {
19748
19760
  /**
19749
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19761
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19750
19762
  * @example rfc3339
19751
19763
  */
19752
19764
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19841,7 +19853,7 @@ export interface operations {
19841
19853
  query?: never;
19842
19854
  header?: {
19843
19855
  /**
19844
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19856
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19845
19857
  * @example rfc3339
19846
19858
  */
19847
19859
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -19927,7 +19939,7 @@ export interface operations {
19927
19939
  query?: never;
19928
19940
  header?: {
19929
19941
  /**
19930
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19942
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
19931
19943
  * @example rfc3339
19932
19944
  */
19933
19945
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20033,7 +20045,7 @@ export interface operations {
20033
20045
  query?: never;
20034
20046
  header?: {
20035
20047
  /**
20036
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20048
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20037
20049
  * @example rfc3339
20038
20050
  */
20039
20051
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20117,7 +20129,7 @@ export interface operations {
20117
20129
  query?: never;
20118
20130
  header?: {
20119
20131
  /**
20120
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20132
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20121
20133
  * @example rfc3339
20122
20134
  */
20123
20135
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20185,7 +20197,7 @@ export interface operations {
20185
20197
  query?: never;
20186
20198
  header?: {
20187
20199
  /**
20188
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20200
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20189
20201
  * @example rfc3339
20190
20202
  */
20191
20203
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20253,7 +20265,7 @@ export interface operations {
20253
20265
  query?: never;
20254
20266
  header?: {
20255
20267
  /**
20256
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20268
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20257
20269
  * @example rfc3339
20258
20270
  */
20259
20271
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20340,7 +20352,7 @@ export interface operations {
20340
20352
  query?: never;
20341
20353
  header?: {
20342
20354
  /**
20343
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20355
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20344
20356
  * @example rfc3339
20345
20357
  */
20346
20358
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20431,7 +20443,7 @@ export interface operations {
20431
20443
  query?: never;
20432
20444
  header?: {
20433
20445
  /**
20434
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20446
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20435
20447
  * @example rfc3339
20436
20448
  */
20437
20449
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20525,7 +20537,7 @@ export interface operations {
20525
20537
  };
20526
20538
  header?: {
20527
20539
  /**
20528
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20540
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20529
20541
  * @example rfc3339
20530
20542
  */
20531
20543
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20633,7 +20645,7 @@ export interface operations {
20633
20645
  };
20634
20646
  header?: {
20635
20647
  /**
20636
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20648
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20637
20649
  * @example rfc3339
20638
20650
  */
20639
20651
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20668,7 +20680,7 @@ export interface operations {
20668
20680
  query?: never;
20669
20681
  header?: {
20670
20682
  /**
20671
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20683
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20672
20684
  * @example rfc3339
20673
20685
  */
20674
20686
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20767,7 +20779,7 @@ export interface operations {
20767
20779
  };
20768
20780
  header?: {
20769
20781
  /**
20770
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20782
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20771
20783
  * @example rfc3339
20772
20784
  */
20773
20785
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20802,7 +20814,7 @@ export interface operations {
20802
20814
  query?: never;
20803
20815
  header?: {
20804
20816
  /**
20805
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20817
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20806
20818
  * @example rfc3339
20807
20819
  */
20808
20820
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20880,7 +20892,7 @@ export interface operations {
20880
20892
  };
20881
20893
  header?: {
20882
20894
  /**
20883
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20895
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20884
20896
  * @example rfc3339
20885
20897
  */
20886
20898
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20915,7 +20927,7 @@ export interface operations {
20915
20927
  query?: never;
20916
20928
  header?: {
20917
20929
  /**
20918
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20930
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20919
20931
  * @example rfc3339
20920
20932
  */
20921
20933
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -20950,7 +20962,7 @@ export interface operations {
20950
20962
  query?: never;
20951
20963
  header?: {
20952
20964
  /**
20953
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20965
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
20954
20966
  * @example rfc3339
20955
20967
  */
20956
20968
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21008,7 +21020,7 @@ export interface operations {
21008
21020
  query?: never;
21009
21021
  header?: {
21010
21022
  /**
21011
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21023
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21012
21024
  * @example rfc3339
21013
21025
  */
21014
21026
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21080,7 +21092,7 @@ export interface operations {
21080
21092
  query?: never;
21081
21093
  header?: {
21082
21094
  /**
21083
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21095
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21084
21096
  * @example rfc3339
21085
21097
  */
21086
21098
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21152,7 +21164,7 @@ export interface operations {
21152
21164
  query?: never;
21153
21165
  header?: {
21154
21166
  /**
21155
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21167
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21156
21168
  * @example rfc3339
21157
21169
  */
21158
21170
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21224,7 +21236,7 @@ export interface operations {
21224
21236
  query?: never;
21225
21237
  header?: {
21226
21238
  /**
21227
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21239
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21228
21240
  * @example rfc3339
21229
21241
  */
21230
21242
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21282,7 +21294,7 @@ export interface operations {
21282
21294
  query?: never;
21283
21295
  header?: {
21284
21296
  /**
21285
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21297
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21286
21298
  * @example rfc3339
21287
21299
  */
21288
21300
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21354,7 +21366,7 @@ export interface operations {
21354
21366
  query?: never;
21355
21367
  header?: {
21356
21368
  /**
21357
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21369
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21358
21370
  * @example rfc3339
21359
21371
  */
21360
21372
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21426,7 +21438,7 @@ export interface operations {
21426
21438
  query?: never;
21427
21439
  header?: {
21428
21440
  /**
21429
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21441
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21430
21442
  * @example rfc3339
21431
21443
  */
21432
21444
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21500,7 +21512,7 @@ export interface operations {
21500
21512
  };
21501
21513
  header?: {
21502
21514
  /**
21503
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21515
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21504
21516
  * @example rfc3339
21505
21517
  */
21506
21518
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21553,7 +21565,7 @@ export interface operations {
21553
21565
  };
21554
21566
  header?: {
21555
21567
  /**
21556
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21568
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21557
21569
  * @example rfc3339
21558
21570
  */
21559
21571
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21640,7 +21652,7 @@ export interface operations {
21640
21652
  query?: never;
21641
21653
  header?: {
21642
21654
  /**
21643
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21655
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21644
21656
  * @example rfc3339
21645
21657
  */
21646
21658
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21724,7 +21736,7 @@ export interface operations {
21724
21736
  query?: never;
21725
21737
  header?: {
21726
21738
  /**
21727
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21739
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21728
21740
  * @example rfc3339
21729
21741
  */
21730
21742
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21785,7 +21797,7 @@ export interface operations {
21785
21797
  query?: never;
21786
21798
  header?: {
21787
21799
  /**
21788
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21800
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21789
21801
  * @example rfc3339
21790
21802
  */
21791
21803
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21857,7 +21869,7 @@ export interface operations {
21857
21869
  query?: never;
21858
21870
  header?: {
21859
21871
  /**
21860
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21872
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21861
21873
  * @example rfc3339
21862
21874
  */
21863
21875
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -21929,7 +21941,7 @@ export interface operations {
21929
21941
  query?: never;
21930
21942
  header?: {
21931
21943
  /**
21932
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21944
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
21933
21945
  * @example rfc3339
21934
21946
  */
21935
21947
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22001,7 +22013,7 @@ export interface operations {
22001
22013
  query?: never;
22002
22014
  header?: {
22003
22015
  /**
22004
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22016
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22005
22017
  * @example rfc3339
22006
22018
  */
22007
22019
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22103,7 +22115,7 @@ export interface operations {
22103
22115
  };
22104
22116
  header?: {
22105
22117
  /**
22106
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22118
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22107
22119
  * @example rfc3339
22108
22120
  */
22109
22121
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22157,7 +22169,7 @@ export interface operations {
22157
22169
  query?: never;
22158
22170
  header?: {
22159
22171
  /**
22160
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22172
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22161
22173
  * @example rfc3339
22162
22174
  */
22163
22175
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22227,7 +22239,7 @@ export interface operations {
22227
22239
  query?: never;
22228
22240
  header?: {
22229
22241
  /**
22230
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22242
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22231
22243
  * @example rfc3339
22232
22244
  */
22233
22245
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22277,7 +22289,7 @@ export interface operations {
22277
22289
  query?: never;
22278
22290
  header?: {
22279
22291
  /**
22280
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22292
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22281
22293
  * @example rfc3339
22282
22294
  */
22283
22295
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22331,7 +22343,7 @@ export interface operations {
22331
22343
  query?: never;
22332
22344
  header?: {
22333
22345
  /**
22334
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22346
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22335
22347
  * @example rfc3339
22336
22348
  */
22337
22349
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22389,7 +22401,7 @@ export interface operations {
22389
22401
  query?: never;
22390
22402
  header?: {
22391
22403
  /**
22392
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22404
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22393
22405
  * @example rfc3339
22394
22406
  */
22395
22407
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22441,7 +22453,7 @@ export interface operations {
22441
22453
  query?: never;
22442
22454
  header?: {
22443
22455
  /**
22444
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22456
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22445
22457
  * @example rfc3339
22446
22458
  */
22447
22459
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22493,7 +22505,7 @@ export interface operations {
22493
22505
  query?: never;
22494
22506
  header?: {
22495
22507
  /**
22496
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22508
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22497
22509
  * @example rfc3339
22498
22510
  */
22499
22511
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22565,7 +22577,7 @@ export interface operations {
22565
22577
  query?: never;
22566
22578
  header?: {
22567
22579
  /**
22568
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22580
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22569
22581
  * @example rfc3339
22570
22582
  */
22571
22583
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22606,7 +22618,7 @@ export interface operations {
22606
22618
  query?: never;
22607
22619
  header?: {
22608
22620
  /**
22609
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22621
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22610
22622
  * @example rfc3339
22611
22623
  */
22612
22624
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22647,7 +22659,7 @@ export interface operations {
22647
22659
  query?: never;
22648
22660
  header?: {
22649
22661
  /**
22650
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22662
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22651
22663
  * @example rfc3339
22652
22664
  */
22653
22665
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22717,7 +22729,7 @@ export interface operations {
22717
22729
  query?: never;
22718
22730
  header?: {
22719
22731
  /**
22720
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22732
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22721
22733
  * @example rfc3339
22722
22734
  */
22723
22735
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22808,7 +22820,7 @@ export interface operations {
22808
22820
  };
22809
22821
  header?: {
22810
22822
  /**
22811
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22823
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22812
22824
  * @example rfc3339
22813
22825
  */
22814
22826
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22875,7 +22887,7 @@ export interface operations {
22875
22887
  query?: never;
22876
22888
  header?: {
22877
22889
  /**
22878
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22890
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22879
22891
  * @example rfc3339
22880
22892
  */
22881
22893
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -22990,7 +23002,7 @@ export interface operations {
22990
23002
  query?: never;
22991
23003
  header?: {
22992
23004
  /**
22993
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23005
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
22994
23006
  * @example rfc3339
22995
23007
  */
22996
23008
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23075,7 +23087,7 @@ export interface operations {
23075
23087
  query?: never;
23076
23088
  header?: {
23077
23089
  /**
23078
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23090
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23079
23091
  * @example rfc3339
23080
23092
  */
23081
23093
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23142,7 +23154,7 @@ export interface operations {
23142
23154
  query?: never;
23143
23155
  header?: {
23144
23156
  /**
23145
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23157
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23146
23158
  * @example rfc3339
23147
23159
  */
23148
23160
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23247,7 +23259,7 @@ export interface operations {
23247
23259
  query?: never;
23248
23260
  header?: {
23249
23261
  /**
23250
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23262
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23251
23263
  * @example rfc3339
23252
23264
  */
23253
23265
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23338,7 +23350,7 @@ export interface operations {
23338
23350
  query?: never;
23339
23351
  header?: {
23340
23352
  /**
23341
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23353
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23342
23354
  * @example rfc3339
23343
23355
  */
23344
23356
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23423,7 +23435,7 @@ export interface operations {
23423
23435
  query?: never;
23424
23436
  header?: {
23425
23437
  /**
23426
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23438
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23427
23439
  * @example rfc3339
23428
23440
  */
23429
23441
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23506,7 +23518,7 @@ export interface operations {
23506
23518
  query?: never;
23507
23519
  header?: {
23508
23520
  /**
23509
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23521
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23510
23522
  * @example rfc3339
23511
23523
  */
23512
23524
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23592,7 +23604,7 @@ export interface operations {
23592
23604
  };
23593
23605
  header?: {
23594
23606
  /**
23595
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23607
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23596
23608
  * @example rfc3339
23597
23609
  */
23598
23610
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23687,7 +23699,7 @@ export interface operations {
23687
23699
  };
23688
23700
  header?: {
23689
23701
  /**
23690
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23702
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23691
23703
  * @example rfc3339
23692
23704
  */
23693
23705
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23738,7 +23750,7 @@ export interface operations {
23738
23750
  query?: never;
23739
23751
  header?: {
23740
23752
  /**
23741
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23753
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23742
23754
  * @example rfc3339
23743
23755
  */
23744
23756
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23808,7 +23820,7 @@ export interface operations {
23808
23820
  query?: never;
23809
23821
  header?: {
23810
23822
  /**
23811
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23823
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23812
23824
  * @example rfc3339
23813
23825
  */
23814
23826
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23876,7 +23888,7 @@ export interface operations {
23876
23888
  query?: never;
23877
23889
  header?: {
23878
23890
  /**
23879
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23891
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23880
23892
  * @example rfc3339
23881
23893
  */
23882
23894
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -23990,7 +24002,7 @@ export interface operations {
23990
24002
  query?: never;
23991
24003
  header?: {
23992
24004
  /**
23993
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24005
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
23994
24006
  * @example rfc3339
23995
24007
  */
23996
24008
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24068,7 +24080,7 @@ export interface operations {
24068
24080
  query?: never;
24069
24081
  header?: {
24070
24082
  /**
24071
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24083
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24072
24084
  * @example rfc3339
24073
24085
  */
24074
24086
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24150,7 +24162,7 @@ export interface operations {
24150
24162
  query?: never;
24151
24163
  header?: {
24152
24164
  /**
24153
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24165
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24154
24166
  * @example rfc3339
24155
24167
  */
24156
24168
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24243,7 +24255,7 @@ export interface operations {
24243
24255
  query?: never;
24244
24256
  header?: {
24245
24257
  /**
24246
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24258
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24247
24259
  * @example rfc3339
24248
24260
  */
24249
24261
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24298,7 +24310,7 @@ export interface operations {
24298
24310
  query?: never;
24299
24311
  header?: {
24300
24312
  /**
24301
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24313
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24302
24314
  * @example rfc3339
24303
24315
  */
24304
24316
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24351,7 +24363,7 @@ export interface operations {
24351
24363
  query?: never;
24352
24364
  header?: {
24353
24365
  /**
24354
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24366
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24355
24367
  * @example rfc3339
24356
24368
  */
24357
24369
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24404,7 +24416,7 @@ export interface operations {
24404
24416
  query?: never;
24405
24417
  header?: {
24406
24418
  /**
24407
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24419
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24408
24420
  * @example rfc3339
24409
24421
  */
24410
24422
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24459,7 +24471,7 @@ export interface operations {
24459
24471
  query?: never;
24460
24472
  header?: {
24461
24473
  /**
24462
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24474
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24463
24475
  * @example rfc3339
24464
24476
  */
24465
24477
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24541,7 +24553,7 @@ export interface operations {
24541
24553
  };
24542
24554
  header?: {
24543
24555
  /**
24544
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24556
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24545
24557
  * @example rfc3339
24546
24558
  */
24547
24559
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24576,7 +24588,7 @@ export interface operations {
24576
24588
  query?: never;
24577
24589
  header?: {
24578
24590
  /**
24579
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24591
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24580
24592
  * @example rfc3339
24581
24593
  */
24582
24594
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24648,7 +24660,7 @@ export interface operations {
24648
24660
  query?: never;
24649
24661
  header?: {
24650
24662
  /**
24651
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24663
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24652
24664
  * @example rfc3339
24653
24665
  */
24654
24666
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24720,7 +24732,7 @@ export interface operations {
24720
24732
  query?: never;
24721
24733
  header?: {
24722
24734
  /**
24723
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24735
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24724
24736
  * @example rfc3339
24725
24737
  */
24726
24738
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24784,7 +24796,7 @@ export interface operations {
24784
24796
  };
24785
24797
  header?: {
24786
24798
  /**
24787
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24799
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24788
24800
  * @example rfc3339
24789
24801
  */
24790
24802
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24856,7 +24868,7 @@ export interface operations {
24856
24868
  query?: never;
24857
24869
  header?: {
24858
24870
  /**
24859
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24871
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24860
24872
  * @example rfc3339
24861
24873
  */
24862
24874
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24909,7 +24921,7 @@ export interface operations {
24909
24921
  query?: never;
24910
24922
  header?: {
24911
24923
  /**
24912
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24924
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24913
24925
  * @example rfc3339
24914
24926
  */
24915
24927
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -24965,7 +24977,7 @@ export interface operations {
24965
24977
  };
24966
24978
  header?: {
24967
24979
  /**
24968
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24980
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
24969
24981
  * @example rfc3339
24970
24982
  */
24971
24983
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25027,7 +25039,7 @@ export interface operations {
25027
25039
  };
25028
25040
  header?: {
25029
25041
  /**
25030
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25042
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25031
25043
  * @example rfc3339
25032
25044
  */
25033
25045
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25094,7 +25106,7 @@ export interface operations {
25094
25106
  query?: never;
25095
25107
  header?: {
25096
25108
  /**
25097
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25109
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25098
25110
  * @example rfc3339
25099
25111
  */
25100
25112
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25168,7 +25180,7 @@ export interface operations {
25168
25180
  };
25169
25181
  header?: {
25170
25182
  /**
25171
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25183
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25172
25184
  * @example rfc3339
25173
25185
  */
25174
25186
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25235,7 +25247,7 @@ export interface operations {
25235
25247
  query?: never;
25236
25248
  header?: {
25237
25249
  /**
25238
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25250
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25239
25251
  * @example rfc3339
25240
25252
  */
25241
25253
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25314,7 +25326,7 @@ export interface operations {
25314
25326
  query?: never;
25315
25327
  header?: {
25316
25328
  /**
25317
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25329
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25318
25330
  * @example rfc3339
25319
25331
  */
25320
25332
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25381,7 +25393,7 @@ export interface operations {
25381
25393
  query?: never;
25382
25394
  header?: {
25383
25395
  /**
25384
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25396
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25385
25397
  * @example rfc3339
25386
25398
  */
25387
25399
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25452,7 +25464,7 @@ export interface operations {
25452
25464
  query?: never;
25453
25465
  header?: {
25454
25466
  /**
25455
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25467
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25456
25468
  * @example rfc3339
25457
25469
  */
25458
25470
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25521,7 +25533,7 @@ export interface operations {
25521
25533
  query?: never;
25522
25534
  header?: {
25523
25535
  /**
25524
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25536
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25525
25537
  * @example rfc3339
25526
25538
  */
25527
25539
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25588,7 +25600,7 @@ export interface operations {
25588
25600
  query?: never;
25589
25601
  header?: {
25590
25602
  /**
25591
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25603
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25592
25604
  * @example rfc3339
25593
25605
  */
25594
25606
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25661,7 +25673,7 @@ export interface operations {
25661
25673
  query?: never;
25662
25674
  header?: {
25663
25675
  /**
25664
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25676
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25665
25677
  * @example rfc3339
25666
25678
  */
25667
25679
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25728,7 +25740,7 @@ export interface operations {
25728
25740
  query?: never;
25729
25741
  header?: {
25730
25742
  /**
25731
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25743
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25732
25744
  * @example rfc3339
25733
25745
  */
25734
25746
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25795,7 +25807,7 @@ export interface operations {
25795
25807
  query?: never;
25796
25808
  header?: {
25797
25809
  /**
25798
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25810
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25799
25811
  * @example rfc3339
25800
25812
  */
25801
25813
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25882,7 +25894,7 @@ export interface operations {
25882
25894
  query?: never;
25883
25895
  header?: {
25884
25896
  /**
25885
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25897
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25886
25898
  * @example rfc3339
25887
25899
  */
25888
25900
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -25968,7 +25980,7 @@ export interface operations {
25968
25980
  query?: never;
25969
25981
  header?: {
25970
25982
  /**
25971
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25983
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
25972
25984
  * @example rfc3339
25973
25985
  */
25974
25986
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26070,7 +26082,7 @@ export interface operations {
26070
26082
  query?: never;
26071
26083
  header?: {
26072
26084
  /**
26073
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26085
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26074
26086
  * @example rfc3339
26075
26087
  */
26076
26088
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26183,7 +26195,7 @@ export interface operations {
26183
26195
  };
26184
26196
  header?: {
26185
26197
  /**
26186
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26198
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26187
26199
  * @example rfc3339
26188
26200
  */
26189
26201
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26250,7 +26262,7 @@ export interface operations {
26250
26262
  query?: never;
26251
26263
  header?: {
26252
26264
  /**
26253
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26265
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26254
26266
  * @example rfc3339
26255
26267
  */
26256
26268
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26319,7 +26331,7 @@ export interface operations {
26319
26331
  query?: never;
26320
26332
  header?: {
26321
26333
  /**
26322
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26334
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26323
26335
  * @example rfc3339
26324
26336
  */
26325
26337
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26386,7 +26398,7 @@ export interface operations {
26386
26398
  query?: never;
26387
26399
  header?: {
26388
26400
  /**
26389
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26401
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26390
26402
  * @example rfc3339
26391
26403
  */
26392
26404
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26462,7 +26474,7 @@ export interface operations {
26462
26474
  };
26463
26475
  header?: {
26464
26476
  /**
26465
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26477
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26466
26478
  * @example rfc3339
26467
26479
  */
26468
26480
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26531,7 +26543,7 @@ export interface operations {
26531
26543
  query?: never;
26532
26544
  header?: {
26533
26545
  /**
26534
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26546
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26535
26547
  * @example rfc3339
26536
26548
  */
26537
26549
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26615,7 +26627,7 @@ export interface operations {
26615
26627
  };
26616
26628
  header?: {
26617
26629
  /**
26618
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26630
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26619
26631
  * @example rfc3339
26620
26632
  */
26621
26633
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26655,7 +26667,7 @@ export interface operations {
26655
26667
  };
26656
26668
  header?: {
26657
26669
  /**
26658
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26670
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26659
26671
  * @example rfc3339
26660
26672
  */
26661
26673
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26695,7 +26707,7 @@ export interface operations {
26695
26707
  };
26696
26708
  header?: {
26697
26709
  /**
26698
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26710
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26699
26711
  * @example rfc3339
26700
26712
  */
26701
26713
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26778,7 +26790,7 @@ export interface operations {
26778
26790
  };
26779
26791
  header?: {
26780
26792
  /**
26781
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26793
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26782
26794
  * @example rfc3339
26783
26795
  */
26784
26796
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26847,7 +26859,7 @@ export interface operations {
26847
26859
  query?: never;
26848
26860
  header?: {
26849
26861
  /**
26850
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26862
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26851
26863
  * @example rfc3339
26852
26864
  */
26853
26865
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26924,7 +26936,7 @@ export interface operations {
26924
26936
  };
26925
26937
  header?: {
26926
26938
  /**
26927
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
26939
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
26928
26940
  * @example rfc3339
26929
26941
  */
26930
26942
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -26999,7 +27011,7 @@ export interface operations {
26999
27011
  };
27000
27012
  header?: {
27001
27013
  /**
27002
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27014
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27003
27015
  * @example rfc3339
27004
27016
  */
27005
27017
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27079,7 +27091,7 @@ export interface operations {
27079
27091
  };
27080
27092
  header?: {
27081
27093
  /**
27082
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27094
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27083
27095
  * @example rfc3339
27084
27096
  */
27085
27097
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27149,7 +27161,7 @@ export interface operations {
27149
27161
  };
27150
27162
  header?: {
27151
27163
  /**
27152
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27164
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27153
27165
  * @example rfc3339
27154
27166
  */
27155
27167
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27216,7 +27228,7 @@ export interface operations {
27216
27228
  query?: never;
27217
27229
  header?: {
27218
27230
  /**
27219
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27231
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27220
27232
  * @example rfc3339
27221
27233
  */
27222
27234
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27287,7 +27299,7 @@ export interface operations {
27287
27299
  query?: never;
27288
27300
  header?: {
27289
27301
  /**
27290
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27302
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27291
27303
  * @example rfc3339
27292
27304
  */
27293
27305
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27357,7 +27369,7 @@ export interface operations {
27357
27369
  };
27358
27370
  header?: {
27359
27371
  /**
27360
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27372
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27361
27373
  * @example rfc3339
27362
27374
  */
27363
27375
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27450,7 +27462,7 @@ export interface operations {
27450
27462
  };
27451
27463
  header?: {
27452
27464
  /**
27453
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27465
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27454
27466
  * @example rfc3339
27455
27467
  */
27456
27468
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27485,7 +27497,7 @@ export interface operations {
27485
27497
  query?: never;
27486
27498
  header?: {
27487
27499
  /**
27488
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27500
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27489
27501
  * @example rfc3339
27490
27502
  */
27491
27503
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27524,7 +27536,7 @@ export interface operations {
27524
27536
  query?: never;
27525
27537
  header?: {
27526
27538
  /**
27527
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27539
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27528
27540
  * @example rfc3339
27529
27541
  */
27530
27542
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27561,7 +27573,7 @@ export interface operations {
27561
27573
  query?: never;
27562
27574
  header?: {
27563
27575
  /**
27564
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27576
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27565
27577
  * @example rfc3339
27566
27578
  */
27567
27579
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27606,7 +27618,7 @@ export interface operations {
27606
27618
  };
27607
27619
  header?: {
27608
27620
  /**
27609
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27621
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27610
27622
  * @example rfc3339
27611
27623
  */
27612
27624
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27657,7 +27669,7 @@ export interface operations {
27657
27669
  query?: never;
27658
27670
  header?: {
27659
27671
  /**
27660
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27672
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27661
27673
  * @example rfc3339
27662
27674
  */
27663
27675
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27729,7 +27741,7 @@ export interface operations {
27729
27741
  query?: never;
27730
27742
  header?: {
27731
27743
  /**
27732
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27744
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27733
27745
  * @example rfc3339
27734
27746
  */
27735
27747
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27818,7 +27830,7 @@ export interface operations {
27818
27830
  query?: never;
27819
27831
  header?: {
27820
27832
  /**
27821
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27833
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27822
27834
  * @example rfc3339
27823
27835
  */
27824
27836
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27888,7 +27900,7 @@ export interface operations {
27888
27900
  query?: never;
27889
27901
  header?: {
27890
27902
  /**
27891
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27903
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27892
27904
  * @example rfc3339
27893
27905
  */
27894
27906
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -27956,7 +27968,7 @@ export interface operations {
27956
27968
  query?: never;
27957
27969
  header?: {
27958
27970
  /**
27959
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
27971
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
27960
27972
  * @example rfc3339
27961
27973
  */
27962
27974
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28047,7 +28059,7 @@ export interface operations {
28047
28059
  query?: never;
28048
28060
  header?: {
28049
28061
  /**
28050
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28062
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28051
28063
  * @example rfc3339
28052
28064
  */
28053
28065
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28124,7 +28136,7 @@ export interface operations {
28124
28136
  };
28125
28137
  header?: {
28126
28138
  /**
28127
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28139
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28128
28140
  * @example rfc3339
28129
28141
  */
28130
28142
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28163,7 +28175,7 @@ export interface operations {
28163
28175
  query?: never;
28164
28176
  header?: {
28165
28177
  /**
28166
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28178
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28167
28179
  * @example rfc3339
28168
28180
  */
28169
28181
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28205,7 +28217,7 @@ export interface operations {
28205
28217
  };
28206
28218
  header?: {
28207
28219
  /**
28208
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28220
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28209
28221
  * @example rfc3339
28210
28222
  */
28211
28223
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28258,7 +28270,7 @@ export interface operations {
28258
28270
  query?: never;
28259
28271
  header?: {
28260
28272
  /**
28261
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28273
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28262
28274
  * @example rfc3339
28263
28275
  */
28264
28276
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28299,7 +28311,7 @@ export interface operations {
28299
28311
  };
28300
28312
  header?: {
28301
28313
  /**
28302
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28314
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28303
28315
  * @example rfc3339
28304
28316
  */
28305
28317
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28336,7 +28348,7 @@ export interface operations {
28336
28348
  };
28337
28349
  header?: {
28338
28350
  /**
28339
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28351
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28340
28352
  * @example rfc3339
28341
28353
  */
28342
28354
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28373,7 +28385,7 @@ export interface operations {
28373
28385
  query?: never;
28374
28386
  header?: {
28375
28387
  /**
28376
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28388
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28377
28389
  * @example rfc3339
28378
28390
  */
28379
28391
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28417,7 +28429,7 @@ export interface operations {
28417
28429
  query?: never;
28418
28430
  header?: {
28419
28431
  /**
28420
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28432
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28421
28433
  * @example rfc3339
28422
28434
  */
28423
28435
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28458,7 +28470,7 @@ export interface operations {
28458
28470
  query?: never;
28459
28471
  header?: {
28460
28472
  /**
28461
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28473
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28462
28474
  * @example rfc3339
28463
28475
  */
28464
28476
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28495,7 +28507,7 @@ export interface operations {
28495
28507
  query?: never;
28496
28508
  header?: {
28497
28509
  /**
28498
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28510
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28499
28511
  * @example rfc3339
28500
28512
  */
28501
28513
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28532,7 +28544,7 @@ export interface operations {
28532
28544
  query?: never;
28533
28545
  header?: {
28534
28546
  /**
28535
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28547
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28536
28548
  * @example rfc3339
28537
28549
  */
28538
28550
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28609,7 +28621,7 @@ export interface operations {
28609
28621
  };
28610
28622
  header?: {
28611
28623
  /**
28612
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28624
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28613
28625
  * @example rfc3339
28614
28626
  */
28615
28627
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28644,7 +28656,7 @@ export interface operations {
28644
28656
  query?: never;
28645
28657
  header?: {
28646
28658
  /**
28647
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28659
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28648
28660
  * @example rfc3339
28649
28661
  */
28650
28662
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28683,7 +28695,7 @@ export interface operations {
28683
28695
  query?: never;
28684
28696
  header?: {
28685
28697
  /**
28686
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28698
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28687
28699
  * @example rfc3339
28688
28700
  */
28689
28701
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28722,7 +28734,7 @@ export interface operations {
28722
28734
  query?: never;
28723
28735
  header?: {
28724
28736
  /**
28725
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28737
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28726
28738
  * @example rfc3339
28727
28739
  */
28728
28740
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28757,7 +28769,7 @@ export interface operations {
28757
28769
  query?: never;
28758
28770
  header?: {
28759
28771
  /**
28760
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28772
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28761
28773
  * @example rfc3339
28762
28774
  */
28763
28775
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28794,7 +28806,7 @@ export interface operations {
28794
28806
  query?: never;
28795
28807
  header?: {
28796
28808
  /**
28797
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28809
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28798
28810
  * @example rfc3339
28799
28811
  */
28800
28812
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28831,7 +28843,7 @@ export interface operations {
28831
28843
  query?: never;
28832
28844
  header?: {
28833
28845
  /**
28834
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28846
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28835
28847
  * @example rfc3339
28836
28848
  */
28837
28849
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28872,7 +28884,7 @@ export interface operations {
28872
28884
  query?: never;
28873
28885
  header?: {
28874
28886
  /**
28875
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28887
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28876
28888
  * @example rfc3339
28877
28889
  */
28878
28890
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28909,7 +28921,7 @@ export interface operations {
28909
28921
  query?: never;
28910
28922
  header?: {
28911
28923
  /**
28912
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28924
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28913
28925
  * @example rfc3339
28914
28926
  */
28915
28927
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28946,7 +28958,7 @@ export interface operations {
28946
28958
  query?: never;
28947
28959
  header?: {
28948
28960
  /**
28949
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
28961
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28950
28962
  * @example rfc3339
28951
28963
  */
28952
28964
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -28986,7 +28998,7 @@ export interface operations {
28986
28998
  };
28987
28999
  header?: {
28988
29000
  /**
28989
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29001
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
28990
29002
  * @example rfc3339
28991
29003
  */
28992
29004
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29023,7 +29035,7 @@ export interface operations {
29023
29035
  query?: never;
29024
29036
  header?: {
29025
29037
  /**
29026
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29038
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29027
29039
  * @example rfc3339
29028
29040
  */
29029
29041
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29058,7 +29070,7 @@ export interface operations {
29058
29070
  query?: never;
29059
29071
  header?: {
29060
29072
  /**
29061
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29073
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29062
29074
  * @example rfc3339
29063
29075
  */
29064
29076
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29097,7 +29109,7 @@ export interface operations {
29097
29109
  query?: never;
29098
29110
  header?: {
29099
29111
  /**
29100
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29112
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29101
29113
  * @example rfc3339
29102
29114
  */
29103
29115
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29136,7 +29148,7 @@ export interface operations {
29136
29148
  query?: never;
29137
29149
  header?: {
29138
29150
  /**
29139
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29151
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29140
29152
  * @example rfc3339
29141
29153
  */
29142
29154
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29171,7 +29183,7 @@ export interface operations {
29171
29183
  query?: never;
29172
29184
  header?: {
29173
29185
  /**
29174
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29186
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29175
29187
  * @example rfc3339
29176
29188
  */
29177
29189
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29210,7 +29222,7 @@ export interface operations {
29210
29222
  query?: never;
29211
29223
  header?: {
29212
29224
  /**
29213
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29225
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29214
29226
  * @example rfc3339
29215
29227
  */
29216
29228
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29245,7 +29257,7 @@ export interface operations {
29245
29257
  query?: never;
29246
29258
  header?: {
29247
29259
  /**
29248
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29260
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29249
29261
  * @example rfc3339
29250
29262
  */
29251
29263
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29280,7 +29292,7 @@ export interface operations {
29280
29292
  query?: never;
29281
29293
  header?: {
29282
29294
  /**
29283
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29295
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29284
29296
  * @example rfc3339
29285
29297
  */
29286
29298
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29319,7 +29331,7 @@ export interface operations {
29319
29331
  query?: never;
29320
29332
  header?: {
29321
29333
  /**
29322
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29334
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29323
29335
  * @example rfc3339
29324
29336
  */
29325
29337
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29358,7 +29370,7 @@ export interface operations {
29358
29370
  query?: never;
29359
29371
  header?: {
29360
29372
  /**
29361
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29373
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29362
29374
  * @example rfc3339
29363
29375
  */
29364
29376
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29397,7 +29409,7 @@ export interface operations {
29397
29409
  query?: never;
29398
29410
  header?: {
29399
29411
  /**
29400
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29412
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29401
29413
  * @example rfc3339
29402
29414
  */
29403
29415
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29432,7 +29444,7 @@ export interface operations {
29432
29444
  query?: never;
29433
29445
  header?: {
29434
29446
  /**
29435
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29447
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29436
29448
  * @example rfc3339
29437
29449
  */
29438
29450
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29471,7 +29483,7 @@ export interface operations {
29471
29483
  query?: never;
29472
29484
  header?: {
29473
29485
  /**
29474
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29486
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29475
29487
  * @example rfc3339
29476
29488
  */
29477
29489
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
@@ -29506,7 +29518,7 @@ export interface operations {
29506
29518
  query?: never;
29507
29519
  header?: {
29508
29520
  /**
29509
- * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
29521
+ * @description Accepted for backwards compatibility; has no effect. Response datetimes are always normalized to UTC and serialized as RFC 3339 with a `Z` suffix, whether or not this header is sent.
29510
29522
  * @example rfc3339
29511
29523
  */
29512
29524
  "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];