@opusdns/api 1.66.0 → 1.67.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.
package/src/schema.d.ts CHANGED
@@ -11950,7 +11950,13 @@ export interface components {
11950
11950
  };
11951
11951
  };
11952
11952
  responses: never;
11953
- parameters: never;
11953
+ parameters: {
11954
+ /**
11955
+ * @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.
11956
+ * @example rfc3339
11957
+ */
11958
+ DatetimeFormatHeader: "rfc3339";
11959
+ };
11954
11960
  requestBodies: never;
11955
11961
  headers: never;
11956
11962
  pathItems: never;
@@ -11960,7 +11966,13 @@ export interface operations {
11960
11966
  get_context_v1_ai_concierge_contexts__context_id__get: {
11961
11967
  parameters: {
11962
11968
  query?: never;
11963
- header?: never;
11969
+ header?: {
11970
+ /**
11971
+ * @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.
11972
+ * @example rfc3339
11973
+ */
11974
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
11975
+ };
11964
11976
  path: {
11965
11977
  context_id: TypeId<"ctx">;
11966
11978
  };
@@ -12046,7 +12058,13 @@ export interface operations {
12046
12058
  /** @description Full-text search on title/summary. */
12047
12059
  q?: string | null;
12048
12060
  };
12049
- header?: never;
12061
+ header?: {
12062
+ /**
12063
+ * @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.
12064
+ * @example rfc3339
12065
+ */
12066
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12067
+ };
12050
12068
  path?: never;
12051
12069
  cookie?: never;
12052
12070
  };
@@ -12123,7 +12141,13 @@ export interface operations {
12123
12141
  create_conversation_v1_ai_concierge_conversations_post: {
12124
12142
  parameters: {
12125
12143
  query?: never;
12126
- header?: never;
12144
+ header?: {
12145
+ /**
12146
+ * @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.
12147
+ * @example rfc3339
12148
+ */
12149
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12150
+ };
12127
12151
  path?: never;
12128
12152
  cookie?: never;
12129
12153
  };
@@ -12204,7 +12228,13 @@ export interface operations {
12204
12228
  get_conversation_v1_ai_concierge_conversations__conversation_id__get: {
12205
12229
  parameters: {
12206
12230
  query?: never;
12207
- header?: never;
12231
+ header?: {
12232
+ /**
12233
+ * @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.
12234
+ * @example rfc3339
12235
+ */
12236
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12237
+ };
12208
12238
  path: {
12209
12239
  conversation_id: TypeId<"conv">;
12210
12240
  };
@@ -12283,7 +12313,13 @@ export interface operations {
12283
12313
  delete_conversation_v1_ai_concierge_conversations__conversation_id__delete: {
12284
12314
  parameters: {
12285
12315
  query?: never;
12286
- header?: never;
12316
+ header?: {
12317
+ /**
12318
+ * @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.
12319
+ * @example rfc3339
12320
+ */
12321
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12322
+ };
12287
12323
  path: {
12288
12324
  conversation_id: TypeId<"conv">;
12289
12325
  };
@@ -12362,6 +12398,11 @@ export interface operations {
12362
12398
  query?: never;
12363
12399
  header?: {
12364
12400
  "If-Match"?: string | null;
12401
+ /**
12402
+ * @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.
12403
+ * @example rfc3339
12404
+ */
12405
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12365
12406
  };
12366
12407
  path: {
12367
12408
  conversation_id: TypeId<"conv">;
@@ -12448,7 +12489,13 @@ export interface operations {
12448
12489
  page?: number;
12449
12490
  page_size?: number;
12450
12491
  };
12451
- header?: never;
12492
+ header?: {
12493
+ /**
12494
+ * @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.
12495
+ * @example rfc3339
12496
+ */
12497
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12498
+ };
12452
12499
  path: {
12453
12500
  conversation_id: TypeId<"conv">;
12454
12501
  };
@@ -12527,7 +12574,13 @@ export interface operations {
12527
12574
  create_context_v1_ai_concierge_conversations__conversation_id__contexts_post: {
12528
12575
  parameters: {
12529
12576
  query?: never;
12530
- header?: never;
12577
+ header?: {
12578
+ /**
12579
+ * @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.
12580
+ * @example rfc3339
12581
+ */
12582
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12583
+ };
12531
12584
  path: {
12532
12585
  conversation_id: TypeId<"conv">;
12533
12586
  };
@@ -12617,7 +12670,13 @@ export interface operations {
12617
12670
  /** @description Comma-separated tokens to exclude (case-insensitive). Supports `tools`. */
12618
12671
  exclude?: string | null;
12619
12672
  };
12620
- header?: never;
12673
+ header?: {
12674
+ /**
12675
+ * @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.
12676
+ * @example rfc3339
12677
+ */
12678
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12679
+ };
12621
12680
  path: {
12622
12681
  conversation_id: TypeId<"conv">;
12623
12682
  };
@@ -12696,7 +12755,13 @@ export interface operations {
12696
12755
  create_message_v1_ai_concierge_conversations__conversation_id__messages_post: {
12697
12756
  parameters: {
12698
12757
  query?: never;
12699
- header?: never;
12758
+ header?: {
12759
+ /**
12760
+ * @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.
12761
+ * @example rfc3339
12762
+ */
12763
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12764
+ };
12700
12765
  path: {
12701
12766
  conversation_id: TypeId<"conv">;
12702
12767
  };
@@ -12779,7 +12844,13 @@ export interface operations {
12779
12844
  get_message_v1_ai_concierge_conversations__conversation_id__messages__message_id__get: {
12780
12845
  parameters: {
12781
12846
  query?: never;
12782
- header?: never;
12847
+ header?: {
12848
+ /**
12849
+ * @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.
12850
+ * @example rfc3339
12851
+ */
12852
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12853
+ };
12783
12854
  path: {
12784
12855
  conversation_id: TypeId<"conv">;
12785
12856
  message_id: TypeId<"msg">;
@@ -12863,7 +12934,13 @@ export interface operations {
12863
12934
  cursor?: string | null;
12864
12935
  kind?: string | null;
12865
12936
  };
12866
- header?: never;
12937
+ header?: {
12938
+ /**
12939
+ * @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.
12940
+ * @example rfc3339
12941
+ */
12942
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12943
+ };
12867
12944
  path?: never;
12868
12945
  cookie?: never;
12869
12946
  };
@@ -12940,7 +13017,13 @@ export interface operations {
12940
13017
  create_memory_fact_v1_ai_concierge_memory_facts_post: {
12941
13018
  parameters: {
12942
13019
  query?: never;
12943
- header?: never;
13020
+ header?: {
13021
+ /**
13022
+ * @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.
13023
+ * @example rfc3339
13024
+ */
13025
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13026
+ };
12944
13027
  path?: never;
12945
13028
  cookie?: never;
12946
13029
  };
@@ -13021,7 +13104,13 @@ export interface operations {
13021
13104
  delete_memory_fact_v1_ai_concierge_memory_facts__fact_id__delete: {
13022
13105
  parameters: {
13023
13106
  query?: never;
13024
- header?: never;
13107
+ header?: {
13108
+ /**
13109
+ * @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.
13110
+ * @example rfc3339
13111
+ */
13112
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13113
+ };
13025
13114
  path: {
13026
13115
  fact_id: TypeId<"fact">;
13027
13116
  };
@@ -13098,7 +13187,13 @@ export interface operations {
13098
13187
  patch_memory_fact_v1_ai_concierge_memory_facts__fact_id__patch: {
13099
13188
  parameters: {
13100
13189
  query?: never;
13101
- header?: never;
13190
+ header?: {
13191
+ /**
13192
+ * @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.
13193
+ * @example rfc3339
13194
+ */
13195
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13196
+ };
13102
13197
  path: {
13103
13198
  fact_id: TypeId<"fact">;
13104
13199
  };
@@ -13190,7 +13285,13 @@ export interface operations {
13190
13285
  start_time?: Date | null;
13191
13286
  end_time?: Date | null;
13192
13287
  };
13193
- header?: never;
13288
+ header?: {
13289
+ /**
13290
+ * @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.
13291
+ * @example rfc3339
13292
+ */
13293
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13294
+ };
13194
13295
  path: {
13195
13296
  email_forward_alias_id: TypeId<"email_forward_alias">;
13196
13297
  };
@@ -13229,7 +13330,13 @@ export interface operations {
13229
13330
  start_time?: Date | null;
13230
13331
  end_time?: Date | null;
13231
13332
  };
13232
- header?: never;
13333
+ header?: {
13334
+ /**
13335
+ * @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.
13336
+ * @example rfc3339
13337
+ */
13338
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13339
+ };
13233
13340
  path: {
13234
13341
  email_forward_id: TypeId<"email_forward">;
13235
13342
  };
@@ -13274,7 +13381,13 @@ export interface operations {
13274
13381
  created_after?: Date | null;
13275
13382
  object_id?: string | null;
13276
13383
  };
13277
- header?: never;
13384
+ header?: {
13385
+ /**
13386
+ * @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.
13387
+ * @example rfc3339
13388
+ */
13389
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13390
+ };
13278
13391
  path?: never;
13279
13392
  cookie?: never;
13280
13393
  };
@@ -13316,7 +13429,13 @@ export interface operations {
13316
13429
  created_before?: Date | null;
13317
13430
  created_after?: Date | null;
13318
13431
  };
13319
- header?: never;
13432
+ header?: {
13433
+ /**
13434
+ * @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.
13435
+ * @example rfc3339
13436
+ */
13437
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13438
+ };
13320
13439
  path: {
13321
13440
  object_id: string;
13322
13441
  };
@@ -13365,7 +13484,13 @@ export interface operations {
13365
13484
  request_started_before?: Date | null;
13366
13485
  request_started_after?: Date | null;
13367
13486
  };
13368
- header?: never;
13487
+ header?: {
13488
+ /**
13489
+ * @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.
13490
+ * @example rfc3339
13491
+ */
13492
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13493
+ };
13369
13494
  path?: never;
13370
13495
  cookie?: never;
13371
13496
  };
@@ -13394,7 +13519,13 @@ export interface operations {
13394
13519
  introspect_client_credential_v1_auth_client_credentials_introspect_get: {
13395
13520
  parameters: {
13396
13521
  query?: never;
13397
- header?: never;
13522
+ header?: {
13523
+ /**
13524
+ * @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.
13525
+ * @example rfc3339
13526
+ */
13527
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13528
+ };
13398
13529
  path?: never;
13399
13530
  cookie?: never;
13400
13531
  };
@@ -13439,7 +13570,13 @@ export interface operations {
13439
13570
  issue_organization_token_v1_auth_token_post: {
13440
13571
  parameters: {
13441
13572
  query?: never;
13442
- header?: never;
13573
+ header?: {
13574
+ /**
13575
+ * @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.
13576
+ * @example rfc3339
13577
+ */
13578
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13579
+ };
13443
13580
  path?: never;
13444
13581
  cookie?: never;
13445
13582
  };
@@ -13485,7 +13622,13 @@ export interface operations {
13485
13622
  * */
13486
13623
  domains: string[];
13487
13624
  };
13488
- header?: never;
13625
+ header?: {
13626
+ /**
13627
+ * @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.
13628
+ * @example rfc3339
13629
+ */
13630
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13631
+ };
13489
13632
  path?: never;
13490
13633
  cookie?: never;
13491
13634
  };
@@ -13535,7 +13678,13 @@ export interface operations {
13535
13678
  * */
13536
13679
  domains: string[];
13537
13680
  };
13538
- header?: never;
13681
+ header?: {
13682
+ /**
13683
+ * @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.
13684
+ * @example rfc3339
13685
+ */
13686
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13687
+ };
13539
13688
  path?: never;
13540
13689
  cookie?: never;
13541
13690
  };
@@ -13580,7 +13729,13 @@ export interface operations {
13580
13729
  stream_availability_post_v1_availability_stream_post: {
13581
13730
  parameters: {
13582
13731
  query?: never;
13583
- header?: never;
13732
+ header?: {
13733
+ /**
13734
+ * @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.
13735
+ * @example rfc3339
13736
+ */
13737
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13738
+ };
13584
13739
  path?: never;
13585
13740
  cookie?: never;
13586
13741
  };
@@ -13649,7 +13804,13 @@ export interface operations {
13649
13804
  /** @description Include additional data in the response. Can be specified multiple times. */
13650
13805
  include?: components["schemas"]["ContactIncludeField"][] | null;
13651
13806
  };
13652
- header?: never;
13807
+ header?: {
13808
+ /**
13809
+ * @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.
13810
+ * @example rfc3339
13811
+ */
13812
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13813
+ };
13653
13814
  path?: never;
13654
13815
  cookie?: never;
13655
13816
  };
@@ -13678,7 +13839,13 @@ export interface operations {
13678
13839
  create_contact_v1_contacts_post: {
13679
13840
  parameters: {
13680
13841
  query?: never;
13681
- header?: never;
13842
+ header?: {
13843
+ /**
13844
+ * @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.
13845
+ * @example rfc3339
13846
+ */
13847
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13848
+ };
13682
13849
  path?: never;
13683
13850
  cookie?: never;
13684
13851
  };
@@ -13718,7 +13885,13 @@ export interface operations {
13718
13885
  tld?: string | null;
13719
13886
  label?: string | null;
13720
13887
  };
13721
- header?: never;
13888
+ header?: {
13889
+ /**
13890
+ * @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.
13891
+ * @example rfc3339
13892
+ */
13893
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13894
+ };
13722
13895
  path?: never;
13723
13896
  cookie?: never;
13724
13897
  };
@@ -13747,7 +13920,13 @@ export interface operations {
13747
13920
  create_attribute_set_v1_contacts_attribute_sets_post: {
13748
13921
  parameters: {
13749
13922
  query?: never;
13750
- header?: never;
13923
+ header?: {
13924
+ /**
13925
+ * @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.
13926
+ * @example rfc3339
13927
+ */
13928
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13929
+ };
13751
13930
  path?: never;
13752
13931
  cookie?: never;
13753
13932
  };
@@ -13797,7 +13976,13 @@ export interface operations {
13797
13976
  get_attribute_set_v1_contacts_attribute_sets__contact_attribute_set_id__get: {
13798
13977
  parameters: {
13799
13978
  query?: never;
13800
- header?: never;
13979
+ header?: {
13980
+ /**
13981
+ * @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.
13982
+ * @example rfc3339
13983
+ */
13984
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13985
+ };
13801
13986
  path: {
13802
13987
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
13803
13988
  };
@@ -13845,7 +14030,13 @@ export interface operations {
13845
14030
  delete_attribute_set_v1_contacts_attribute_sets__contact_attribute_set_id__delete: {
13846
14031
  parameters: {
13847
14032
  query?: never;
13848
- header?: never;
14033
+ header?: {
14034
+ /**
14035
+ * @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.
14036
+ * @example rfc3339
14037
+ */
14038
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14039
+ };
13849
14040
  path: {
13850
14041
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
13851
14042
  };
@@ -13891,7 +14082,13 @@ export interface operations {
13891
14082
  update_attribute_set_v1_contacts_attribute_sets__contact_attribute_set_id__patch: {
13892
14083
  parameters: {
13893
14084
  query?: never;
13894
- header?: never;
14085
+ header?: {
14086
+ /**
14087
+ * @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.
14088
+ * @example rfc3339
14089
+ */
14090
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14091
+ };
13895
14092
  path: {
13896
14093
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
13897
14094
  };
@@ -13962,7 +14159,13 @@ export interface operations {
13962
14159
  query: {
13963
14160
  token: string;
13964
14161
  };
13965
- header?: never;
14162
+ header?: {
14163
+ /**
14164
+ * @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.
14165
+ * @example rfc3339
14166
+ */
14167
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14168
+ };
13966
14169
  path?: never;
13967
14170
  cookie?: never;
13968
14171
  };
@@ -14026,7 +14229,13 @@ export interface operations {
14026
14229
  query: {
14027
14230
  token: string;
14028
14231
  };
14029
- header?: never;
14232
+ header?: {
14233
+ /**
14234
+ * @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.
14235
+ * @example rfc3339
14236
+ */
14237
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14238
+ };
14030
14239
  path?: never;
14031
14240
  cookie?: never;
14032
14241
  };
@@ -14097,7 +14306,13 @@ export interface operations {
14097
14306
  query: {
14098
14307
  token: string;
14099
14308
  };
14100
- header?: never;
14309
+ header?: {
14310
+ /**
14311
+ * @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.
14312
+ * @example rfc3339
14313
+ */
14314
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14315
+ };
14101
14316
  path?: never;
14102
14317
  cookie?: never;
14103
14318
  };
@@ -14128,7 +14343,13 @@ export interface operations {
14128
14343
  query?: {
14129
14344
  include?: components["schemas"]["ContactIncludeField"][] | null;
14130
14345
  };
14131
- header?: never;
14346
+ header?: {
14347
+ /**
14348
+ * @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.
14349
+ * @example rfc3339
14350
+ */
14351
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14352
+ };
14132
14353
  path: {
14133
14354
  contact_id: TypeId<"contact">;
14134
14355
  };
@@ -14176,7 +14397,13 @@ export interface operations {
14176
14397
  delete_contact_v1_contacts__contact_id__delete: {
14177
14398
  parameters: {
14178
14399
  query?: never;
14179
- header?: never;
14400
+ header?: {
14401
+ /**
14402
+ * @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.
14403
+ * @example rfc3339
14404
+ */
14405
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14406
+ };
14180
14407
  path: {
14181
14408
  contact_id: TypeId<"contact">;
14182
14409
  };
@@ -14238,7 +14465,13 @@ export interface operations {
14238
14465
  create_attribute_link_v1_contacts__contact_id__link__contact_attribute_set_id__patch: {
14239
14466
  parameters: {
14240
14467
  query?: never;
14241
- header?: never;
14468
+ header?: {
14469
+ /**
14470
+ * @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.
14471
+ * @example rfc3339
14472
+ */
14473
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14474
+ };
14242
14475
  path: {
14243
14476
  contact_id: TypeId<"contact">;
14244
14477
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
@@ -14297,7 +14530,13 @@ export interface operations {
14297
14530
  get_verification_status_v1_contacts__contact_id__verification_get: {
14298
14531
  parameters: {
14299
14532
  query?: never;
14300
- header?: never;
14533
+ header?: {
14534
+ /**
14535
+ * @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.
14536
+ * @example rfc3339
14537
+ */
14538
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14539
+ };
14301
14540
  path: {
14302
14541
  contact_id: TypeId<"contact">;
14303
14542
  };
@@ -14363,7 +14602,13 @@ export interface operations {
14363
14602
  query: {
14364
14603
  token: string;
14365
14604
  };
14366
- header?: never;
14605
+ header?: {
14606
+ /**
14607
+ * @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.
14608
+ * @example rfc3339
14609
+ */
14610
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14611
+ };
14367
14612
  path: {
14368
14613
  contact_id: TypeId<"contact">;
14369
14614
  };
@@ -14452,7 +14697,13 @@ export interface operations {
14452
14697
  query: {
14453
14698
  type: components["schemas"]["VerificationType"];
14454
14699
  };
14455
- header?: never;
14700
+ header?: {
14701
+ /**
14702
+ * @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.
14703
+ * @example rfc3339
14704
+ */
14705
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14706
+ };
14456
14707
  path: {
14457
14708
  contact_id: TypeId<"contact">;
14458
14709
  };
@@ -14532,7 +14783,13 @@ export interface operations {
14532
14783
  cancel_verification_v1_contacts__contact_id__verification_delete: {
14533
14784
  parameters: {
14534
14785
  query?: never;
14535
- header?: never;
14786
+ header?: {
14787
+ /**
14788
+ * @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.
14789
+ * @example rfc3339
14790
+ */
14791
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14792
+ };
14536
14793
  path: {
14537
14794
  contact_id: TypeId<"contact">;
14538
14795
  };
@@ -14594,7 +14851,13 @@ export interface operations {
14594
14851
  get_contact_verification_status_v1_contacts__contact_id__verifications_get: {
14595
14852
  parameters: {
14596
14853
  query?: never;
14597
- header?: never;
14854
+ header?: {
14855
+ /**
14856
+ * @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.
14857
+ * @example rfc3339
14858
+ */
14859
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14860
+ };
14598
14861
  path: {
14599
14862
  contact_id: TypeId<"contact">;
14600
14863
  };
@@ -14674,7 +14937,13 @@ export interface operations {
14674
14937
  attest_contact_verification_v1_contacts__contact_id__verifications_attest_post: {
14675
14938
  parameters: {
14676
14939
  query?: never;
14677
- header?: never;
14940
+ header?: {
14941
+ /**
14942
+ * @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.
14943
+ * @example rfc3339
14944
+ */
14945
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14946
+ };
14678
14947
  path: {
14679
14948
  contact_id: TypeId<"contact">;
14680
14949
  };
@@ -14794,7 +15063,13 @@ export interface operations {
14794
15063
  /** @description Include additional data in the response. Can be specified multiple times. */
14795
15064
  include?: components["schemas"]["ZoneIncludeField"][] | null;
14796
15065
  };
14797
- header?: never;
15066
+ header?: {
15067
+ /**
15068
+ * @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.
15069
+ * @example rfc3339
15070
+ */
15071
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15072
+ };
14798
15073
  path?: never;
14799
15074
  cookie?: never;
14800
15075
  };
@@ -14823,7 +15098,13 @@ export interface operations {
14823
15098
  create_zone_v1_dns_post: {
14824
15099
  parameters: {
14825
15100
  query?: never;
14826
- header?: never;
15101
+ header?: {
15102
+ /**
15103
+ * @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.
15104
+ * @example rfc3339
15105
+ */
15106
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15107
+ };
14827
15108
  path?: never;
14828
15109
  cookie?: never;
14829
15110
  };
@@ -14878,7 +15159,13 @@ export interface operations {
14878
15159
  sort_by?: components["schemas"]["DomainForwardZoneSortField"];
14879
15160
  sort_order?: components["schemas"]["SortOrder"];
14880
15161
  };
14881
- header?: never;
15162
+ header?: {
15163
+ /**
15164
+ * @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.
15165
+ * @example rfc3339
15166
+ */
15167
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15168
+ };
14882
15169
  path?: never;
14883
15170
  cookie?: never;
14884
15171
  };
@@ -14945,7 +15232,13 @@ export interface operations {
14945
15232
  sort_by?: components["schemas"]["EmailForwardZoneSortField"];
14946
15233
  sort_order?: components["schemas"]["SortOrder"];
14947
15234
  };
14948
- header?: never;
15235
+ header?: {
15236
+ /**
15237
+ * @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.
15238
+ * @example rfc3339
15239
+ */
15240
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15241
+ };
14949
15242
  path?: never;
14950
15243
  cookie?: never;
14951
15244
  };
@@ -15006,7 +15299,13 @@ export interface operations {
15006
15299
  get_zones_summary_v1_dns_summary_get: {
15007
15300
  parameters: {
15008
15301
  query?: never;
15009
- header?: never;
15302
+ header?: {
15303
+ /**
15304
+ * @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.
15305
+ * @example rfc3339
15306
+ */
15307
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15308
+ };
15010
15309
  path?: never;
15011
15310
  cookie?: never;
15012
15311
  };
@@ -15037,7 +15336,13 @@ export interface operations {
15037
15336
  query?: {
15038
15337
  include?: components["schemas"]["ZoneIncludeField"][] | null;
15039
15338
  };
15040
- header?: never;
15339
+ header?: {
15340
+ /**
15341
+ * @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.
15342
+ * @example rfc3339
15343
+ */
15344
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15345
+ };
15041
15346
  path: {
15042
15347
  /** @description DNS zone name (trailing dot optional) */
15043
15348
  zone_name: string;
@@ -15069,7 +15374,13 @@ export interface operations {
15069
15374
  delete_zone_v1_dns__zone_name__delete: {
15070
15375
  parameters: {
15071
15376
  query?: never;
15072
- header?: never;
15377
+ header?: {
15378
+ /**
15379
+ * @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.
15380
+ * @example rfc3339
15381
+ */
15382
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15383
+ };
15073
15384
  path: {
15074
15385
  /** @description DNS zone name (trailing dot optional) */
15075
15386
  zone_name: string;
@@ -15099,7 +15410,13 @@ export interface operations {
15099
15410
  disable_dnssec_v1_dns__zone_name__dnssec_disable_post: {
15100
15411
  parameters: {
15101
15412
  query?: never;
15102
- header?: never;
15413
+ header?: {
15414
+ /**
15415
+ * @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.
15416
+ * @example rfc3339
15417
+ */
15418
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15419
+ };
15103
15420
  path: {
15104
15421
  /** @description DNS zone name (trailing dot optional) */
15105
15422
  zone_name: string;
@@ -15147,7 +15464,13 @@ export interface operations {
15147
15464
  enable_dnssec_v1_dns__zone_name__dnssec_enable_post: {
15148
15465
  parameters: {
15149
15466
  query?: never;
15150
- header?: never;
15467
+ header?: {
15468
+ /**
15469
+ * @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.
15470
+ * @example rfc3339
15471
+ */
15472
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15473
+ };
15151
15474
  path: {
15152
15475
  /** @description DNS zone name (trailing dot optional) */
15153
15476
  zone_name: string;
@@ -15195,7 +15518,13 @@ export interface operations {
15195
15518
  list_zone_domain_forwards_v1_dns__zone_name__domain_forwards_get: {
15196
15519
  parameters: {
15197
15520
  query?: never;
15198
- header?: never;
15521
+ header?: {
15522
+ /**
15523
+ * @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.
15524
+ * @example rfc3339
15525
+ */
15526
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15527
+ };
15199
15528
  path: {
15200
15529
  /** @description DNS zone name (trailing dot optional) */
15201
15530
  zone_name: string;
@@ -15259,7 +15588,13 @@ export interface operations {
15259
15588
  list_zone_email_forwards_v1_dns__zone_name__email_forwards_get: {
15260
15589
  parameters: {
15261
15590
  query?: never;
15262
- header?: never;
15591
+ header?: {
15592
+ /**
15593
+ * @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.
15594
+ * @example rfc3339
15595
+ */
15596
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15597
+ };
15263
15598
  path: {
15264
15599
  /** @description DNS zone name (trailing dot optional) */
15265
15600
  zone_name: string;
@@ -15323,7 +15658,13 @@ export interface operations {
15323
15658
  patch_zone_records_v1_dns__zone_name__records_patch: {
15324
15659
  parameters: {
15325
15660
  query?: never;
15326
- header?: never;
15661
+ header?: {
15662
+ /**
15663
+ * @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.
15664
+ * @example rfc3339
15665
+ */
15666
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15667
+ };
15327
15668
  path: {
15328
15669
  /** @description DNS zone name (trailing dot optional) */
15329
15670
  zone_name: string;
@@ -15373,7 +15714,13 @@ export interface operations {
15373
15714
  update_zone_rrsets_v1_dns__zone_name__rrsets_put: {
15374
15715
  parameters: {
15375
15716
  query?: never;
15376
- header?: never;
15717
+ header?: {
15718
+ /**
15719
+ * @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.
15720
+ * @example rfc3339
15721
+ */
15722
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15723
+ };
15377
15724
  path: {
15378
15725
  /** @description DNS zone name (trailing dot optional) */
15379
15726
  zone_name: string;
@@ -15423,7 +15770,13 @@ export interface operations {
15423
15770
  patch_zone_rrsets_v1_dns__zone_name__rrsets_patch: {
15424
15771
  parameters: {
15425
15772
  query?: never;
15426
- header?: never;
15773
+ header?: {
15774
+ /**
15775
+ * @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.
15776
+ * @example rfc3339
15777
+ */
15778
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15779
+ };
15427
15780
  path: {
15428
15781
  /** @description DNS zone name (trailing dot optional) */
15429
15782
  zone_name: string;
@@ -15473,7 +15826,13 @@ export interface operations {
15473
15826
  update_zone_vanity_set_v1_dns__zone_name__vanity_set_patch: {
15474
15827
  parameters: {
15475
15828
  query?: never;
15476
- header?: never;
15829
+ header?: {
15830
+ /**
15831
+ * @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.
15832
+ * @example rfc3339
15833
+ */
15834
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15835
+ };
15477
15836
  path: {
15478
15837
  /** @description DNS zone name (trailing dot optional) */
15479
15838
  zone_name: string;
@@ -15531,7 +15890,13 @@ export interface operations {
15531
15890
  sort_by?: components["schemas"]["DomainForwardSortField"];
15532
15891
  sort_order?: components["schemas"]["SortOrder"];
15533
15892
  };
15534
- header?: never;
15893
+ header?: {
15894
+ /**
15895
+ * @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.
15896
+ * @example rfc3339
15897
+ */
15898
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15899
+ };
15535
15900
  path?: never;
15536
15901
  cookie?: never;
15537
15902
  };
@@ -15592,7 +15957,13 @@ export interface operations {
15592
15957
  create_domain_forward_v2_v1_domain_forwards_post: {
15593
15958
  parameters: {
15594
15959
  query?: never;
15595
- header?: never;
15960
+ header?: {
15961
+ /**
15962
+ * @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.
15963
+ * @example rfc3339
15964
+ */
15965
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15966
+ };
15596
15967
  path?: never;
15597
15968
  cookie?: never;
15598
15969
  };
@@ -15690,7 +16061,13 @@ export interface operations {
15690
16061
  patch_redirects_v1_domain_forwards_patch: {
15691
16062
  parameters: {
15692
16063
  query?: never;
15693
- header?: never;
16064
+ header?: {
16065
+ /**
16066
+ * @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.
16067
+ * @example rfc3339
16068
+ */
16069
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16070
+ };
15694
16071
  path?: never;
15695
16072
  cookie?: never;
15696
16073
  };
@@ -15778,7 +16155,13 @@ export interface operations {
15778
16155
  /** @description Exclude platform values: Unknown, Bot */
15779
16156
  exclude_bots?: boolean;
15780
16157
  };
15781
- header?: never;
16158
+ header?: {
16159
+ /**
16160
+ * @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.
16161
+ * @example rfc3339
16162
+ */
16163
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16164
+ };
15782
16165
  path?: never;
15783
16166
  cookie?: never;
15784
16167
  };
@@ -15876,7 +16259,13 @@ export interface operations {
15876
16259
  /** @description Exclude platform values: Unknown, Bot */
15877
16260
  exclude_bots?: boolean;
15878
16261
  };
15879
- header?: never;
16262
+ header?: {
16263
+ /**
16264
+ * @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.
16265
+ * @example rfc3339
16266
+ */
16267
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16268
+ };
15880
16269
  path?: never;
15881
16270
  cookie?: never;
15882
16271
  };
@@ -15974,7 +16363,13 @@ export interface operations {
15974
16363
  /** @description Exclude platform values: Unknown, Bot */
15975
16364
  exclude_bots?: boolean;
15976
16365
  };
15977
- header?: never;
16366
+ header?: {
16367
+ /**
16368
+ * @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.
16369
+ * @example rfc3339
16370
+ */
16371
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16372
+ };
15978
16373
  path?: never;
15979
16374
  cookie?: never;
15980
16375
  };
@@ -16072,7 +16467,13 @@ export interface operations {
16072
16467
  /** @description Exclude platform values: Unknown, Bot */
16073
16468
  exclude_bots?: boolean;
16074
16469
  };
16075
- header?: never;
16470
+ header?: {
16471
+ /**
16472
+ * @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.
16473
+ * @example rfc3339
16474
+ */
16475
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16476
+ };
16076
16477
  path?: never;
16077
16478
  cookie?: never;
16078
16479
  };
@@ -16170,7 +16571,13 @@ export interface operations {
16170
16571
  /** @description Exclude platform values: Unknown, Bot */
16171
16572
  exclude_bots?: boolean;
16172
16573
  };
16173
- header?: never;
16574
+ header?: {
16575
+ /**
16576
+ * @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.
16577
+ * @example rfc3339
16578
+ */
16579
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16580
+ };
16174
16581
  path?: never;
16175
16582
  cookie?: never;
16176
16583
  };
@@ -16268,7 +16675,13 @@ export interface operations {
16268
16675
  /** @description Exclude platform values: Unknown, Bot */
16269
16676
  exclude_bots?: boolean;
16270
16677
  };
16271
- header?: never;
16678
+ header?: {
16679
+ /**
16680
+ * @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.
16681
+ * @example rfc3339
16682
+ */
16683
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16684
+ };
16272
16685
  path?: never;
16273
16686
  cookie?: never;
16274
16687
  };
@@ -16366,7 +16779,13 @@ export interface operations {
16366
16779
  /** @description Exclude platform values: Unknown, Bot */
16367
16780
  exclude_bots?: boolean;
16368
16781
  };
16369
- header?: never;
16782
+ header?: {
16783
+ /**
16784
+ * @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.
16785
+ * @example rfc3339
16786
+ */
16787
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16788
+ };
16370
16789
  path?: never;
16371
16790
  cookie?: never;
16372
16791
  };
@@ -16464,7 +16883,13 @@ export interface operations {
16464
16883
  /** @description Exclude platform values: Unknown, Bot */
16465
16884
  exclude_bots?: boolean;
16466
16885
  };
16467
- header?: never;
16886
+ header?: {
16887
+ /**
16888
+ * @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.
16889
+ * @example rfc3339
16890
+ */
16891
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16892
+ };
16468
16893
  path?: never;
16469
16894
  cookie?: never;
16470
16895
  };
@@ -16564,7 +16989,13 @@ export interface operations {
16564
16989
  /** @description Exclude platform values: Unknown, Bot */
16565
16990
  exclude_bots?: boolean;
16566
16991
  };
16567
- header?: never;
16992
+ header?: {
16993
+ /**
16994
+ * @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.
16995
+ * @example rfc3339
16996
+ */
16997
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16998
+ };
16568
16999
  path?: never;
16569
17000
  cookie?: never;
16570
17001
  };
@@ -16653,7 +17084,13 @@ export interface operations {
16653
17084
  get_domain_forward_v1_domain_forwards__hostname__get: {
16654
17085
  parameters: {
16655
17086
  query?: never;
16656
- header?: never;
17087
+ header?: {
17088
+ /**
17089
+ * @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.
17090
+ * @example rfc3339
17091
+ */
17092
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17093
+ };
16657
17094
  path: {
16658
17095
  /** @description Hostname */
16659
17096
  hostname: string;
@@ -16733,7 +17170,13 @@ export interface operations {
16733
17170
  create_domain_forward_set_v1_domain_forwards__hostname__post: {
16734
17171
  parameters: {
16735
17172
  query?: never;
16736
- header?: never;
17173
+ header?: {
17174
+ /**
17175
+ * @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.
17176
+ * @example rfc3339
17177
+ */
17178
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17179
+ };
16737
17180
  path: {
16738
17181
  /** @description Hostname */
16739
17182
  hostname: string;
@@ -16833,7 +17276,13 @@ export interface operations {
16833
17276
  delete_domain_forward_v1_domain_forwards__hostname__delete: {
16834
17277
  parameters: {
16835
17278
  query?: never;
16836
- header?: never;
17279
+ header?: {
17280
+ /**
17281
+ * @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.
17282
+ * @example rfc3339
17283
+ */
17284
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17285
+ };
16837
17286
  path: {
16838
17287
  /** @description Hostname */
16839
17288
  hostname: string;
@@ -16911,7 +17360,13 @@ export interface operations {
16911
17360
  disable_domain_forward_v1_domain_forwards__hostname__disable_patch: {
16912
17361
  parameters: {
16913
17362
  query?: never;
16914
- header?: never;
17363
+ header?: {
17364
+ /**
17365
+ * @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.
17366
+ * @example rfc3339
17367
+ */
17368
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17369
+ };
16915
17370
  path: {
16916
17371
  /** @description Hostname */
16917
17372
  hostname: string;
@@ -16973,7 +17428,13 @@ export interface operations {
16973
17428
  enable_domain_forward_v1_domain_forwards__hostname__enable_patch: {
16974
17429
  parameters: {
16975
17430
  query?: never;
16976
- header?: never;
17431
+ header?: {
17432
+ /**
17433
+ * @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.
17434
+ * @example rfc3339
17435
+ */
17436
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17437
+ };
16977
17438
  path: {
16978
17439
  /** @description Hostname */
16979
17440
  hostname: string;
@@ -17035,7 +17496,13 @@ export interface operations {
17035
17496
  get_domain_forward_set_v1_domain_forwards__hostname___protocol__get: {
17036
17497
  parameters: {
17037
17498
  query?: never;
17038
- header?: never;
17499
+ header?: {
17500
+ /**
17501
+ * @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.
17502
+ * @example rfc3339
17503
+ */
17504
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17505
+ };
17039
17506
  path: {
17040
17507
  protocol: components["schemas"]["HttpProtocol"];
17041
17508
  /** @description Hostname */
@@ -17116,7 +17583,13 @@ export interface operations {
17116
17583
  update_domain_forward_set_v1_domain_forwards__hostname___protocol__put: {
17117
17584
  parameters: {
17118
17585
  query?: never;
17119
- header?: never;
17586
+ header?: {
17587
+ /**
17588
+ * @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.
17589
+ * @example rfc3339
17590
+ */
17591
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17592
+ };
17120
17593
  path: {
17121
17594
  protocol: components["schemas"]["HttpProtocol"];
17122
17595
  /** @description Hostname */
@@ -17201,7 +17674,13 @@ export interface operations {
17201
17674
  delete_domain_forward_set_v1_domain_forwards__hostname___protocol__delete: {
17202
17675
  parameters: {
17203
17676
  query?: never;
17204
- header?: never;
17677
+ header?: {
17678
+ /**
17679
+ * @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.
17680
+ * @example rfc3339
17681
+ */
17682
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17683
+ };
17205
17684
  path: {
17206
17685
  protocol: components["schemas"]["HttpProtocol"];
17207
17686
  /** @description Hostname */
@@ -17289,7 +17768,13 @@ export interface operations {
17289
17768
  /** @description Whether to include premium domains in the suggestions */
17290
17769
  premium?: boolean | null;
17291
17770
  };
17292
- header?: never;
17771
+ header?: {
17772
+ /**
17773
+ * @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.
17774
+ * @example rfc3339
17775
+ */
17776
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17777
+ };
17293
17778
  path?: never;
17294
17779
  cookie?: never;
17295
17780
  };
@@ -17383,7 +17868,13 @@ export interface operations {
17383
17868
  /** @description Include additional data in the response. Can be specified multiple times. */
17384
17869
  include?: components["schemas"]["DomainIncludeField"][] | null;
17385
17870
  };
17386
- header?: never;
17871
+ header?: {
17872
+ /**
17873
+ * @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.
17874
+ * @example rfc3339
17875
+ */
17876
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17877
+ };
17387
17878
  path?: never;
17388
17879
  cookie?: never;
17389
17880
  };
@@ -17412,7 +17903,13 @@ export interface operations {
17412
17903
  create_domain_v1_domains_post: {
17413
17904
  parameters: {
17414
17905
  query?: never;
17415
- header?: never;
17906
+ header?: {
17907
+ /**
17908
+ * @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.
17909
+ * @example rfc3339
17910
+ */
17911
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17912
+ };
17416
17913
  path?: never;
17417
17914
  cookie?: never;
17418
17915
  };
@@ -17505,7 +18002,13 @@ export interface operations {
17505
18002
  * */
17506
18003
  domains: string[];
17507
18004
  };
17508
- header?: never;
18005
+ header?: {
18006
+ /**
18007
+ * @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.
18008
+ * @example rfc3339
18009
+ */
18010
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18011
+ };
17509
18012
  path?: never;
17510
18013
  cookie?: never;
17511
18014
  };
@@ -17534,7 +18037,13 @@ export interface operations {
17534
18037
  get_claims_notices_v1_domains_claims_notices_post: {
17535
18038
  parameters: {
17536
18039
  query?: never;
17537
- header?: never;
18040
+ header?: {
18041
+ /**
18042
+ * @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.
18043
+ * @example rfc3339
18044
+ */
18045
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18046
+ };
17538
18047
  path?: never;
17539
18048
  cookie?: never;
17540
18049
  };
@@ -17599,7 +18108,13 @@ export interface operations {
17599
18108
  get_domain_summary_v1_domains_summary_get: {
17600
18109
  parameters: {
17601
18110
  query?: never;
17602
- header?: never;
18111
+ header?: {
18112
+ /**
18113
+ * @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.
18114
+ * @example rfc3339
18115
+ */
18116
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18117
+ };
17603
18118
  path?: never;
17604
18119
  cookie?: never;
17605
18120
  };
@@ -17628,7 +18143,13 @@ export interface operations {
17628
18143
  withdraw_domain_v1_domains_tld_specific_at__domain_reference__withdraw_post: {
17629
18144
  parameters: {
17630
18145
  query?: never;
17631
- header?: never;
18146
+ header?: {
18147
+ /**
18148
+ * @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.
18149
+ * @example rfc3339
18150
+ */
18151
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18152
+ };
17632
18153
  path: {
17633
18154
  domain_reference: TypeId<"domain"> | string;
17634
18155
  };
@@ -17680,7 +18201,13 @@ export interface operations {
17680
18201
  request_auth_code_v1_domains_tld_specific_be__domain_reference__auth_code_request_post: {
17681
18202
  parameters: {
17682
18203
  query?: never;
17683
- header?: never;
18204
+ header?: {
18205
+ /**
18206
+ * @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.
18207
+ * @example rfc3339
18208
+ */
18209
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18210
+ };
17684
18211
  path: {
17685
18212
  domain_reference: TypeId<"domain"> | string;
17686
18213
  };
@@ -17746,7 +18273,13 @@ export interface operations {
17746
18273
  transit_domain_v1_domains_tld_specific_de__domain_reference__transit_post: {
17747
18274
  parameters: {
17748
18275
  query?: never;
17749
- header?: never;
18276
+ header?: {
18277
+ /**
18278
+ * @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.
18279
+ * @example rfc3339
18280
+ */
18281
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18282
+ };
17750
18283
  path: {
17751
18284
  domain_reference: TypeId<"domain"> | string;
17752
18285
  };
@@ -17798,7 +18331,13 @@ export interface operations {
17798
18331
  request_auth_code_v1_domains_tld_specific_eu__domain_reference__auth_code_request_post: {
17799
18332
  parameters: {
17800
18333
  query?: never;
17801
- header?: never;
18334
+ header?: {
18335
+ /**
18336
+ * @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.
18337
+ * @example rfc3339
18338
+ */
18339
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18340
+ };
17802
18341
  path: {
17803
18342
  domain_reference: TypeId<"domain"> | string;
17804
18343
  };
@@ -17864,7 +18403,13 @@ export interface operations {
17864
18403
  request_auth_code_v1_domains_tld_specific_lt__domain_reference__auth_code_request_post: {
17865
18404
  parameters: {
17866
18405
  query?: never;
17867
- header?: never;
18406
+ header?: {
18407
+ /**
18408
+ * @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.
18409
+ * @example rfc3339
18410
+ */
18411
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18412
+ };
17868
18413
  path: {
17869
18414
  domain_reference: TypeId<"domain"> | string;
17870
18415
  };
@@ -17930,7 +18475,13 @@ export interface operations {
17930
18475
  transfer_domain_v1_domains_transfer_post: {
17931
18476
  parameters: {
17932
18477
  query?: never;
17933
- header?: never;
18478
+ header?: {
18479
+ /**
18480
+ * @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.
18481
+ * @example rfc3339
18482
+ */
18483
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18484
+ };
17934
18485
  path?: never;
17935
18486
  cookie?: never;
17936
18487
  };
@@ -18026,7 +18577,13 @@ export interface operations {
18026
18577
  /** @description Include additional data in the response. */
18027
18578
  include?: components["schemas"]["DomainIncludeField"][] | null;
18028
18579
  };
18029
- header?: never;
18580
+ header?: {
18581
+ /**
18582
+ * @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.
18583
+ * @example rfc3339
18584
+ */
18585
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18586
+ };
18030
18587
  path: {
18031
18588
  domain_reference: TypeId<"domain"> | string;
18032
18589
  };
@@ -18074,7 +18631,13 @@ export interface operations {
18074
18631
  delete_domain_v1_domains__domain_reference__delete: {
18075
18632
  parameters: {
18076
18633
  query?: never;
18077
- header?: never;
18634
+ header?: {
18635
+ /**
18636
+ * @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.
18637
+ * @example rfc3339
18638
+ */
18639
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18640
+ };
18078
18641
  path: {
18079
18642
  domain_reference: TypeId<"domain"> | string;
18080
18643
  };
@@ -18138,7 +18701,13 @@ export interface operations {
18138
18701
  update_domain_v1_domains__domain_reference__patch: {
18139
18702
  parameters: {
18140
18703
  query?: never;
18141
- header?: never;
18704
+ header?: {
18705
+ /**
18706
+ * @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.
18707
+ * @example rfc3339
18708
+ */
18709
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18710
+ };
18142
18711
  path: {
18143
18712
  domain_reference: TypeId<"domain"> | string;
18144
18713
  };
@@ -18182,7 +18751,13 @@ export interface operations {
18182
18751
  get_dnssec_v1_domains__domain_reference__dnssec_get: {
18183
18752
  parameters: {
18184
18753
  query?: never;
18185
- header?: never;
18754
+ header?: {
18755
+ /**
18756
+ * @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.
18757
+ * @example rfc3339
18758
+ */
18759
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18760
+ };
18186
18761
  path: {
18187
18762
  domain_reference: TypeId<"domain"> | string;
18188
18763
  };
@@ -18230,7 +18805,13 @@ export interface operations {
18230
18805
  create_or_update_dnssec_v1_domains__domain_reference__dnssec_put: {
18231
18806
  parameters: {
18232
18807
  query?: never;
18233
- header?: never;
18808
+ header?: {
18809
+ /**
18810
+ * @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.
18811
+ * @example rfc3339
18812
+ */
18813
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18814
+ };
18234
18815
  path: {
18235
18816
  domain_reference: TypeId<"domain"> | string;
18236
18817
  };
@@ -18289,7 +18870,13 @@ export interface operations {
18289
18870
  delete_dnssec_v1_domains__domain_reference__dnssec_delete: {
18290
18871
  parameters: {
18291
18872
  query?: never;
18292
- header?: never;
18873
+ header?: {
18874
+ /**
18875
+ * @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.
18876
+ * @example rfc3339
18877
+ */
18878
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18879
+ };
18293
18880
  path: {
18294
18881
  domain_reference: TypeId<"domain"> | string;
18295
18882
  };
@@ -18335,7 +18922,13 @@ export interface operations {
18335
18922
  disable_and_unpublish_dnssec_records_v1_domains__domain_reference__dnssec_disable_post: {
18336
18923
  parameters: {
18337
18924
  query?: never;
18338
- header?: never;
18925
+ header?: {
18926
+ /**
18927
+ * @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.
18928
+ * @example rfc3339
18929
+ */
18930
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18931
+ };
18339
18932
  path: {
18340
18933
  domain_reference: TypeId<"domain"> | string;
18341
18934
  };
@@ -18381,7 +18974,13 @@ export interface operations {
18381
18974
  enable_and_publish_dnssec_records_v1_domains__domain_reference__dnssec_enable_post: {
18382
18975
  parameters: {
18383
18976
  query?: never;
18384
- header?: never;
18977
+ header?: {
18978
+ /**
18979
+ * @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.
18980
+ * @example rfc3339
18981
+ */
18982
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18983
+ };
18385
18984
  path: {
18386
18985
  domain_reference: TypeId<"domain"> | string;
18387
18986
  };
@@ -18429,7 +19028,13 @@ export interface operations {
18429
19028
  renew_domain_v1_domains__domain_reference__renew_post: {
18430
19029
  parameters: {
18431
19030
  query?: never;
18432
- header?: never;
19031
+ header?: {
19032
+ /**
19033
+ * @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.
19034
+ * @example rfc3339
19035
+ */
19036
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19037
+ };
18433
19038
  path: {
18434
19039
  domain_reference: TypeId<"domain"> | string;
18435
19040
  };
@@ -18464,7 +19069,13 @@ export interface operations {
18464
19069
  restore_domain_v1_domains__domain_reference__restore_post: {
18465
19070
  parameters: {
18466
19071
  query?: never;
18467
- header?: never;
19072
+ header?: {
19073
+ /**
19074
+ * @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.
19075
+ * @example rfc3339
19076
+ */
19077
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19078
+ };
18468
19079
  path: {
18469
19080
  domain_reference: TypeId<"domain"> | string;
18470
19081
  };
@@ -18499,7 +19110,13 @@ export interface operations {
18499
19110
  cancel_domain_transfer_v1_domains__domain_reference__transfer_delete: {
18500
19111
  parameters: {
18501
19112
  query?: never;
18502
- header?: never;
19113
+ header?: {
19114
+ /**
19115
+ * @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.
19116
+ * @example rfc3339
19117
+ */
19118
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19119
+ };
18503
19120
  path: {
18504
19121
  domain_reference: TypeId<"domain"> | string;
18505
19122
  };
@@ -18570,7 +19187,13 @@ export interface operations {
18570
19187
  sort_by?: components["schemas"]["EmailForwardSortField"];
18571
19188
  sort_order?: components["schemas"]["SortOrder"];
18572
19189
  };
18573
- header?: never;
19190
+ header?: {
19191
+ /**
19192
+ * @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.
19193
+ * @example rfc3339
19194
+ */
19195
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19196
+ };
18574
19197
  path?: never;
18575
19198
  cookie?: never;
18576
19199
  };
@@ -18631,7 +19254,13 @@ export interface operations {
18631
19254
  create_email_forward_v1_email_forwards_post: {
18632
19255
  parameters: {
18633
19256
  query?: never;
18634
- header?: never;
19257
+ header?: {
19258
+ /**
19259
+ * @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.
19260
+ * @example rfc3339
19261
+ */
19262
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19263
+ };
18635
19264
  path?: never;
18636
19265
  cookie?: never;
18637
19266
  };
@@ -18729,7 +19358,13 @@ export interface operations {
18729
19358
  get_email_forward_v1_email_forwards__email_forward_id__get: {
18730
19359
  parameters: {
18731
19360
  query?: never;
18732
- header?: never;
19361
+ header?: {
19362
+ /**
19363
+ * @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.
19364
+ * @example rfc3339
19365
+ */
19366
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19367
+ };
18733
19368
  path: {
18734
19369
  email_forward_id: TypeId<"email_forward">;
18735
19370
  };
@@ -18808,7 +19443,13 @@ export interface operations {
18808
19443
  delete_email_forward_v1_email_forwards__email_forward_id__delete: {
18809
19444
  parameters: {
18810
19445
  query?: never;
18811
- header?: never;
19446
+ header?: {
19447
+ /**
19448
+ * @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.
19449
+ * @example rfc3339
19450
+ */
19451
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19452
+ };
18812
19453
  path: {
18813
19454
  email_forward_id: TypeId<"email_forward">;
18814
19455
  };
@@ -18869,7 +19510,13 @@ export interface operations {
18869
19510
  create_email_forward_alias_v1_email_forwards__email_forward_id__aliases_post: {
18870
19511
  parameters: {
18871
19512
  query?: never;
18872
- header?: never;
19513
+ header?: {
19514
+ /**
19515
+ * @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.
19516
+ * @example rfc3339
19517
+ */
19518
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19519
+ };
18873
19520
  path: {
18874
19521
  email_forward_id: TypeId<"email_forward">;
18875
19522
  };
@@ -18968,7 +19615,13 @@ export interface operations {
18968
19615
  update_email_forward_alias_v1_email_forwards__email_forward_id__aliases__alias_id__put: {
18969
19616
  parameters: {
18970
19617
  query?: never;
18971
- header?: never;
19618
+ header?: {
19619
+ /**
19620
+ * @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.
19621
+ * @example rfc3339
19622
+ */
19623
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19624
+ };
18972
19625
  path: {
18973
19626
  email_forward_id: TypeId<"email_forward">;
18974
19627
  alias_id: TypeId<"email_forward_alias">;
@@ -19053,7 +19706,13 @@ export interface operations {
19053
19706
  delete_email_forward_alias_v1_email_forwards__email_forward_id__aliases__alias_id__delete: {
19054
19707
  parameters: {
19055
19708
  query?: never;
19056
- header?: never;
19709
+ header?: {
19710
+ /**
19711
+ * @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.
19712
+ * @example rfc3339
19713
+ */
19714
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19715
+ };
19057
19716
  path: {
19058
19717
  email_forward_id: TypeId<"email_forward">;
19059
19718
  alias_id: TypeId<"email_forward_alias">;
@@ -19132,7 +19791,13 @@ export interface operations {
19132
19791
  disable_email_forward_v1_email_forwards__email_forward_id__disable_patch: {
19133
19792
  parameters: {
19134
19793
  query?: never;
19135
- header?: never;
19794
+ header?: {
19795
+ /**
19796
+ * @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.
19797
+ * @example rfc3339
19798
+ */
19799
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19800
+ };
19136
19801
  path: {
19137
19802
  email_forward_id: TypeId<"email_forward">;
19138
19803
  };
@@ -19209,7 +19874,13 @@ export interface operations {
19209
19874
  enable_email_forward_v1_email_forwards__email_forward_id__enable_patch: {
19210
19875
  parameters: {
19211
19876
  query?: never;
19212
- header?: never;
19877
+ header?: {
19878
+ /**
19879
+ * @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.
19880
+ * @example rfc3339
19881
+ */
19882
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19883
+ };
19213
19884
  path: {
19214
19885
  email_forward_id: TypeId<"email_forward">;
19215
19886
  };
@@ -19289,7 +19960,13 @@ export interface operations {
19289
19960
  start_time?: Date | null;
19290
19961
  end_time?: Date | null;
19291
19962
  };
19292
- header?: never;
19963
+ header?: {
19964
+ /**
19965
+ * @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.
19966
+ * @example rfc3339
19967
+ */
19968
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19969
+ };
19293
19970
  path: {
19294
19971
  email_forward_id: TypeId<"email_forward">;
19295
19972
  };
@@ -19378,7 +20055,13 @@ export interface operations {
19378
20055
  subtype?: components["schemas"]["EventSubtype"] | null;
19379
20056
  acknowledged?: boolean | null;
19380
20057
  };
19381
- header?: never;
20058
+ header?: {
20059
+ /**
20060
+ * @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.
20061
+ * @example rfc3339
20062
+ */
20063
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20064
+ };
19382
20065
  path?: never;
19383
20066
  cookie?: never;
19384
20067
  };
@@ -19423,7 +20106,13 @@ export interface operations {
19423
20106
  get_event_v1_events__event_id__get: {
19424
20107
  parameters: {
19425
20108
  query?: never;
19426
- header?: never;
20109
+ header?: {
20110
+ /**
20111
+ * @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.
20112
+ * @example rfc3339
20113
+ */
20114
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20115
+ };
19427
20116
  path: {
19428
20117
  event_id: TypeId<"event">;
19429
20118
  };
@@ -19487,7 +20176,13 @@ export interface operations {
19487
20176
  acknowledge_event_v1_events__event_id__patch: {
19488
20177
  parameters: {
19489
20178
  query?: never;
19490
- header?: never;
20179
+ header?: {
20180
+ /**
20181
+ * @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.
20182
+ * @example rfc3339
20183
+ */
20184
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20185
+ };
19491
20186
  path: {
19492
20187
  event_id: TypeId<"event">;
19493
20188
  };
@@ -19549,7 +20244,13 @@ export interface operations {
19549
20244
  create_host_v1_hosts_post: {
19550
20245
  parameters: {
19551
20246
  query?: never;
19552
- header?: never;
20247
+ header?: {
20248
+ /**
20249
+ * @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.
20250
+ * @example rfc3339
20251
+ */
20252
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20253
+ };
19553
20254
  path?: never;
19554
20255
  cookie?: never;
19555
20256
  };
@@ -19657,7 +20358,13 @@ export interface operations {
19657
20358
  get_host_v1_hosts__host_reference__get: {
19658
20359
  parameters: {
19659
20360
  query?: never;
19660
- header?: never;
20361
+ header?: {
20362
+ /**
20363
+ * @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.
20364
+ * @example rfc3339
20365
+ */
20366
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20367
+ };
19661
20368
  path: {
19662
20369
  host_reference: TypeId<"host"> | string;
19663
20370
  };
@@ -19729,7 +20436,13 @@ export interface operations {
19729
20436
  update_host_v1_hosts__host_reference__put: {
19730
20437
  parameters: {
19731
20438
  query?: never;
19732
- header?: never;
20439
+ header?: {
20440
+ /**
20441
+ * @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.
20442
+ * @example rfc3339
20443
+ */
20444
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20445
+ };
19733
20446
  path: {
19734
20447
  host_reference: TypeId<"host"> | string;
19735
20448
  };
@@ -19805,7 +20518,13 @@ export interface operations {
19805
20518
  delete_host_v1_hosts__host_reference__delete: {
19806
20519
  parameters: {
19807
20520
  query?: never;
19808
- header?: never;
20521
+ header?: {
20522
+ /**
20523
+ * @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.
20524
+ * @example rfc3339
20525
+ */
20526
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20527
+ };
19809
20528
  path: {
19810
20529
  host_reference: TypeId<"host"> | string;
19811
20530
  };
@@ -19892,7 +20611,13 @@ export interface operations {
19892
20611
  get_job_v1_job__job_id__get: {
19893
20612
  parameters: {
19894
20613
  query?: never;
19895
- header?: never;
20614
+ header?: {
20615
+ /**
20616
+ * @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.
20617
+ * @example rfc3339
20618
+ */
20619
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20620
+ };
19896
20621
  path: {
19897
20622
  /** @description Job ID */
19898
20623
  job_id: TypeId<"job">;
@@ -19941,7 +20666,13 @@ export interface operations {
19941
20666
  delete_job_v1_job__job_id__delete: {
19942
20667
  parameters: {
19943
20668
  query?: never;
19944
- header?: never;
20669
+ header?: {
20670
+ /**
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.
20672
+ * @example rfc3339
20673
+ */
20674
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20675
+ };
19945
20676
  path: {
19946
20677
  /** @description Job ID */
19947
20678
  job_id: TypeId<"job">;
@@ -19988,7 +20719,13 @@ export interface operations {
19988
20719
  pause_job_v1_job__job_id__pause_post: {
19989
20720
  parameters: {
19990
20721
  query?: never;
19991
- header?: never;
20722
+ header?: {
20723
+ /**
20724
+ * @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.
20725
+ * @example rfc3339
20726
+ */
20727
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20728
+ };
19992
20729
  path: {
19993
20730
  /** @description Job ID */
19994
20731
  job_id: TypeId<"job">;
@@ -20035,7 +20772,13 @@ export interface operations {
20035
20772
  resume_job_v1_job__job_id__resume_post: {
20036
20773
  parameters: {
20037
20774
  query?: never;
20038
- header?: never;
20775
+ header?: {
20776
+ /**
20777
+ * @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.
20778
+ * @example rfc3339
20779
+ */
20780
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20781
+ };
20039
20782
  path: {
20040
20783
  /** @description Job ID */
20041
20784
  job_id: TypeId<"job">;
@@ -20084,7 +20827,13 @@ export interface operations {
20084
20827
  retry_job_v1_job__job_id__retry_post: {
20085
20828
  parameters: {
20086
20829
  query?: never;
20087
- header?: never;
20830
+ header?: {
20831
+ /**
20832
+ * @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.
20833
+ * @example rfc3339
20834
+ */
20835
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20836
+ };
20088
20837
  path: {
20089
20838
  /** @description Job ID */
20090
20839
  job_id: TypeId<"job">;
@@ -20160,7 +20909,13 @@ export interface operations {
20160
20909
  /** @description Number of batches per page */
20161
20910
  page_size?: number;
20162
20911
  };
20163
- header?: never;
20912
+ header?: {
20913
+ /**
20914
+ * @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.
20915
+ * @example rfc3339
20916
+ */
20917
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20918
+ };
20164
20919
  path?: never;
20165
20920
  cookie?: never;
20166
20921
  };
@@ -20189,7 +20944,13 @@ export interface operations {
20189
20944
  create_batch_v1_jobs_post: {
20190
20945
  parameters: {
20191
20946
  query?: never;
20192
- header?: never;
20947
+ header?: {
20948
+ /**
20949
+ * @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.
20950
+ * @example rfc3339
20951
+ */
20952
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20953
+ };
20193
20954
  path?: never;
20194
20955
  cookie?: never;
20195
20956
  };
@@ -20255,7 +21016,13 @@ export interface operations {
20255
21016
  get_batch_v1_jobs__batch_id__get: {
20256
21017
  parameters: {
20257
21018
  query?: never;
20258
- header?: never;
21019
+ header?: {
21020
+ /**
21021
+ * @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.
21022
+ * @example rfc3339
21023
+ */
21024
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21025
+ };
20259
21026
  path: {
20260
21027
  /** @description Batch ID */
20261
21028
  batch_id: TypeId<"batch">;
@@ -20321,7 +21088,13 @@ export interface operations {
20321
21088
  delete_batch_v1_jobs__batch_id__delete: {
20322
21089
  parameters: {
20323
21090
  query?: never;
20324
- header?: never;
21091
+ header?: {
21092
+ /**
21093
+ * @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.
21094
+ * @example rfc3339
21095
+ */
21096
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21097
+ };
20325
21098
  path: {
20326
21099
  /** @description Batch ID */
20327
21100
  batch_id: TypeId<"batch">;
@@ -20379,7 +21152,13 @@ export interface operations {
20379
21152
  /** @description Number of jobs per page */
20380
21153
  page_size?: number;
20381
21154
  };
20382
- header?: never;
21155
+ header?: {
21156
+ /**
21157
+ * @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.
21158
+ * @example rfc3339
21159
+ */
21160
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21161
+ };
20383
21162
  path: {
20384
21163
  /** @description Batch ID */
20385
21164
  batch_id: TypeId<"batch">;
@@ -20445,7 +21224,13 @@ export interface operations {
20445
21224
  pause_batch_v1_jobs__batch_id__pause_post: {
20446
21225
  parameters: {
20447
21226
  query?: never;
20448
- header?: never;
21227
+ header?: {
21228
+ /**
21229
+ * @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.
21230
+ * @example rfc3339
21231
+ */
21232
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21233
+ };
20449
21234
  path: {
20450
21235
  /** @description Batch ID */
20451
21236
  batch_id: TypeId<"batch">;
@@ -20492,7 +21277,13 @@ export interface operations {
20492
21277
  resume_batch_v1_jobs__batch_id__resume_post: {
20493
21278
  parameters: {
20494
21279
  query?: never;
20495
- header?: never;
21280
+ header?: {
21281
+ /**
21282
+ * @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.
21283
+ * @example rfc3339
21284
+ */
21285
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21286
+ };
20496
21287
  path: {
20497
21288
  /** @description Batch ID */
20498
21289
  batch_id: TypeId<"batch">;
@@ -20542,7 +21333,13 @@ export interface operations {
20542
21333
  /** @description Optional repeatable filter: only retry jobs whose error_class matches one of these values. Example: `?error_class=BillingInsufficientFundsError` to retry only insufficient-funds failures. Omit to retry all failed/dead-lettered jobs in the batch. */
20543
21334
  error_class?: string[] | null;
20544
21335
  };
20545
- header?: never;
21336
+ header?: {
21337
+ /**
21338
+ * @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.
21339
+ * @example rfc3339
21340
+ */
21341
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21342
+ };
20546
21343
  path: {
20547
21344
  /** @description Batch ID */
20548
21345
  batch_id: TypeId<"batch">;
@@ -20598,7 +21395,13 @@ export interface operations {
20598
21395
  search?: string | null;
20599
21396
  country_code?: string | null;
20600
21397
  };
20601
- header?: never;
21398
+ header?: {
21399
+ /**
21400
+ * @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.
21401
+ * @example rfc3339
21402
+ */
21403
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21404
+ };
20602
21405
  path?: never;
20603
21406
  cookie?: never;
20604
21407
  };
@@ -20659,7 +21462,13 @@ export interface operations {
20659
21462
  create_organization_v1_organizations_post: {
20660
21463
  parameters: {
20661
21464
  query?: never;
20662
- header?: never;
21465
+ header?: {
21466
+ /**
21467
+ * @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.
21468
+ * @example rfc3339
21469
+ */
21470
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21471
+ };
20663
21472
  path?: never;
20664
21473
  cookie?: never;
20665
21474
  };
@@ -20734,7 +21543,13 @@ export interface operations {
20734
21543
  /** @description Optional list of attribute keys to filter */
20735
21544
  keys?: string[] | null;
20736
21545
  };
20737
- header?: never;
21546
+ header?: {
21547
+ /**
21548
+ * @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.
21549
+ * @example rfc3339
21550
+ */
21551
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21552
+ };
20738
21553
  path?: never;
20739
21554
  cookie?: never;
20740
21555
  };
@@ -20795,7 +21610,13 @@ export interface operations {
20795
21610
  update_current_organization_attributes_v1_organizations_attributes_patch: {
20796
21611
  parameters: {
20797
21612
  query?: never;
20798
- header?: never;
21613
+ header?: {
21614
+ /**
21615
+ * @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.
21616
+ * @example rfc3339
21617
+ */
21618
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21619
+ };
20799
21620
  path?: never;
20800
21621
  cookie?: never;
20801
21622
  };
@@ -20860,7 +21681,13 @@ export interface operations {
20860
21681
  list_ip_restrictions_v1_organizations_ip_restrictions_get: {
20861
21682
  parameters: {
20862
21683
  query?: never;
20863
- header?: never;
21684
+ header?: {
21685
+ /**
21686
+ * @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.
21687
+ * @example rfc3339
21688
+ */
21689
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21690
+ };
20864
21691
  path?: never;
20865
21692
  cookie?: never;
20866
21693
  };
@@ -20921,7 +21748,13 @@ export interface operations {
20921
21748
  create_ip_restriction_v1_organizations_ip_restrictions_post: {
20922
21749
  parameters: {
20923
21750
  query?: never;
20924
- header?: never;
21751
+ header?: {
21752
+ /**
21753
+ * @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.
21754
+ * @example rfc3339
21755
+ */
21756
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21757
+ };
20925
21758
  path?: never;
20926
21759
  cookie?: never;
20927
21760
  };
@@ -20986,7 +21819,13 @@ export interface operations {
20986
21819
  get_ip_restriction_v1_organizations_ip_restrictions__ip_restriction_id__get: {
20987
21820
  parameters: {
20988
21821
  query?: never;
20989
- header?: never;
21822
+ header?: {
21823
+ /**
21824
+ * @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.
21825
+ * @example rfc3339
21826
+ */
21827
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21828
+ };
20990
21829
  path: {
20991
21830
  ip_restriction_id: number;
20992
21831
  };
@@ -21049,7 +21888,13 @@ export interface operations {
21049
21888
  delete_ip_restriction_v1_organizations_ip_restrictions__ip_restriction_id__delete: {
21050
21889
  parameters: {
21051
21890
  query?: never;
21052
- header?: never;
21891
+ header?: {
21892
+ /**
21893
+ * @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.
21894
+ * @example rfc3339
21895
+ */
21896
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21897
+ };
21053
21898
  path: {
21054
21899
  ip_restriction_id: number;
21055
21900
  };
@@ -21110,7 +21955,13 @@ export interface operations {
21110
21955
  update_ip_restriction_v1_organizations_ip_restrictions__ip_restriction_id__patch: {
21111
21956
  parameters: {
21112
21957
  query?: never;
21113
- header?: never;
21958
+ header?: {
21959
+ /**
21960
+ * @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.
21961
+ * @example rfc3339
21962
+ */
21963
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21964
+ };
21114
21965
  path: {
21115
21966
  ip_restriction_id: number;
21116
21967
  };
@@ -21177,7 +22028,13 @@ export interface operations {
21177
22028
  list_role_permissions_v1_organizations_role_permissions_get: {
21178
22029
  parameters: {
21179
22030
  query?: never;
21180
- header?: never;
22031
+ header?: {
22032
+ /**
22033
+ * @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.
22034
+ * @example rfc3339
22035
+ */
22036
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22037
+ };
21181
22038
  path?: never;
21182
22039
  cookie?: never;
21183
22040
  };
@@ -21238,7 +22095,13 @@ export interface operations {
21238
22095
  list_roles_v1_organizations_roles_get: {
21239
22096
  parameters: {
21240
22097
  query?: never;
21241
- header?: never;
22098
+ header?: {
22099
+ /**
22100
+ * @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.
22101
+ * @example rfc3339
22102
+ */
22103
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22104
+ };
21242
22105
  path?: never;
21243
22106
  cookie?: never;
21244
22107
  };
@@ -21299,7 +22162,13 @@ export interface operations {
21299
22162
  create_role_v1_organizations_roles_post: {
21300
22163
  parameters: {
21301
22164
  query?: never;
21302
- header?: never;
22165
+ header?: {
22166
+ /**
22167
+ * @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.
22168
+ * @example rfc3339
22169
+ */
22170
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22171
+ };
21303
22172
  path?: never;
21304
22173
  cookie?: never;
21305
22174
  };
@@ -21380,7 +22249,13 @@ export interface operations {
21380
22249
  get_role_v1_organizations_roles__label__get: {
21381
22250
  parameters: {
21382
22251
  query?: never;
21383
- header?: never;
22252
+ header?: {
22253
+ /**
22254
+ * @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.
22255
+ * @example rfc3339
22256
+ */
22257
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22258
+ };
21384
22259
  path: {
21385
22260
  label: string;
21386
22261
  };
@@ -21460,7 +22335,13 @@ export interface operations {
21460
22335
  delete_role_v1_organizations_roles__label__delete: {
21461
22336
  parameters: {
21462
22337
  query?: never;
21463
- header?: never;
22338
+ header?: {
22339
+ /**
22340
+ * @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.
22341
+ * @example rfc3339
22342
+ */
22343
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22344
+ };
21464
22345
  path: {
21465
22346
  label: string;
21466
22347
  };
@@ -21556,7 +22437,13 @@ export interface operations {
21556
22437
  update_role_v1_organizations_roles__label__patch: {
21557
22438
  parameters: {
21558
22439
  query?: never;
21559
- header?: never;
22440
+ header?: {
22441
+ /**
22442
+ * @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.
22443
+ * @example rfc3339
22444
+ */
22445
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22446
+ };
21560
22447
  path: {
21561
22448
  label: string;
21562
22449
  };
@@ -21663,7 +22550,13 @@ export interface operations {
21663
22550
  sort_order?: components["schemas"]["SortOrder"];
21664
22551
  search?: string | null;
21665
22552
  };
21666
- header?: never;
22553
+ header?: {
22554
+ /**
22555
+ * @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.
22556
+ * @example rfc3339
22557
+ */
22558
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22559
+ };
21667
22560
  path?: never;
21668
22561
  cookie?: never;
21669
22562
  };
@@ -21724,7 +22617,13 @@ export interface operations {
21724
22617
  get_organization_v1_organizations__organization_id__get: {
21725
22618
  parameters: {
21726
22619
  query?: never;
21727
- header?: never;
22620
+ header?: {
22621
+ /**
22622
+ * @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.
22623
+ * @example rfc3339
22624
+ */
22625
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22626
+ };
21728
22627
  path: {
21729
22628
  organization_id: TypeId<"organization">;
21730
22629
  };
@@ -21787,7 +22686,13 @@ export interface operations {
21787
22686
  delete_organization_v1_organizations__organization_id__delete: {
21788
22687
  parameters: {
21789
22688
  query?: never;
21790
- header?: never;
22689
+ header?: {
22690
+ /**
22691
+ * @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.
22692
+ * @example rfc3339
22693
+ */
22694
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22695
+ };
21791
22696
  path: {
21792
22697
  organization_id: TypeId<"organization">;
21793
22698
  };
@@ -21848,7 +22753,13 @@ export interface operations {
21848
22753
  update_organization_v1_organizations__organization_id__patch: {
21849
22754
  parameters: {
21850
22755
  query?: never;
21851
- header?: never;
22756
+ header?: {
22757
+ /**
22758
+ * @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.
22759
+ * @example rfc3339
22760
+ */
22761
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22762
+ };
21852
22763
  path: {
21853
22764
  organization_id: TypeId<"organization">;
21854
22765
  };
@@ -21918,7 +22829,13 @@ export interface operations {
21918
22829
  /** @description Optional list of attribute keys to filter */
21919
22830
  keys?: string[] | null;
21920
22831
  };
21921
- header?: never;
22832
+ header?: {
22833
+ /**
22834
+ * @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.
22835
+ * @example rfc3339
22836
+ */
22837
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22838
+ };
21922
22839
  path: {
21923
22840
  organization_id: TypeId<"organization">;
21924
22841
  };
@@ -21981,7 +22898,13 @@ export interface operations {
21981
22898
  update_organization_attributes_v1_organizations__organization_id__attributes_patch: {
21982
22899
  parameters: {
21983
22900
  query?: never;
21984
- header?: never;
22901
+ header?: {
22902
+ /**
22903
+ * @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.
22904
+ * @example rfc3339
22905
+ */
22906
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22907
+ };
21985
22908
  path: {
21986
22909
  organization_id: TypeId<"organization">;
21987
22910
  };
@@ -22051,7 +22974,13 @@ export interface operations {
22051
22974
  page?: number;
22052
22975
  page_size?: number;
22053
22976
  };
22054
- header?: never;
22977
+ header?: {
22978
+ /**
22979
+ * @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.
22980
+ * @example rfc3339
22981
+ */
22982
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22983
+ };
22055
22984
  path: {
22056
22985
  organization_id: TypeId<"organization">;
22057
22986
  };
@@ -22085,7 +23014,13 @@ export interface operations {
22085
23014
  product_action?: components["schemas"]["BillingTransactionAction"] | null;
22086
23015
  product_class?: string | null;
22087
23016
  };
22088
- header?: never;
23017
+ header?: {
23018
+ /**
23019
+ * @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.
23020
+ * @example rfc3339
23021
+ */
23022
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23023
+ };
22089
23024
  path: {
22090
23025
  organization_id: TypeId<"organization">;
22091
23026
  product_type: components["schemas"]["BillingTransactionProductType"];
@@ -22162,7 +23097,13 @@ export interface operations {
22162
23097
  completed_after?: Date | null;
22163
23098
  completed_before?: Date | null;
22164
23099
  };
22165
- header?: never;
23100
+ header?: {
23101
+ /**
23102
+ * @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.
23103
+ * @example rfc3339
23104
+ */
23105
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23106
+ };
22166
23107
  path: {
22167
23108
  organization_id: TypeId<"organization">;
22168
23109
  };
@@ -22225,7 +23166,13 @@ export interface operations {
22225
23166
  get_transaction_v1_organizations__organization_id__transactions__transaction_id__get: {
22226
23167
  parameters: {
22227
23168
  query?: never;
22228
- header?: never;
23169
+ header?: {
23170
+ /**
23171
+ * @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.
23172
+ * @example rfc3339
23173
+ */
23174
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23175
+ };
22229
23176
  path: {
22230
23177
  organization_id: TypeId<"organization">;
22231
23178
  transaction_id: TypeId<"billing_transaction">;
@@ -22299,7 +23246,13 @@ export interface operations {
22299
23246
  enabled?: boolean | null;
22300
23247
  compliance_status?: components["schemas"]["ComplianceStatus"] | null;
22301
23248
  };
22302
- header?: never;
23249
+ header?: {
23250
+ /**
23251
+ * @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.
23252
+ * @example rfc3339
23253
+ */
23254
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23255
+ };
22303
23256
  path?: never;
22304
23257
  cookie?: never;
22305
23258
  };
@@ -22363,7 +23316,13 @@ export interface operations {
22363
23316
  start_time?: Date | null;
22364
23317
  end_time?: Date | null;
22365
23318
  };
22366
- header?: never;
23319
+ header?: {
23320
+ /**
23321
+ * @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.
23322
+ * @example rfc3339
23323
+ */
23324
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23325
+ };
22367
23326
  path?: never;
22368
23327
  cookie?: never;
22369
23328
  };
@@ -22424,7 +23383,13 @@ export interface operations {
22424
23383
  signup_for_parking_v1_parking_signup_post: {
22425
23384
  parameters: {
22426
23385
  query?: never;
22427
- header?: never;
23386
+ header?: {
23387
+ /**
23388
+ * @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.
23389
+ * @example rfc3339
23390
+ */
23391
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23392
+ };
22428
23393
  path?: never;
22429
23394
  cookie?: never;
22430
23395
  };
@@ -22489,7 +23454,13 @@ export interface operations {
22489
23454
  get_parking_signup_status_v1_parking_signup_status_get: {
22490
23455
  parameters: {
22491
23456
  query?: never;
22492
- header?: never;
23457
+ header?: {
23458
+ /**
23459
+ * @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.
23460
+ * @example rfc3339
23461
+ */
23462
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23463
+ };
22493
23464
  path?: never;
22494
23465
  cookie?: never;
22495
23466
  };
@@ -22553,7 +23524,13 @@ export interface operations {
22553
23524
  start_time?: Date | null;
22554
23525
  end_time?: Date | null;
22555
23526
  };
22556
- header?: never;
23527
+ header?: {
23528
+ /**
23529
+ * @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.
23530
+ * @example rfc3339
23531
+ */
23532
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23533
+ };
22557
23534
  path: {
22558
23535
  parking_reference: TypeId<"parking"> | string;
22559
23536
  };
@@ -22640,7 +23617,13 @@ export interface operations {
22640
23617
  created_after?: Date | null;
22641
23618
  created_before?: Date | null;
22642
23619
  };
22643
- header?: never;
23620
+ header?: {
23621
+ /**
23622
+ * @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.
23623
+ * @example rfc3339
23624
+ */
23625
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23626
+ };
22644
23627
  path?: never;
22645
23628
  cookie?: never;
22646
23629
  };
@@ -22669,7 +23652,13 @@ export interface operations {
22669
23652
  create_report_v1_reports_post: {
22670
23653
  parameters: {
22671
23654
  query?: never;
22672
- header?: never;
23655
+ header?: {
23656
+ /**
23657
+ * @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.
23658
+ * @example rfc3339
23659
+ */
23660
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23661
+ };
22673
23662
  path?: never;
22674
23663
  cookie?: never;
22675
23664
  };
@@ -22702,7 +23691,13 @@ export interface operations {
22702
23691
  get_report_v1_reports__report_id__get: {
22703
23692
  parameters: {
22704
23693
  query?: never;
22705
- header?: never;
23694
+ header?: {
23695
+ /**
23696
+ * @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.
23697
+ * @example rfc3339
23698
+ */
23699
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23700
+ };
22706
23701
  path: {
22707
23702
  report_id: string;
22708
23703
  };
@@ -22733,7 +23728,13 @@ export interface operations {
22733
23728
  download_report_v1_reports__report_id__download_get: {
22734
23729
  parameters: {
22735
23730
  query?: never;
22736
- header?: never;
23731
+ header?: {
23732
+ /**
23733
+ * @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.
23734
+ * @example rfc3339
23735
+ */
23736
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23737
+ };
22737
23738
  path: {
22738
23739
  report_id: string;
22739
23740
  };
@@ -22772,7 +23773,13 @@ export interface operations {
22772
23773
  tag_types?: components["schemas"]["TagType"][] | null;
22773
23774
  search?: string | null;
22774
23775
  };
22775
- header?: never;
23776
+ header?: {
23777
+ /**
23778
+ * @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.
23779
+ * @example rfc3339
23780
+ */
23781
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23782
+ };
22776
23783
  path?: never;
22777
23784
  cookie?: never;
22778
23785
  };
@@ -22817,7 +23824,13 @@ export interface operations {
22817
23824
  create_tag_v1_tags_post: {
22818
23825
  parameters: {
22819
23826
  query?: never;
22820
- header?: never;
23827
+ header?: {
23828
+ /**
23829
+ * @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.
23830
+ * @example rfc3339
23831
+ */
23832
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23833
+ };
22821
23834
  path?: never;
22822
23835
  cookie?: never;
22823
23836
  };
@@ -22883,7 +23896,13 @@ export interface operations {
22883
23896
  bulk_update_object_tags_v1_tags_objects_post: {
22884
23897
  parameters: {
22885
23898
  query?: never;
22886
- header?: never;
23899
+ header?: {
23900
+ /**
23901
+ * @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.
23902
+ * @example rfc3339
23903
+ */
23904
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23905
+ };
22887
23906
  path?: never;
22888
23907
  cookie?: never;
22889
23908
  };
@@ -22966,7 +23985,13 @@ export interface operations {
22966
23985
  get_tag_v1_tags__tag_id__get: {
22967
23986
  parameters: {
22968
23987
  query?: never;
22969
- header?: never;
23988
+ header?: {
23989
+ /**
23990
+ * @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.
23991
+ * @example rfc3339
23992
+ */
23993
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23994
+ };
22970
23995
  path: {
22971
23996
  tag_id: TypeId<"tag">;
22972
23997
  };
@@ -23030,7 +24055,13 @@ export interface operations {
23030
24055
  delete_tag_v1_tags__tag_id__delete: {
23031
24056
  parameters: {
23032
24057
  query?: never;
23033
- header?: never;
24058
+ header?: {
24059
+ /**
24060
+ * @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.
24061
+ * @example rfc3339
24062
+ */
24063
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24064
+ };
23034
24065
  path: {
23035
24066
  tag_id: TypeId<"tag">;
23036
24067
  };
@@ -23092,7 +24123,13 @@ export interface operations {
23092
24123
  update_tag_v1_tags__tag_id__patch: {
23093
24124
  parameters: {
23094
24125
  query?: never;
23095
- header?: never;
24126
+ header?: {
24127
+ /**
24128
+ * @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.
24129
+ * @example rfc3339
24130
+ */
24131
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24132
+ };
23096
24133
  path: {
23097
24134
  tag_id: TypeId<"tag">;
23098
24135
  };
@@ -23177,7 +24214,13 @@ export interface operations {
23177
24214
  update_tag_objects_v1_tags__tag_id__objects_post: {
23178
24215
  parameters: {
23179
24216
  query?: never;
23180
- header?: never;
24217
+ header?: {
24218
+ /**
24219
+ * @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.
24220
+ * @example rfc3339
24221
+ */
24222
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24223
+ };
23181
24224
  path: {
23182
24225
  tag_id: TypeId<"tag">;
23183
24226
  };
@@ -23248,7 +24291,13 @@ export interface operations {
23248
24291
  fields?: string | null;
23249
24292
  tlds?: string | null;
23250
24293
  };
23251
- header?: never;
24294
+ header?: {
24295
+ /**
24296
+ * @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.
24297
+ * @example rfc3339
24298
+ */
24299
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24300
+ };
23252
24301
  path?: never;
23253
24302
  cookie?: never;
23254
24303
  };
@@ -23281,7 +24330,13 @@ export interface operations {
23281
24330
  get_tld_portfolio_v1_tlds_portfolio_get: {
23282
24331
  parameters: {
23283
24332
  query?: never;
23284
- header?: never;
24333
+ header?: {
24334
+ /**
24335
+ * @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.
24336
+ * @example rfc3339
24337
+ */
24338
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24339
+ };
23285
24340
  path?: never;
23286
24341
  cookie?: never;
23287
24342
  };
@@ -23310,7 +24365,13 @@ export interface operations {
23310
24365
  get_tld_spec_v1_tlds__tld__get: {
23311
24366
  parameters: {
23312
24367
  query?: never;
23313
- header?: never;
24368
+ header?: {
24369
+ /**
24370
+ * @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.
24371
+ * @example rfc3339
24372
+ */
24373
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24374
+ };
23314
24375
  path: {
23315
24376
  tld: string;
23316
24377
  };
@@ -23357,7 +24418,13 @@ export interface operations {
23357
24418
  create_user_v1_users_post: {
23358
24419
  parameters: {
23359
24420
  query?: never;
23360
- header?: never;
24421
+ header?: {
24422
+ /**
24423
+ * @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.
24424
+ * @example rfc3339
24425
+ */
24426
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24427
+ };
23361
24428
  path?: never;
23362
24429
  cookie?: never;
23363
24430
  };
@@ -23392,7 +24459,13 @@ export interface operations {
23392
24459
  query?: {
23393
24460
  attributes?: string[] | null;
23394
24461
  };
23395
- header?: never;
24462
+ header?: {
24463
+ /**
24464
+ * @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.
24465
+ * @example rfc3339
24466
+ */
24467
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24468
+ };
23396
24469
  path?: never;
23397
24470
  cookie?: never;
23398
24471
  };
@@ -23423,7 +24496,13 @@ export interface operations {
23423
24496
  query?: {
23424
24497
  attributes?: string[] | null;
23425
24498
  };
23426
- header?: never;
24499
+ header?: {
24500
+ /**
24501
+ * @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.
24502
+ * @example rfc3339
24503
+ */
24504
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24505
+ };
23427
24506
  path: {
23428
24507
  user_id: TypeId<"user">;
23429
24508
  };
@@ -23454,7 +24533,13 @@ export interface operations {
23454
24533
  delete_user_v1_users__user_id__delete: {
23455
24534
  parameters: {
23456
24535
  query?: never;
23457
- header?: never;
24536
+ header?: {
24537
+ /**
24538
+ * @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.
24539
+ * @example rfc3339
24540
+ */
24541
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24542
+ };
23458
24543
  path: {
23459
24544
  user_id: TypeId<"user">;
23460
24545
  };
@@ -23492,7 +24577,13 @@ export interface operations {
23492
24577
  update_user_v1_users__user_id__patch: {
23493
24578
  parameters: {
23494
24579
  query?: never;
23495
- header?: never;
24580
+ header?: {
24581
+ /**
24582
+ * @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.
24583
+ * @example rfc3339
24584
+ */
24585
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24586
+ };
23496
24587
  path: {
23497
24588
  user_id: TypeId<"user">;
23498
24589
  };
@@ -23527,7 +24618,13 @@ export interface operations {
23527
24618
  get_user_permissions_v1_users__user_id__permissions_get: {
23528
24619
  parameters: {
23529
24620
  query?: never;
23530
- header?: never;
24621
+ header?: {
24622
+ /**
24623
+ * @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.
24624
+ * @example rfc3339
24625
+ */
24626
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24627
+ };
23531
24628
  path: {
23532
24629
  user_id: TypeId<"user">;
23533
24630
  };
@@ -23558,7 +24655,13 @@ export interface operations {
23558
24655
  get_role_v1_users__user_id__role_get: {
23559
24656
  parameters: {
23560
24657
  query?: never;
23561
- header?: never;
24658
+ header?: {
24659
+ /**
24660
+ * @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.
24661
+ * @example rfc3339
24662
+ */
24663
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24664
+ };
23562
24665
  path: {
23563
24666
  user_id: TypeId<"user">;
23564
24667
  };
@@ -23589,7 +24692,13 @@ export interface operations {
23589
24692
  set_user_role_v1_users__user_id__role_put: {
23590
24693
  parameters: {
23591
24694
  query?: never;
23592
- header?: never;
24695
+ header?: {
24696
+ /**
24697
+ * @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.
24698
+ * @example rfc3339
24699
+ */
24700
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24701
+ };
23593
24702
  path: {
23594
24703
  user_id: TypeId<"user">;
23595
24704
  };
@@ -23660,7 +24769,13 @@ export interface operations {
23660
24769
  page?: number;
23661
24770
  page_size?: number;
23662
24771
  };
23663
- header?: never;
24772
+ header?: {
24773
+ /**
24774
+ * @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.
24775
+ * @example rfc3339
24776
+ */
24777
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24778
+ };
23664
24779
  path?: never;
23665
24780
  cookie?: never;
23666
24781
  };
@@ -23689,7 +24804,13 @@ export interface operations {
23689
24804
  create_vanity_nameserver_set_v1_vanity_nameserver_sets_post: {
23690
24805
  parameters: {
23691
24806
  query?: never;
23692
- header?: never;
24807
+ header?: {
24808
+ /**
24809
+ * @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.
24810
+ * @example rfc3339
24811
+ */
24812
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24813
+ };
23693
24814
  path?: never;
23694
24815
  cookie?: never;
23695
24816
  };
@@ -23722,7 +24843,13 @@ export interface operations {
23722
24843
  check_vanity_nameserver_set_v1_vanity_nameserver_sets_check_post: {
23723
24844
  parameters: {
23724
24845
  query?: never;
23725
- header?: never;
24846
+ header?: {
24847
+ /**
24848
+ * @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.
24849
+ * @example rfc3339
24850
+ */
24851
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24852
+ };
23726
24853
  path?: never;
23727
24854
  cookie?: never;
23728
24855
  };
@@ -23755,7 +24882,13 @@ export interface operations {
23755
24882
  clear_vanity_nameserver_set_default_v1_vanity_nameserver_sets_default_delete: {
23756
24883
  parameters: {
23757
24884
  query?: never;
23758
- header?: never;
24885
+ header?: {
24886
+ /**
24887
+ * @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.
24888
+ * @example rfc3339
24889
+ */
24890
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24891
+ };
23759
24892
  path?: never;
23760
24893
  cookie?: never;
23761
24894
  };
@@ -23784,7 +24917,13 @@ export interface operations {
23784
24917
  get_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__get: {
23785
24918
  parameters: {
23786
24919
  query?: never;
23787
- header?: never;
24920
+ header?: {
24921
+ /**
24922
+ * @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.
24923
+ * @example rfc3339
24924
+ */
24925
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24926
+ };
23788
24927
  path: {
23789
24928
  set_id: TypeId<"vns">;
23790
24929
  };
@@ -23815,7 +24954,13 @@ export interface operations {
23815
24954
  delete_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__delete: {
23816
24955
  parameters: {
23817
24956
  query?: never;
23818
- header?: never;
24957
+ header?: {
24958
+ /**
24959
+ * @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.
24960
+ * @example rfc3339
24961
+ */
24962
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24963
+ };
23819
24964
  path: {
23820
24965
  set_id: TypeId<"vns">;
23821
24966
  };
@@ -23846,7 +24991,13 @@ export interface operations {
23846
24991
  set_vanity_nameserver_set_default_v1_vanity_nameserver_sets__set_id__default_patch: {
23847
24992
  parameters: {
23848
24993
  query?: never;
23849
- header?: never;
24994
+ header?: {
24995
+ /**
24996
+ * @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.
24997
+ * @example rfc3339
24998
+ */
24999
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25000
+ };
23850
25001
  path: {
23851
25002
  set_id: TypeId<"vns">;
23852
25003
  };
@@ -23877,7 +25028,13 @@ export interface operations {
23877
25028
  restore_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__restore_post: {
23878
25029
  parameters: {
23879
25030
  query?: never;
23880
- header?: never;
25031
+ header?: {
25032
+ /**
25033
+ * @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.
25034
+ * @example rfc3339
25035
+ */
25036
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25037
+ };
23881
25038
  path: {
23882
25039
  set_id: TypeId<"vns">;
23883
25040
  };
@@ -23908,7 +25065,13 @@ export interface operations {
23908
25065
  retry_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__retry_post: {
23909
25066
  parameters: {
23910
25067
  query?: never;
23911
- header?: never;
25068
+ header?: {
25069
+ /**
25070
+ * @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.
25071
+ * @example rfc3339
25072
+ */
25073
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25074
+ };
23912
25075
  path: {
23913
25076
  set_id: TypeId<"vns">;
23914
25077
  };
@@ -23942,7 +25105,13 @@ export interface operations {
23942
25105
  page?: number;
23943
25106
  page_size?: number;
23944
25107
  };
23945
- header?: never;
25108
+ header?: {
25109
+ /**
25110
+ * @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.
25111
+ * @example rfc3339
25112
+ */
25113
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25114
+ };
23946
25115
  path: {
23947
25116
  set_id: TypeId<"vns">;
23948
25117
  };