@opusdns/api 1.66.0 → 1.68.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
@@ -1253,6 +1253,64 @@ export interface paths {
1253
1253
  patch?: never;
1254
1254
  trace?: never;
1255
1255
  };
1256
+ "/v1/domains/tld-specific/no/applicant-declaration": {
1257
+ parameters: {
1258
+ query?: never;
1259
+ header?: never;
1260
+ path?: never;
1261
+ cookie?: never;
1262
+ };
1263
+ /** Retrieve the .no applicant declaration by token */
1264
+ get: operations["get_norid_declaration_by_token_v1_domains_tld_specific_no_applicant_declaration_get"];
1265
+ /**
1266
+ * Sign the .no applicant declaration with token
1267
+ * @description Records the applicant declaration signature (`acceptName` + `acceptDate`) and queues the actual registration at Norid.
1268
+ */
1269
+ put: operations["confirm_norid_declaration_by_token_v1_domains_tld_specific_no_applicant_declaration_put"];
1270
+ post?: never;
1271
+ delete?: never;
1272
+ options?: never;
1273
+ head?: never;
1274
+ patch?: never;
1275
+ trace?: never;
1276
+ };
1277
+ "/v1/domains/tld-specific/no/{domain_reference}/applicant-declaration": {
1278
+ parameters: {
1279
+ query?: never;
1280
+ header?: never;
1281
+ path?: never;
1282
+ cookie?: never;
1283
+ };
1284
+ get?: never;
1285
+ put?: never;
1286
+ /**
1287
+ * Submit the .no applicant declaration on behalf of the subscriber
1288
+ * @description Records the applicant declaration signature collected by the registrar (e.g. via Norid's own signing tool) and queues the actual registration at Norid, without the registrant email round-trip.
1289
+ */
1290
+ post: operations["submit_norid_declaration_v1_domains_tld_specific_no__domain_reference__applicant_declaration_post"];
1291
+ delete?: never;
1292
+ options?: never;
1293
+ head?: never;
1294
+ patch?: never;
1295
+ trace?: never;
1296
+ };
1297
+ "/v1/domains/tld-specific/no/{domain_reference}/resend-declaration-email": {
1298
+ parameters: {
1299
+ query?: never;
1300
+ header?: never;
1301
+ path?: never;
1302
+ cookie?: never;
1303
+ };
1304
+ get?: never;
1305
+ put?: never;
1306
+ /** Resend the .no applicant declaration email to the registrant */
1307
+ post: operations["resend_norid_declaration_email_v1_domains_tld_specific_no__domain_reference__resend_declaration_email_post"];
1308
+ delete?: never;
1309
+ options?: never;
1310
+ head?: never;
1311
+ patch?: never;
1312
+ trace?: never;
1313
+ };
1256
1314
  "/v1/domains/transfer": {
1257
1315
  parameters: {
1258
1316
  query?: never;
@@ -4945,7 +5003,7 @@ export interface components {
4945
5003
  * DomainAttributeKey
4946
5004
  * @enum {string}
4947
5005
  */
4948
- DomainAttributeKey: "auto_renew_period" | "music_registrant_attestation" | "nic_it_compliance_confirmation" | "travel_industry_acknowledgement" | "verification_required" | "de_general_request_contact" | "de_abuse_contact" | "nor_id_applicant_version" | "nor_id_applicant_accept_name" | "nor_id_applicant_accept_date";
5006
+ DomainAttributeKey: "auto_renew_period" | "music_registrant_attestation" | "nic_it_compliance_confirmation" | "travel_industry_acknowledgement" | "verification_required" | "de_general_request_contact" | "de_abuse_contact" | "nor_id_applicant_version" | "nor_id_applicant_accept_name" | "nor_id_applicant_accept_date" | "nor_id_declaration" | "nor_id_declaration_token";
4949
5007
  /** DomainAvailability */
4950
5008
  DomainAvailability: {
4951
5009
  /** Domain */
@@ -8559,6 +8617,83 @@ export interface components {
8559
8617
  */
8560
8618
  ip_addresses?: string[];
8561
8619
  };
8620
+ /** NorIdDeclarationConfirmRequest */
8621
+ NorIdDeclarationConfirmRequest: {
8622
+ /**
8623
+ * Accept Name
8624
+ * @description The full name of the person signing the applicant declaration. For private individuals this is the subscriber personally; for organizations it must be an authorized representative.
8625
+ */
8626
+ accept_name: string;
8627
+ };
8628
+ /** NorIdDeclarationResponse */
8629
+ NorIdDeclarationResponse: {
8630
+ /**
8631
+ * Declaration Contract Text
8632
+ * @description The fixed Norwegian declaration contract text
8633
+ */
8634
+ declaration_contract_text: string;
8635
+ /**
8636
+ * Declaration Header
8637
+ * @description The fixed Norwegian declaration header
8638
+ */
8639
+ declaration_header: string;
8640
+ /**
8641
+ * Declaration Introduction
8642
+ * @description The fixed Norwegian declaration introduction
8643
+ */
8644
+ declaration_introduction: string;
8645
+ /**
8646
+ * Declaration Version
8647
+ * @description The applicant declaration text version
8648
+ */
8649
+ declaration_version: string;
8650
+ /**
8651
+ * Domain Name
8652
+ * @description The domain name the declaration applies to
8653
+ */
8654
+ domain_name: string;
8655
+ /**
8656
+ * Expires On
8657
+ * Format: date-time
8658
+ * @description When the unconfirmed create request expires
8659
+ */
8660
+ expires_on: Date;
8661
+ /**
8662
+ * Identity Type
8663
+ * @description The subscriber identity type
8664
+ */
8665
+ identity_type?: string | null;
8666
+ /**
8667
+ * Identity Value
8668
+ * @description The subscriber identity (organization number or Person-ID)
8669
+ */
8670
+ identity_value?: string | null;
8671
+ /** @description The declaration status */
8672
+ status: components["schemas"]["NorIdDeclarationStatus"];
8673
+ /**
8674
+ * Subscriber Name
8675
+ * @description The domain name subscriber (registrant)
8676
+ */
8677
+ subscriber_name: string;
8678
+ };
8679
+ /**
8680
+ * NorIdDeclarationStatus
8681
+ * @enum {string}
8682
+ */
8683
+ NorIdDeclarationStatus: "pending" | "confirmed" | "completed" | "expired" | "failed";
8684
+ /** NorIdResellerDeclarationRequest */
8685
+ NorIdResellerDeclarationRequest: {
8686
+ /**
8687
+ * Accept Date
8688
+ * @description UTC timestamp of the declaration signature. Only provide it when the declaration was signed out-of-band (e.g. via Norid's own tool); defaults to the submission time.
8689
+ */
8690
+ accept_date?: Date | null;
8691
+ /**
8692
+ * Accept Name
8693
+ * @description The full name of the person signing the applicant declaration. For private individuals this is the subscriber personally; for organizations it must be an authorized representative.
8694
+ */
8695
+ accept_name: string;
8696
+ };
8562
8697
  /**
8563
8698
  * ObjectEventType
8564
8699
  * @enum {string}
@@ -11950,7 +12085,13 @@ export interface components {
11950
12085
  };
11951
12086
  };
11952
12087
  responses: never;
11953
- parameters: never;
12088
+ parameters: {
12089
+ /**
12090
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12091
+ * @example rfc3339
12092
+ */
12093
+ DatetimeFormatHeader: "rfc3339";
12094
+ };
11954
12095
  requestBodies: never;
11955
12096
  headers: never;
11956
12097
  pathItems: never;
@@ -11960,7 +12101,13 @@ export interface operations {
11960
12101
  get_context_v1_ai_concierge_contexts__context_id__get: {
11961
12102
  parameters: {
11962
12103
  query?: never;
11963
- header?: never;
12104
+ header?: {
12105
+ /**
12106
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12107
+ * @example rfc3339
12108
+ */
12109
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12110
+ };
11964
12111
  path: {
11965
12112
  context_id: TypeId<"ctx">;
11966
12113
  };
@@ -12046,7 +12193,13 @@ export interface operations {
12046
12193
  /** @description Full-text search on title/summary. */
12047
12194
  q?: string | null;
12048
12195
  };
12049
- header?: never;
12196
+ header?: {
12197
+ /**
12198
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12199
+ * @example rfc3339
12200
+ */
12201
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12202
+ };
12050
12203
  path?: never;
12051
12204
  cookie?: never;
12052
12205
  };
@@ -12123,7 +12276,13 @@ export interface operations {
12123
12276
  create_conversation_v1_ai_concierge_conversations_post: {
12124
12277
  parameters: {
12125
12278
  query?: never;
12126
- header?: never;
12279
+ header?: {
12280
+ /**
12281
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12282
+ * @example rfc3339
12283
+ */
12284
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12285
+ };
12127
12286
  path?: never;
12128
12287
  cookie?: never;
12129
12288
  };
@@ -12204,7 +12363,13 @@ export interface operations {
12204
12363
  get_conversation_v1_ai_concierge_conversations__conversation_id__get: {
12205
12364
  parameters: {
12206
12365
  query?: never;
12207
- header?: never;
12366
+ header?: {
12367
+ /**
12368
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12369
+ * @example rfc3339
12370
+ */
12371
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12372
+ };
12208
12373
  path: {
12209
12374
  conversation_id: TypeId<"conv">;
12210
12375
  };
@@ -12283,7 +12448,13 @@ export interface operations {
12283
12448
  delete_conversation_v1_ai_concierge_conversations__conversation_id__delete: {
12284
12449
  parameters: {
12285
12450
  query?: never;
12286
- header?: never;
12451
+ header?: {
12452
+ /**
12453
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12454
+ * @example rfc3339
12455
+ */
12456
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12457
+ };
12287
12458
  path: {
12288
12459
  conversation_id: TypeId<"conv">;
12289
12460
  };
@@ -12362,6 +12533,11 @@ export interface operations {
12362
12533
  query?: never;
12363
12534
  header?: {
12364
12535
  "If-Match"?: string | null;
12536
+ /**
12537
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12538
+ * @example rfc3339
12539
+ */
12540
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12365
12541
  };
12366
12542
  path: {
12367
12543
  conversation_id: TypeId<"conv">;
@@ -12448,7 +12624,13 @@ export interface operations {
12448
12624
  page?: number;
12449
12625
  page_size?: number;
12450
12626
  };
12451
- header?: never;
12627
+ header?: {
12628
+ /**
12629
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12630
+ * @example rfc3339
12631
+ */
12632
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12633
+ };
12452
12634
  path: {
12453
12635
  conversation_id: TypeId<"conv">;
12454
12636
  };
@@ -12527,7 +12709,13 @@ export interface operations {
12527
12709
  create_context_v1_ai_concierge_conversations__conversation_id__contexts_post: {
12528
12710
  parameters: {
12529
12711
  query?: never;
12530
- header?: never;
12712
+ header?: {
12713
+ /**
12714
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12715
+ * @example rfc3339
12716
+ */
12717
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12718
+ };
12531
12719
  path: {
12532
12720
  conversation_id: TypeId<"conv">;
12533
12721
  };
@@ -12617,7 +12805,13 @@ export interface operations {
12617
12805
  /** @description Comma-separated tokens to exclude (case-insensitive). Supports `tools`. */
12618
12806
  exclude?: string | null;
12619
12807
  };
12620
- header?: never;
12808
+ header?: {
12809
+ /**
12810
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12811
+ * @example rfc3339
12812
+ */
12813
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12814
+ };
12621
12815
  path: {
12622
12816
  conversation_id: TypeId<"conv">;
12623
12817
  };
@@ -12696,7 +12890,13 @@ export interface operations {
12696
12890
  create_message_v1_ai_concierge_conversations__conversation_id__messages_post: {
12697
12891
  parameters: {
12698
12892
  query?: never;
12699
- header?: never;
12893
+ header?: {
12894
+ /**
12895
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12896
+ * @example rfc3339
12897
+ */
12898
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12899
+ };
12700
12900
  path: {
12701
12901
  conversation_id: TypeId<"conv">;
12702
12902
  };
@@ -12779,7 +12979,13 @@ export interface operations {
12779
12979
  get_message_v1_ai_concierge_conversations__conversation_id__messages__message_id__get: {
12780
12980
  parameters: {
12781
12981
  query?: never;
12782
- header?: never;
12982
+ header?: {
12983
+ /**
12984
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
12985
+ * @example rfc3339
12986
+ */
12987
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
12988
+ };
12783
12989
  path: {
12784
12990
  conversation_id: TypeId<"conv">;
12785
12991
  message_id: TypeId<"msg">;
@@ -12863,7 +13069,13 @@ export interface operations {
12863
13069
  cursor?: string | null;
12864
13070
  kind?: string | null;
12865
13071
  };
12866
- header?: never;
13072
+ header?: {
13073
+ /**
13074
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13075
+ * @example rfc3339
13076
+ */
13077
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13078
+ };
12867
13079
  path?: never;
12868
13080
  cookie?: never;
12869
13081
  };
@@ -12940,7 +13152,13 @@ export interface operations {
12940
13152
  create_memory_fact_v1_ai_concierge_memory_facts_post: {
12941
13153
  parameters: {
12942
13154
  query?: never;
12943
- header?: never;
13155
+ header?: {
13156
+ /**
13157
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13158
+ * @example rfc3339
13159
+ */
13160
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13161
+ };
12944
13162
  path?: never;
12945
13163
  cookie?: never;
12946
13164
  };
@@ -13021,7 +13239,13 @@ export interface operations {
13021
13239
  delete_memory_fact_v1_ai_concierge_memory_facts__fact_id__delete: {
13022
13240
  parameters: {
13023
13241
  query?: never;
13024
- header?: never;
13242
+ header?: {
13243
+ /**
13244
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13245
+ * @example rfc3339
13246
+ */
13247
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13248
+ };
13025
13249
  path: {
13026
13250
  fact_id: TypeId<"fact">;
13027
13251
  };
@@ -13098,7 +13322,13 @@ export interface operations {
13098
13322
  patch_memory_fact_v1_ai_concierge_memory_facts__fact_id__patch: {
13099
13323
  parameters: {
13100
13324
  query?: never;
13101
- header?: never;
13325
+ header?: {
13326
+ /**
13327
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13328
+ * @example rfc3339
13329
+ */
13330
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13331
+ };
13102
13332
  path: {
13103
13333
  fact_id: TypeId<"fact">;
13104
13334
  };
@@ -13190,7 +13420,13 @@ export interface operations {
13190
13420
  start_time?: Date | null;
13191
13421
  end_time?: Date | null;
13192
13422
  };
13193
- header?: never;
13423
+ header?: {
13424
+ /**
13425
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13426
+ * @example rfc3339
13427
+ */
13428
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13429
+ };
13194
13430
  path: {
13195
13431
  email_forward_alias_id: TypeId<"email_forward_alias">;
13196
13432
  };
@@ -13229,7 +13465,13 @@ export interface operations {
13229
13465
  start_time?: Date | null;
13230
13466
  end_time?: Date | null;
13231
13467
  };
13232
- header?: never;
13468
+ header?: {
13469
+ /**
13470
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13471
+ * @example rfc3339
13472
+ */
13473
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13474
+ };
13233
13475
  path: {
13234
13476
  email_forward_id: TypeId<"email_forward">;
13235
13477
  };
@@ -13274,7 +13516,13 @@ export interface operations {
13274
13516
  created_after?: Date | null;
13275
13517
  object_id?: string | null;
13276
13518
  };
13277
- header?: never;
13519
+ header?: {
13520
+ /**
13521
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13522
+ * @example rfc3339
13523
+ */
13524
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13525
+ };
13278
13526
  path?: never;
13279
13527
  cookie?: never;
13280
13528
  };
@@ -13316,7 +13564,13 @@ export interface operations {
13316
13564
  created_before?: Date | null;
13317
13565
  created_after?: Date | null;
13318
13566
  };
13319
- header?: never;
13567
+ header?: {
13568
+ /**
13569
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13570
+ * @example rfc3339
13571
+ */
13572
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13573
+ };
13320
13574
  path: {
13321
13575
  object_id: string;
13322
13576
  };
@@ -13365,7 +13619,13 @@ export interface operations {
13365
13619
  request_started_before?: Date | null;
13366
13620
  request_started_after?: Date | null;
13367
13621
  };
13368
- header?: never;
13622
+ header?: {
13623
+ /**
13624
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13625
+ * @example rfc3339
13626
+ */
13627
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13628
+ };
13369
13629
  path?: never;
13370
13630
  cookie?: never;
13371
13631
  };
@@ -13394,7 +13654,13 @@ export interface operations {
13394
13654
  introspect_client_credential_v1_auth_client_credentials_introspect_get: {
13395
13655
  parameters: {
13396
13656
  query?: never;
13397
- header?: never;
13657
+ header?: {
13658
+ /**
13659
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13660
+ * @example rfc3339
13661
+ */
13662
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13663
+ };
13398
13664
  path?: never;
13399
13665
  cookie?: never;
13400
13666
  };
@@ -13439,7 +13705,13 @@ export interface operations {
13439
13705
  issue_organization_token_v1_auth_token_post: {
13440
13706
  parameters: {
13441
13707
  query?: never;
13442
- header?: never;
13708
+ header?: {
13709
+ /**
13710
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13711
+ * @example rfc3339
13712
+ */
13713
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13714
+ };
13443
13715
  path?: never;
13444
13716
  cookie?: never;
13445
13717
  };
@@ -13485,7 +13757,13 @@ export interface operations {
13485
13757
  * */
13486
13758
  domains: string[];
13487
13759
  };
13488
- header?: never;
13760
+ header?: {
13761
+ /**
13762
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13763
+ * @example rfc3339
13764
+ */
13765
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13766
+ };
13489
13767
  path?: never;
13490
13768
  cookie?: never;
13491
13769
  };
@@ -13535,7 +13813,13 @@ export interface operations {
13535
13813
  * */
13536
13814
  domains: string[];
13537
13815
  };
13538
- header?: never;
13816
+ header?: {
13817
+ /**
13818
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13819
+ * @example rfc3339
13820
+ */
13821
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13822
+ };
13539
13823
  path?: never;
13540
13824
  cookie?: never;
13541
13825
  };
@@ -13580,7 +13864,13 @@ export interface operations {
13580
13864
  stream_availability_post_v1_availability_stream_post: {
13581
13865
  parameters: {
13582
13866
  query?: never;
13583
- header?: never;
13867
+ header?: {
13868
+ /**
13869
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13870
+ * @example rfc3339
13871
+ */
13872
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13873
+ };
13584
13874
  path?: never;
13585
13875
  cookie?: never;
13586
13876
  };
@@ -13649,7 +13939,13 @@ export interface operations {
13649
13939
  /** @description Include additional data in the response. Can be specified multiple times. */
13650
13940
  include?: components["schemas"]["ContactIncludeField"][] | null;
13651
13941
  };
13652
- header?: never;
13942
+ header?: {
13943
+ /**
13944
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13945
+ * @example rfc3339
13946
+ */
13947
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13948
+ };
13653
13949
  path?: never;
13654
13950
  cookie?: never;
13655
13951
  };
@@ -13678,7 +13974,13 @@ export interface operations {
13678
13974
  create_contact_v1_contacts_post: {
13679
13975
  parameters: {
13680
13976
  query?: never;
13681
- header?: never;
13977
+ header?: {
13978
+ /**
13979
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
13980
+ * @example rfc3339
13981
+ */
13982
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
13983
+ };
13682
13984
  path?: never;
13683
13985
  cookie?: never;
13684
13986
  };
@@ -13718,7 +14020,13 @@ export interface operations {
13718
14020
  tld?: string | null;
13719
14021
  label?: string | null;
13720
14022
  };
13721
- header?: never;
14023
+ header?: {
14024
+ /**
14025
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14026
+ * @example rfc3339
14027
+ */
14028
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14029
+ };
13722
14030
  path?: never;
13723
14031
  cookie?: never;
13724
14032
  };
@@ -13747,7 +14055,13 @@ export interface operations {
13747
14055
  create_attribute_set_v1_contacts_attribute_sets_post: {
13748
14056
  parameters: {
13749
14057
  query?: never;
13750
- header?: never;
14058
+ header?: {
14059
+ /**
14060
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14061
+ * @example rfc3339
14062
+ */
14063
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14064
+ };
13751
14065
  path?: never;
13752
14066
  cookie?: never;
13753
14067
  };
@@ -13797,7 +14111,13 @@ export interface operations {
13797
14111
  get_attribute_set_v1_contacts_attribute_sets__contact_attribute_set_id__get: {
13798
14112
  parameters: {
13799
14113
  query?: never;
13800
- header?: never;
14114
+ header?: {
14115
+ /**
14116
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14117
+ * @example rfc3339
14118
+ */
14119
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14120
+ };
13801
14121
  path: {
13802
14122
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
13803
14123
  };
@@ -13845,7 +14165,13 @@ export interface operations {
13845
14165
  delete_attribute_set_v1_contacts_attribute_sets__contact_attribute_set_id__delete: {
13846
14166
  parameters: {
13847
14167
  query?: never;
13848
- header?: never;
14168
+ header?: {
14169
+ /**
14170
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14171
+ * @example rfc3339
14172
+ */
14173
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14174
+ };
13849
14175
  path: {
13850
14176
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
13851
14177
  };
@@ -13891,7 +14217,13 @@ export interface operations {
13891
14217
  update_attribute_set_v1_contacts_attribute_sets__contact_attribute_set_id__patch: {
13892
14218
  parameters: {
13893
14219
  query?: never;
13894
- header?: never;
14220
+ header?: {
14221
+ /**
14222
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14223
+ * @example rfc3339
14224
+ */
14225
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14226
+ };
13895
14227
  path: {
13896
14228
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
13897
14229
  };
@@ -13962,7 +14294,13 @@ export interface operations {
13962
14294
  query: {
13963
14295
  token: string;
13964
14296
  };
13965
- header?: never;
14297
+ header?: {
14298
+ /**
14299
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14300
+ * @example rfc3339
14301
+ */
14302
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14303
+ };
13966
14304
  path?: never;
13967
14305
  cookie?: never;
13968
14306
  };
@@ -14026,7 +14364,13 @@ export interface operations {
14026
14364
  query: {
14027
14365
  token: string;
14028
14366
  };
14029
- header?: never;
14367
+ header?: {
14368
+ /**
14369
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14370
+ * @example rfc3339
14371
+ */
14372
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14373
+ };
14030
14374
  path?: never;
14031
14375
  cookie?: never;
14032
14376
  };
@@ -14097,7 +14441,13 @@ export interface operations {
14097
14441
  query: {
14098
14442
  token: string;
14099
14443
  };
14100
- header?: never;
14444
+ header?: {
14445
+ /**
14446
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14447
+ * @example rfc3339
14448
+ */
14449
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14450
+ };
14101
14451
  path?: never;
14102
14452
  cookie?: never;
14103
14453
  };
@@ -14128,7 +14478,13 @@ export interface operations {
14128
14478
  query?: {
14129
14479
  include?: components["schemas"]["ContactIncludeField"][] | null;
14130
14480
  };
14131
- header?: never;
14481
+ header?: {
14482
+ /**
14483
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14484
+ * @example rfc3339
14485
+ */
14486
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14487
+ };
14132
14488
  path: {
14133
14489
  contact_id: TypeId<"contact">;
14134
14490
  };
@@ -14176,7 +14532,13 @@ export interface operations {
14176
14532
  delete_contact_v1_contacts__contact_id__delete: {
14177
14533
  parameters: {
14178
14534
  query?: never;
14179
- header?: never;
14535
+ header?: {
14536
+ /**
14537
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14538
+ * @example rfc3339
14539
+ */
14540
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14541
+ };
14180
14542
  path: {
14181
14543
  contact_id: TypeId<"contact">;
14182
14544
  };
@@ -14238,7 +14600,13 @@ export interface operations {
14238
14600
  create_attribute_link_v1_contacts__contact_id__link__contact_attribute_set_id__patch: {
14239
14601
  parameters: {
14240
14602
  query?: never;
14241
- header?: never;
14603
+ header?: {
14604
+ /**
14605
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14606
+ * @example rfc3339
14607
+ */
14608
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14609
+ };
14242
14610
  path: {
14243
14611
  contact_id: TypeId<"contact">;
14244
14612
  contact_attribute_set_id: TypeId<"contact_attribute_set">;
@@ -14297,7 +14665,13 @@ export interface operations {
14297
14665
  get_verification_status_v1_contacts__contact_id__verification_get: {
14298
14666
  parameters: {
14299
14667
  query?: never;
14300
- header?: never;
14668
+ header?: {
14669
+ /**
14670
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14671
+ * @example rfc3339
14672
+ */
14673
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14674
+ };
14301
14675
  path: {
14302
14676
  contact_id: TypeId<"contact">;
14303
14677
  };
@@ -14363,7 +14737,13 @@ export interface operations {
14363
14737
  query: {
14364
14738
  token: string;
14365
14739
  };
14366
- header?: never;
14740
+ header?: {
14741
+ /**
14742
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14743
+ * @example rfc3339
14744
+ */
14745
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14746
+ };
14367
14747
  path: {
14368
14748
  contact_id: TypeId<"contact">;
14369
14749
  };
@@ -14452,7 +14832,13 @@ export interface operations {
14452
14832
  query: {
14453
14833
  type: components["schemas"]["VerificationType"];
14454
14834
  };
14455
- header?: never;
14835
+ header?: {
14836
+ /**
14837
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14838
+ * @example rfc3339
14839
+ */
14840
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14841
+ };
14456
14842
  path: {
14457
14843
  contact_id: TypeId<"contact">;
14458
14844
  };
@@ -14532,7 +14918,13 @@ export interface operations {
14532
14918
  cancel_verification_v1_contacts__contact_id__verification_delete: {
14533
14919
  parameters: {
14534
14920
  query?: never;
14535
- header?: never;
14921
+ header?: {
14922
+ /**
14923
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14924
+ * @example rfc3339
14925
+ */
14926
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14927
+ };
14536
14928
  path: {
14537
14929
  contact_id: TypeId<"contact">;
14538
14930
  };
@@ -14594,7 +14986,13 @@ export interface operations {
14594
14986
  get_contact_verification_status_v1_contacts__contact_id__verifications_get: {
14595
14987
  parameters: {
14596
14988
  query?: never;
14597
- header?: never;
14989
+ header?: {
14990
+ /**
14991
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
14992
+ * @example rfc3339
14993
+ */
14994
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
14995
+ };
14598
14996
  path: {
14599
14997
  contact_id: TypeId<"contact">;
14600
14998
  };
@@ -14674,7 +15072,13 @@ export interface operations {
14674
15072
  attest_contact_verification_v1_contacts__contact_id__verifications_attest_post: {
14675
15073
  parameters: {
14676
15074
  query?: never;
14677
- header?: never;
15075
+ header?: {
15076
+ /**
15077
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15078
+ * @example rfc3339
15079
+ */
15080
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15081
+ };
14678
15082
  path: {
14679
15083
  contact_id: TypeId<"contact">;
14680
15084
  };
@@ -14794,7 +15198,13 @@ export interface operations {
14794
15198
  /** @description Include additional data in the response. Can be specified multiple times. */
14795
15199
  include?: components["schemas"]["ZoneIncludeField"][] | null;
14796
15200
  };
14797
- header?: never;
15201
+ header?: {
15202
+ /**
15203
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15204
+ * @example rfc3339
15205
+ */
15206
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15207
+ };
14798
15208
  path?: never;
14799
15209
  cookie?: never;
14800
15210
  };
@@ -14823,7 +15233,13 @@ export interface operations {
14823
15233
  create_zone_v1_dns_post: {
14824
15234
  parameters: {
14825
15235
  query?: never;
14826
- header?: never;
15236
+ header?: {
15237
+ /**
15238
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15239
+ * @example rfc3339
15240
+ */
15241
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15242
+ };
14827
15243
  path?: never;
14828
15244
  cookie?: never;
14829
15245
  };
@@ -14878,7 +15294,13 @@ export interface operations {
14878
15294
  sort_by?: components["schemas"]["DomainForwardZoneSortField"];
14879
15295
  sort_order?: components["schemas"]["SortOrder"];
14880
15296
  };
14881
- header?: never;
15297
+ header?: {
15298
+ /**
15299
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15300
+ * @example rfc3339
15301
+ */
15302
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15303
+ };
14882
15304
  path?: never;
14883
15305
  cookie?: never;
14884
15306
  };
@@ -14945,7 +15367,13 @@ export interface operations {
14945
15367
  sort_by?: components["schemas"]["EmailForwardZoneSortField"];
14946
15368
  sort_order?: components["schemas"]["SortOrder"];
14947
15369
  };
14948
- header?: never;
15370
+ header?: {
15371
+ /**
15372
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15373
+ * @example rfc3339
15374
+ */
15375
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15376
+ };
14949
15377
  path?: never;
14950
15378
  cookie?: never;
14951
15379
  };
@@ -15006,7 +15434,13 @@ export interface operations {
15006
15434
  get_zones_summary_v1_dns_summary_get: {
15007
15435
  parameters: {
15008
15436
  query?: never;
15009
- header?: never;
15437
+ header?: {
15438
+ /**
15439
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15440
+ * @example rfc3339
15441
+ */
15442
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15443
+ };
15010
15444
  path?: never;
15011
15445
  cookie?: never;
15012
15446
  };
@@ -15037,7 +15471,13 @@ export interface operations {
15037
15471
  query?: {
15038
15472
  include?: components["schemas"]["ZoneIncludeField"][] | null;
15039
15473
  };
15040
- header?: never;
15474
+ header?: {
15475
+ /**
15476
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15477
+ * @example rfc3339
15478
+ */
15479
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15480
+ };
15041
15481
  path: {
15042
15482
  /** @description DNS zone name (trailing dot optional) */
15043
15483
  zone_name: string;
@@ -15069,7 +15509,13 @@ export interface operations {
15069
15509
  delete_zone_v1_dns__zone_name__delete: {
15070
15510
  parameters: {
15071
15511
  query?: never;
15072
- header?: never;
15512
+ header?: {
15513
+ /**
15514
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15515
+ * @example rfc3339
15516
+ */
15517
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15518
+ };
15073
15519
  path: {
15074
15520
  /** @description DNS zone name (trailing dot optional) */
15075
15521
  zone_name: string;
@@ -15099,7 +15545,13 @@ export interface operations {
15099
15545
  disable_dnssec_v1_dns__zone_name__dnssec_disable_post: {
15100
15546
  parameters: {
15101
15547
  query?: never;
15102
- header?: never;
15548
+ header?: {
15549
+ /**
15550
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15551
+ * @example rfc3339
15552
+ */
15553
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15554
+ };
15103
15555
  path: {
15104
15556
  /** @description DNS zone name (trailing dot optional) */
15105
15557
  zone_name: string;
@@ -15147,7 +15599,13 @@ export interface operations {
15147
15599
  enable_dnssec_v1_dns__zone_name__dnssec_enable_post: {
15148
15600
  parameters: {
15149
15601
  query?: never;
15150
- header?: never;
15602
+ header?: {
15603
+ /**
15604
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15605
+ * @example rfc3339
15606
+ */
15607
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15608
+ };
15151
15609
  path: {
15152
15610
  /** @description DNS zone name (trailing dot optional) */
15153
15611
  zone_name: string;
@@ -15195,7 +15653,13 @@ export interface operations {
15195
15653
  list_zone_domain_forwards_v1_dns__zone_name__domain_forwards_get: {
15196
15654
  parameters: {
15197
15655
  query?: never;
15198
- header?: never;
15656
+ header?: {
15657
+ /**
15658
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15659
+ * @example rfc3339
15660
+ */
15661
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15662
+ };
15199
15663
  path: {
15200
15664
  /** @description DNS zone name (trailing dot optional) */
15201
15665
  zone_name: string;
@@ -15259,7 +15723,13 @@ export interface operations {
15259
15723
  list_zone_email_forwards_v1_dns__zone_name__email_forwards_get: {
15260
15724
  parameters: {
15261
15725
  query?: never;
15262
- header?: never;
15726
+ header?: {
15727
+ /**
15728
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15729
+ * @example rfc3339
15730
+ */
15731
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15732
+ };
15263
15733
  path: {
15264
15734
  /** @description DNS zone name (trailing dot optional) */
15265
15735
  zone_name: string;
@@ -15323,7 +15793,13 @@ export interface operations {
15323
15793
  patch_zone_records_v1_dns__zone_name__records_patch: {
15324
15794
  parameters: {
15325
15795
  query?: never;
15326
- header?: never;
15796
+ header?: {
15797
+ /**
15798
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15799
+ * @example rfc3339
15800
+ */
15801
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15802
+ };
15327
15803
  path: {
15328
15804
  /** @description DNS zone name (trailing dot optional) */
15329
15805
  zone_name: string;
@@ -15373,7 +15849,13 @@ export interface operations {
15373
15849
  update_zone_rrsets_v1_dns__zone_name__rrsets_put: {
15374
15850
  parameters: {
15375
15851
  query?: never;
15376
- header?: never;
15852
+ header?: {
15853
+ /**
15854
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15855
+ * @example rfc3339
15856
+ */
15857
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15858
+ };
15377
15859
  path: {
15378
15860
  /** @description DNS zone name (trailing dot optional) */
15379
15861
  zone_name: string;
@@ -15423,7 +15905,13 @@ export interface operations {
15423
15905
  patch_zone_rrsets_v1_dns__zone_name__rrsets_patch: {
15424
15906
  parameters: {
15425
15907
  query?: never;
15426
- header?: never;
15908
+ header?: {
15909
+ /**
15910
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15911
+ * @example rfc3339
15912
+ */
15913
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15914
+ };
15427
15915
  path: {
15428
15916
  /** @description DNS zone name (trailing dot optional) */
15429
15917
  zone_name: string;
@@ -15473,7 +15961,13 @@ export interface operations {
15473
15961
  update_zone_vanity_set_v1_dns__zone_name__vanity_set_patch: {
15474
15962
  parameters: {
15475
15963
  query?: never;
15476
- header?: never;
15964
+ header?: {
15965
+ /**
15966
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
15967
+ * @example rfc3339
15968
+ */
15969
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
15970
+ };
15477
15971
  path: {
15478
15972
  /** @description DNS zone name (trailing dot optional) */
15479
15973
  zone_name: string;
@@ -15531,7 +16025,13 @@ export interface operations {
15531
16025
  sort_by?: components["schemas"]["DomainForwardSortField"];
15532
16026
  sort_order?: components["schemas"]["SortOrder"];
15533
16027
  };
15534
- header?: never;
16028
+ header?: {
16029
+ /**
16030
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16031
+ * @example rfc3339
16032
+ */
16033
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16034
+ };
15535
16035
  path?: never;
15536
16036
  cookie?: never;
15537
16037
  };
@@ -15592,7 +16092,13 @@ export interface operations {
15592
16092
  create_domain_forward_v2_v1_domain_forwards_post: {
15593
16093
  parameters: {
15594
16094
  query?: never;
15595
- header?: never;
16095
+ header?: {
16096
+ /**
16097
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16098
+ * @example rfc3339
16099
+ */
16100
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16101
+ };
15596
16102
  path?: never;
15597
16103
  cookie?: never;
15598
16104
  };
@@ -15690,7 +16196,13 @@ export interface operations {
15690
16196
  patch_redirects_v1_domain_forwards_patch: {
15691
16197
  parameters: {
15692
16198
  query?: never;
15693
- header?: never;
16199
+ header?: {
16200
+ /**
16201
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16202
+ * @example rfc3339
16203
+ */
16204
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16205
+ };
15694
16206
  path?: never;
15695
16207
  cookie?: never;
15696
16208
  };
@@ -15778,7 +16290,13 @@ export interface operations {
15778
16290
  /** @description Exclude platform values: Unknown, Bot */
15779
16291
  exclude_bots?: boolean;
15780
16292
  };
15781
- header?: never;
16293
+ header?: {
16294
+ /**
16295
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16296
+ * @example rfc3339
16297
+ */
16298
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16299
+ };
15782
16300
  path?: never;
15783
16301
  cookie?: never;
15784
16302
  };
@@ -15876,7 +16394,13 @@ export interface operations {
15876
16394
  /** @description Exclude platform values: Unknown, Bot */
15877
16395
  exclude_bots?: boolean;
15878
16396
  };
15879
- header?: never;
16397
+ header?: {
16398
+ /**
16399
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16400
+ * @example rfc3339
16401
+ */
16402
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16403
+ };
15880
16404
  path?: never;
15881
16405
  cookie?: never;
15882
16406
  };
@@ -15974,7 +16498,13 @@ export interface operations {
15974
16498
  /** @description Exclude platform values: Unknown, Bot */
15975
16499
  exclude_bots?: boolean;
15976
16500
  };
15977
- header?: never;
16501
+ header?: {
16502
+ /**
16503
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16504
+ * @example rfc3339
16505
+ */
16506
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16507
+ };
15978
16508
  path?: never;
15979
16509
  cookie?: never;
15980
16510
  };
@@ -16072,7 +16602,13 @@ export interface operations {
16072
16602
  /** @description Exclude platform values: Unknown, Bot */
16073
16603
  exclude_bots?: boolean;
16074
16604
  };
16075
- header?: never;
16605
+ header?: {
16606
+ /**
16607
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16608
+ * @example rfc3339
16609
+ */
16610
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16611
+ };
16076
16612
  path?: never;
16077
16613
  cookie?: never;
16078
16614
  };
@@ -16170,7 +16706,13 @@ export interface operations {
16170
16706
  /** @description Exclude platform values: Unknown, Bot */
16171
16707
  exclude_bots?: boolean;
16172
16708
  };
16173
- header?: never;
16709
+ header?: {
16710
+ /**
16711
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16712
+ * @example rfc3339
16713
+ */
16714
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16715
+ };
16174
16716
  path?: never;
16175
16717
  cookie?: never;
16176
16718
  };
@@ -16268,7 +16810,13 @@ export interface operations {
16268
16810
  /** @description Exclude platform values: Unknown, Bot */
16269
16811
  exclude_bots?: boolean;
16270
16812
  };
16271
- header?: never;
16813
+ header?: {
16814
+ /**
16815
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16816
+ * @example rfc3339
16817
+ */
16818
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16819
+ };
16272
16820
  path?: never;
16273
16821
  cookie?: never;
16274
16822
  };
@@ -16366,7 +16914,13 @@ export interface operations {
16366
16914
  /** @description Exclude platform values: Unknown, Bot */
16367
16915
  exclude_bots?: boolean;
16368
16916
  };
16369
- header?: never;
16917
+ header?: {
16918
+ /**
16919
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
16920
+ * @example rfc3339
16921
+ */
16922
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
16923
+ };
16370
16924
  path?: never;
16371
16925
  cookie?: never;
16372
16926
  };
@@ -16464,7 +17018,13 @@ export interface operations {
16464
17018
  /** @description Exclude platform values: Unknown, Bot */
16465
17019
  exclude_bots?: boolean;
16466
17020
  };
16467
- header?: never;
17021
+ header?: {
17022
+ /**
17023
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17024
+ * @example rfc3339
17025
+ */
17026
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17027
+ };
16468
17028
  path?: never;
16469
17029
  cookie?: never;
16470
17030
  };
@@ -16564,7 +17124,13 @@ export interface operations {
16564
17124
  /** @description Exclude platform values: Unknown, Bot */
16565
17125
  exclude_bots?: boolean;
16566
17126
  };
16567
- header?: never;
17127
+ header?: {
17128
+ /**
17129
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17130
+ * @example rfc3339
17131
+ */
17132
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17133
+ };
16568
17134
  path?: never;
16569
17135
  cookie?: never;
16570
17136
  };
@@ -16653,7 +17219,13 @@ export interface operations {
16653
17219
  get_domain_forward_v1_domain_forwards__hostname__get: {
16654
17220
  parameters: {
16655
17221
  query?: never;
16656
- header?: never;
17222
+ header?: {
17223
+ /**
17224
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17225
+ * @example rfc3339
17226
+ */
17227
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17228
+ };
16657
17229
  path: {
16658
17230
  /** @description Hostname */
16659
17231
  hostname: string;
@@ -16733,7 +17305,13 @@ export interface operations {
16733
17305
  create_domain_forward_set_v1_domain_forwards__hostname__post: {
16734
17306
  parameters: {
16735
17307
  query?: never;
16736
- header?: never;
17308
+ header?: {
17309
+ /**
17310
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17311
+ * @example rfc3339
17312
+ */
17313
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17314
+ };
16737
17315
  path: {
16738
17316
  /** @description Hostname */
16739
17317
  hostname: string;
@@ -16833,7 +17411,13 @@ export interface operations {
16833
17411
  delete_domain_forward_v1_domain_forwards__hostname__delete: {
16834
17412
  parameters: {
16835
17413
  query?: never;
16836
- header?: never;
17414
+ header?: {
17415
+ /**
17416
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17417
+ * @example rfc3339
17418
+ */
17419
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17420
+ };
16837
17421
  path: {
16838
17422
  /** @description Hostname */
16839
17423
  hostname: string;
@@ -16911,7 +17495,13 @@ export interface operations {
16911
17495
  disable_domain_forward_v1_domain_forwards__hostname__disable_patch: {
16912
17496
  parameters: {
16913
17497
  query?: never;
16914
- header?: never;
17498
+ header?: {
17499
+ /**
17500
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17501
+ * @example rfc3339
17502
+ */
17503
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17504
+ };
16915
17505
  path: {
16916
17506
  /** @description Hostname */
16917
17507
  hostname: string;
@@ -16973,7 +17563,13 @@ export interface operations {
16973
17563
  enable_domain_forward_v1_domain_forwards__hostname__enable_patch: {
16974
17564
  parameters: {
16975
17565
  query?: never;
16976
- header?: never;
17566
+ header?: {
17567
+ /**
17568
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17569
+ * @example rfc3339
17570
+ */
17571
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17572
+ };
16977
17573
  path: {
16978
17574
  /** @description Hostname */
16979
17575
  hostname: string;
@@ -17035,7 +17631,13 @@ export interface operations {
17035
17631
  get_domain_forward_set_v1_domain_forwards__hostname___protocol__get: {
17036
17632
  parameters: {
17037
17633
  query?: never;
17038
- header?: never;
17634
+ header?: {
17635
+ /**
17636
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17637
+ * @example rfc3339
17638
+ */
17639
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17640
+ };
17039
17641
  path: {
17040
17642
  protocol: components["schemas"]["HttpProtocol"];
17041
17643
  /** @description Hostname */
@@ -17116,7 +17718,13 @@ export interface operations {
17116
17718
  update_domain_forward_set_v1_domain_forwards__hostname___protocol__put: {
17117
17719
  parameters: {
17118
17720
  query?: never;
17119
- header?: never;
17721
+ header?: {
17722
+ /**
17723
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17724
+ * @example rfc3339
17725
+ */
17726
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17727
+ };
17120
17728
  path: {
17121
17729
  protocol: components["schemas"]["HttpProtocol"];
17122
17730
  /** @description Hostname */
@@ -17201,7 +17809,13 @@ export interface operations {
17201
17809
  delete_domain_forward_set_v1_domain_forwards__hostname___protocol__delete: {
17202
17810
  parameters: {
17203
17811
  query?: never;
17204
- header?: never;
17812
+ header?: {
17813
+ /**
17814
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
17815
+ * @example rfc3339
17816
+ */
17817
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
17818
+ };
17205
17819
  path: {
17206
17820
  protocol: components["schemas"]["HttpProtocol"];
17207
17821
  /** @description Hostname */
@@ -17289,7 +17903,13 @@ export interface operations {
17289
17903
  /** @description Whether to include premium domains in the suggestions */
17290
17904
  premium?: boolean | null;
17291
17905
  };
17292
- 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
+ };
17293
17913
  path?: never;
17294
17914
  cookie?: never;
17295
17915
  };
@@ -17383,7 +18003,13 @@ export interface operations {
17383
18003
  /** @description Include additional data in the response. Can be specified multiple times. */
17384
18004
  include?: components["schemas"]["DomainIncludeField"][] | null;
17385
18005
  };
17386
- header?: never;
18006
+ header?: {
18007
+ /**
18008
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18009
+ * @example rfc3339
18010
+ */
18011
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18012
+ };
17387
18013
  path?: never;
17388
18014
  cookie?: never;
17389
18015
  };
@@ -17412,7 +18038,13 @@ export interface operations {
17412
18038
  create_domain_v1_domains_post: {
17413
18039
  parameters: {
17414
18040
  query?: never;
17415
- header?: never;
18041
+ header?: {
18042
+ /**
18043
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18044
+ * @example rfc3339
18045
+ */
18046
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18047
+ };
17416
18048
  path?: never;
17417
18049
  cookie?: never;
17418
18050
  };
@@ -17505,7 +18137,13 @@ export interface operations {
17505
18137
  * */
17506
18138
  domains: string[];
17507
18139
  };
17508
- header?: never;
18140
+ header?: {
18141
+ /**
18142
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18143
+ * @example rfc3339
18144
+ */
18145
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18146
+ };
17509
18147
  path?: never;
17510
18148
  cookie?: never;
17511
18149
  };
@@ -17534,7 +18172,13 @@ export interface operations {
17534
18172
  get_claims_notices_v1_domains_claims_notices_post: {
17535
18173
  parameters: {
17536
18174
  query?: never;
17537
- header?: never;
18175
+ header?: {
18176
+ /**
18177
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18178
+ * @example rfc3339
18179
+ */
18180
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18181
+ };
17538
18182
  path?: never;
17539
18183
  cookie?: never;
17540
18184
  };
@@ -17599,7 +18243,13 @@ export interface operations {
17599
18243
  get_domain_summary_v1_domains_summary_get: {
17600
18244
  parameters: {
17601
18245
  query?: never;
17602
- header?: never;
18246
+ header?: {
18247
+ /**
18248
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18249
+ * @example rfc3339
18250
+ */
18251
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18252
+ };
17603
18253
  path?: never;
17604
18254
  cookie?: never;
17605
18255
  };
@@ -17628,7 +18278,13 @@ export interface operations {
17628
18278
  withdraw_domain_v1_domains_tld_specific_at__domain_reference__withdraw_post: {
17629
18279
  parameters: {
17630
18280
  query?: never;
17631
- header?: never;
18281
+ header?: {
18282
+ /**
18283
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18284
+ * @example rfc3339
18285
+ */
18286
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18287
+ };
17632
18288
  path: {
17633
18289
  domain_reference: TypeId<"domain"> | string;
17634
18290
  };
@@ -17680,7 +18336,13 @@ export interface operations {
17680
18336
  request_auth_code_v1_domains_tld_specific_be__domain_reference__auth_code_request_post: {
17681
18337
  parameters: {
17682
18338
  query?: never;
17683
- header?: never;
18339
+ header?: {
18340
+ /**
18341
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18342
+ * @example rfc3339
18343
+ */
18344
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18345
+ };
17684
18346
  path: {
17685
18347
  domain_reference: TypeId<"domain"> | string;
17686
18348
  };
@@ -17746,7 +18408,13 @@ export interface operations {
17746
18408
  transit_domain_v1_domains_tld_specific_de__domain_reference__transit_post: {
17747
18409
  parameters: {
17748
18410
  query?: never;
17749
- header?: never;
18411
+ header?: {
18412
+ /**
18413
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18414
+ * @example rfc3339
18415
+ */
18416
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18417
+ };
17750
18418
  path: {
17751
18419
  domain_reference: TypeId<"domain"> | string;
17752
18420
  };
@@ -17798,7 +18466,13 @@ export interface operations {
17798
18466
  request_auth_code_v1_domains_tld_specific_eu__domain_reference__auth_code_request_post: {
17799
18467
  parameters: {
17800
18468
  query?: never;
17801
- header?: never;
18469
+ header?: {
18470
+ /**
18471
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18472
+ * @example rfc3339
18473
+ */
18474
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18475
+ };
17802
18476
  path: {
17803
18477
  domain_reference: TypeId<"domain"> | string;
17804
18478
  };
@@ -17864,7 +18538,13 @@ export interface operations {
17864
18538
  request_auth_code_v1_domains_tld_specific_lt__domain_reference__auth_code_request_post: {
17865
18539
  parameters: {
17866
18540
  query?: never;
17867
- header?: never;
18541
+ header?: {
18542
+ /**
18543
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18544
+ * @example rfc3339
18545
+ */
18546
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18547
+ };
17868
18548
  path: {
17869
18549
  domain_reference: TypeId<"domain"> | string;
17870
18550
  };
@@ -17927,10 +18607,303 @@ export interface operations {
17927
18607
  };
17928
18608
  };
17929
18609
  };
18610
+ get_norid_declaration_by_token_v1_domains_tld_specific_no_applicant_declaration_get: {
18611
+ parameters: {
18612
+ query: {
18613
+ token: string;
18614
+ };
18615
+ header?: {
18616
+ /**
18617
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18618
+ * @example rfc3339
18619
+ */
18620
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18621
+ };
18622
+ path?: never;
18623
+ cookie?: never;
18624
+ };
18625
+ requestBody?: never;
18626
+ responses: {
18627
+ /** @description Successful Response */
18628
+ 200: {
18629
+ headers: {
18630
+ [name: string]: unknown;
18631
+ };
18632
+ content: {
18633
+ "application/json": components["schemas"]["NorIdDeclarationResponse"];
18634
+ };
18635
+ };
18636
+ /** @description Not Found */
18637
+ 404: {
18638
+ headers: {
18639
+ [name: string]: unknown;
18640
+ };
18641
+ content: {
18642
+ /** @example {
18643
+ * "code": "ERROR_NORID_DECLARATION_NOT_FOUND",
18644
+ * "detail": "Additional error context.",
18645
+ * "status": 404,
18646
+ * "title": "Domain Management Error",
18647
+ * "type": "nor-id-declaration-not-found"
18648
+ * } */
18649
+ "application/problem+json": components["schemas"]["Problem"];
18650
+ };
18651
+ };
18652
+ /** @description Validation Error */
18653
+ 422: {
18654
+ headers: {
18655
+ [name: string]: unknown;
18656
+ };
18657
+ content: {
18658
+ "application/problem+json": components["schemas"]["HTTPValidationError"];
18659
+ };
18660
+ };
18661
+ };
18662
+ };
18663
+ confirm_norid_declaration_by_token_v1_domains_tld_specific_no_applicant_declaration_put: {
18664
+ parameters: {
18665
+ query: {
18666
+ token: string;
18667
+ };
18668
+ header?: {
18669
+ /**
18670
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18671
+ * @example rfc3339
18672
+ */
18673
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18674
+ };
18675
+ path?: never;
18676
+ cookie?: never;
18677
+ };
18678
+ requestBody: {
18679
+ content: {
18680
+ "application/json": components["schemas"]["NorIdDeclarationConfirmRequest"];
18681
+ };
18682
+ };
18683
+ responses: {
18684
+ /** @description Successful Response */
18685
+ 204: {
18686
+ headers: {
18687
+ [name: string]: unknown;
18688
+ };
18689
+ content?: never;
18690
+ };
18691
+ /** @description Bad Request */
18692
+ 400: {
18693
+ headers: {
18694
+ [name: string]: unknown;
18695
+ };
18696
+ content: {
18697
+ /** @example {
18698
+ * "code": "ERROR_NORID_DECLARATION_EXPIRED",
18699
+ * "detail": "The applicant declaration request has expired",
18700
+ * "domain_name": "Additional error context.",
18701
+ * "status": 400,
18702
+ * "title": "Domain Management Error",
18703
+ * "type": "nor-id-declaration-expired"
18704
+ * } */
18705
+ "application/problem+json": components["schemas"]["Problem"];
18706
+ };
18707
+ };
18708
+ /** @description Not Found */
18709
+ 404: {
18710
+ headers: {
18711
+ [name: string]: unknown;
18712
+ };
18713
+ content: {
18714
+ /** @example {
18715
+ * "code": "ERROR_NORID_DECLARATION_NOT_FOUND",
18716
+ * "detail": "Additional error context.",
18717
+ * "status": 404,
18718
+ * "title": "Domain Management Error",
18719
+ * "type": "nor-id-declaration-not-found"
18720
+ * } */
18721
+ "application/problem+json": components["schemas"]["Problem"];
18722
+ };
18723
+ };
18724
+ /** @description Conflict */
18725
+ 409: {
18726
+ headers: {
18727
+ [name: string]: unknown;
18728
+ };
18729
+ content: {
18730
+ /** @example {
18731
+ * "code": "ERROR_NORID_DECLARATION_STATE",
18732
+ * "detail": "The applicant declaration is not in a valid state",
18733
+ * "domain_name": "Additional error context.",
18734
+ * "status": 409,
18735
+ * "title": "Domain Management Error",
18736
+ * "type": "nor-id-declaration-state"
18737
+ * } */
18738
+ "application/problem+json": components["schemas"]["Problem"];
18739
+ };
18740
+ };
18741
+ /** @description Validation Error */
18742
+ 422: {
18743
+ headers: {
18744
+ [name: string]: unknown;
18745
+ };
18746
+ content: {
18747
+ "application/problem+json": components["schemas"]["HTTPValidationError"];
18748
+ };
18749
+ };
18750
+ };
18751
+ };
18752
+ submit_norid_declaration_v1_domains_tld_specific_no__domain_reference__applicant_declaration_post: {
18753
+ parameters: {
18754
+ query?: never;
18755
+ header?: {
18756
+ /**
18757
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18758
+ * @example rfc3339
18759
+ */
18760
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18761
+ };
18762
+ path: {
18763
+ domain_reference: TypeId<"domain"> | string;
18764
+ };
18765
+ cookie?: never;
18766
+ };
18767
+ requestBody: {
18768
+ content: {
18769
+ "application/json": components["schemas"]["NorIdResellerDeclarationRequest"];
18770
+ };
18771
+ };
18772
+ responses: {
18773
+ /** @description Successful Response */
18774
+ 202: {
18775
+ headers: {
18776
+ [name: string]: unknown;
18777
+ };
18778
+ content: {
18779
+ "application/json": components["schemas"]["NorIdDeclarationResponse"];
18780
+ };
18781
+ };
18782
+ /** @description Bad Request */
18783
+ 400: {
18784
+ headers: {
18785
+ [name: string]: unknown;
18786
+ };
18787
+ content: {
18788
+ /** @example {
18789
+ * "code": "ERROR_NORID_DECLARATION_EXPIRED",
18790
+ * "detail": "The applicant declaration request has expired",
18791
+ * "domain_name": "Additional error context.",
18792
+ * "status": 400,
18793
+ * "title": "Domain Management Error",
18794
+ * "type": "nor-id-declaration-expired"
18795
+ * } */
18796
+ "application/problem+json": components["schemas"]["Problem"];
18797
+ };
18798
+ };
18799
+ /** @description Not Found */
18800
+ 404: {
18801
+ headers: {
18802
+ [name: string]: unknown;
18803
+ };
18804
+ content: {
18805
+ "application/problem+json": components["schemas"]["Problem"];
18806
+ };
18807
+ };
18808
+ /** @description Conflict */
18809
+ 409: {
18810
+ headers: {
18811
+ [name: string]: unknown;
18812
+ };
18813
+ content: {
18814
+ /** @example {
18815
+ * "code": "ERROR_NORID_DECLARATION_STATE",
18816
+ * "detail": "The applicant declaration is not in a valid state",
18817
+ * "domain_name": "Additional error context.",
18818
+ * "status": 409,
18819
+ * "title": "Domain Management Error",
18820
+ * "type": "nor-id-declaration-state"
18821
+ * } */
18822
+ "application/problem+json": components["schemas"]["Problem"];
18823
+ };
18824
+ };
18825
+ /** @description Validation Error */
18826
+ 422: {
18827
+ headers: {
18828
+ [name: string]: unknown;
18829
+ };
18830
+ content: {
18831
+ "application/problem+json": components["schemas"]["HTTPValidationError"];
18832
+ };
18833
+ };
18834
+ };
18835
+ };
18836
+ resend_norid_declaration_email_v1_domains_tld_specific_no__domain_reference__resend_declaration_email_post: {
18837
+ parameters: {
18838
+ query?: never;
18839
+ header?: {
18840
+ /**
18841
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18842
+ * @example rfc3339
18843
+ */
18844
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18845
+ };
18846
+ path: {
18847
+ domain_reference: TypeId<"domain"> | string;
18848
+ };
18849
+ cookie?: never;
18850
+ };
18851
+ requestBody?: never;
18852
+ responses: {
18853
+ /** @description Successful Response */
18854
+ 204: {
18855
+ headers: {
18856
+ [name: string]: unknown;
18857
+ };
18858
+ content?: never;
18859
+ };
18860
+ /** @description Not Found */
18861
+ 404: {
18862
+ headers: {
18863
+ [name: string]: unknown;
18864
+ };
18865
+ content: {
18866
+ "application/problem+json": components["schemas"]["Problem"];
18867
+ };
18868
+ };
18869
+ /** @description Conflict */
18870
+ 409: {
18871
+ headers: {
18872
+ [name: string]: unknown;
18873
+ };
18874
+ content: {
18875
+ /** @example {
18876
+ * "code": "ERROR_NORID_DECLARATION_STATE",
18877
+ * "detail": "The applicant declaration is not in a valid state",
18878
+ * "domain_name": "Additional error context.",
18879
+ * "status": 409,
18880
+ * "title": "Domain Management Error",
18881
+ * "type": "nor-id-declaration-state"
18882
+ * } */
18883
+ "application/problem+json": components["schemas"]["Problem"];
18884
+ };
18885
+ };
18886
+ /** @description Validation Error */
18887
+ 422: {
18888
+ headers: {
18889
+ [name: string]: unknown;
18890
+ };
18891
+ content: {
18892
+ "application/problem+json": components["schemas"]["HTTPValidationError"];
18893
+ };
18894
+ };
18895
+ };
18896
+ };
17930
18897
  transfer_domain_v1_domains_transfer_post: {
17931
18898
  parameters: {
17932
18899
  query?: never;
17933
- header?: never;
18900
+ header?: {
18901
+ /**
18902
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
18903
+ * @example rfc3339
18904
+ */
18905
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
18906
+ };
17934
18907
  path?: never;
17935
18908
  cookie?: never;
17936
18909
  };
@@ -18026,7 +18999,13 @@ export interface operations {
18026
18999
  /** @description Include additional data in the response. */
18027
19000
  include?: components["schemas"]["DomainIncludeField"][] | null;
18028
19001
  };
18029
- header?: never;
19002
+ header?: {
19003
+ /**
19004
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19005
+ * @example rfc3339
19006
+ */
19007
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19008
+ };
18030
19009
  path: {
18031
19010
  domain_reference: TypeId<"domain"> | string;
18032
19011
  };
@@ -18074,7 +19053,13 @@ export interface operations {
18074
19053
  delete_domain_v1_domains__domain_reference__delete: {
18075
19054
  parameters: {
18076
19055
  query?: never;
18077
- header?: never;
19056
+ header?: {
19057
+ /**
19058
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19059
+ * @example rfc3339
19060
+ */
19061
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19062
+ };
18078
19063
  path: {
18079
19064
  domain_reference: TypeId<"domain"> | string;
18080
19065
  };
@@ -18138,7 +19123,13 @@ export interface operations {
18138
19123
  update_domain_v1_domains__domain_reference__patch: {
18139
19124
  parameters: {
18140
19125
  query?: never;
18141
- header?: never;
19126
+ header?: {
19127
+ /**
19128
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19129
+ * @example rfc3339
19130
+ */
19131
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19132
+ };
18142
19133
  path: {
18143
19134
  domain_reference: TypeId<"domain"> | string;
18144
19135
  };
@@ -18182,7 +19173,13 @@ export interface operations {
18182
19173
  get_dnssec_v1_domains__domain_reference__dnssec_get: {
18183
19174
  parameters: {
18184
19175
  query?: never;
18185
- header?: never;
19176
+ header?: {
19177
+ /**
19178
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19179
+ * @example rfc3339
19180
+ */
19181
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19182
+ };
18186
19183
  path: {
18187
19184
  domain_reference: TypeId<"domain"> | string;
18188
19185
  };
@@ -18230,7 +19227,13 @@ export interface operations {
18230
19227
  create_or_update_dnssec_v1_domains__domain_reference__dnssec_put: {
18231
19228
  parameters: {
18232
19229
  query?: never;
18233
- header?: never;
19230
+ header?: {
19231
+ /**
19232
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19233
+ * @example rfc3339
19234
+ */
19235
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19236
+ };
18234
19237
  path: {
18235
19238
  domain_reference: TypeId<"domain"> | string;
18236
19239
  };
@@ -18289,7 +19292,13 @@ export interface operations {
18289
19292
  delete_dnssec_v1_domains__domain_reference__dnssec_delete: {
18290
19293
  parameters: {
18291
19294
  query?: never;
18292
- header?: never;
19295
+ header?: {
19296
+ /**
19297
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19298
+ * @example rfc3339
19299
+ */
19300
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19301
+ };
18293
19302
  path: {
18294
19303
  domain_reference: TypeId<"domain"> | string;
18295
19304
  };
@@ -18335,7 +19344,13 @@ export interface operations {
18335
19344
  disable_and_unpublish_dnssec_records_v1_domains__domain_reference__dnssec_disable_post: {
18336
19345
  parameters: {
18337
19346
  query?: never;
18338
- header?: never;
19347
+ header?: {
19348
+ /**
19349
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19350
+ * @example rfc3339
19351
+ */
19352
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19353
+ };
18339
19354
  path: {
18340
19355
  domain_reference: TypeId<"domain"> | string;
18341
19356
  };
@@ -18381,7 +19396,13 @@ export interface operations {
18381
19396
  enable_and_publish_dnssec_records_v1_domains__domain_reference__dnssec_enable_post: {
18382
19397
  parameters: {
18383
19398
  query?: never;
18384
- header?: never;
19399
+ header?: {
19400
+ /**
19401
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19402
+ * @example rfc3339
19403
+ */
19404
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19405
+ };
18385
19406
  path: {
18386
19407
  domain_reference: TypeId<"domain"> | string;
18387
19408
  };
@@ -18429,7 +19450,13 @@ export interface operations {
18429
19450
  renew_domain_v1_domains__domain_reference__renew_post: {
18430
19451
  parameters: {
18431
19452
  query?: never;
18432
- header?: never;
19453
+ header?: {
19454
+ /**
19455
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19456
+ * @example rfc3339
19457
+ */
19458
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19459
+ };
18433
19460
  path: {
18434
19461
  domain_reference: TypeId<"domain"> | string;
18435
19462
  };
@@ -18464,7 +19491,13 @@ export interface operations {
18464
19491
  restore_domain_v1_domains__domain_reference__restore_post: {
18465
19492
  parameters: {
18466
19493
  query?: never;
18467
- header?: never;
19494
+ header?: {
19495
+ /**
19496
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19497
+ * @example rfc3339
19498
+ */
19499
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19500
+ };
18468
19501
  path: {
18469
19502
  domain_reference: TypeId<"domain"> | string;
18470
19503
  };
@@ -18499,7 +19532,13 @@ export interface operations {
18499
19532
  cancel_domain_transfer_v1_domains__domain_reference__transfer_delete: {
18500
19533
  parameters: {
18501
19534
  query?: never;
18502
- header?: never;
19535
+ header?: {
19536
+ /**
19537
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19538
+ * @example rfc3339
19539
+ */
19540
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19541
+ };
18503
19542
  path: {
18504
19543
  domain_reference: TypeId<"domain"> | string;
18505
19544
  };
@@ -18570,7 +19609,13 @@ export interface operations {
18570
19609
  sort_by?: components["schemas"]["EmailForwardSortField"];
18571
19610
  sort_order?: components["schemas"]["SortOrder"];
18572
19611
  };
18573
- header?: never;
19612
+ header?: {
19613
+ /**
19614
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19615
+ * @example rfc3339
19616
+ */
19617
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19618
+ };
18574
19619
  path?: never;
18575
19620
  cookie?: never;
18576
19621
  };
@@ -18631,7 +19676,13 @@ export interface operations {
18631
19676
  create_email_forward_v1_email_forwards_post: {
18632
19677
  parameters: {
18633
19678
  query?: never;
18634
- header?: never;
19679
+ header?: {
19680
+ /**
19681
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19682
+ * @example rfc3339
19683
+ */
19684
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19685
+ };
18635
19686
  path?: never;
18636
19687
  cookie?: never;
18637
19688
  };
@@ -18729,7 +19780,13 @@ export interface operations {
18729
19780
  get_email_forward_v1_email_forwards__email_forward_id__get: {
18730
19781
  parameters: {
18731
19782
  query?: never;
18732
- header?: never;
19783
+ header?: {
19784
+ /**
19785
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19786
+ * @example rfc3339
19787
+ */
19788
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19789
+ };
18733
19790
  path: {
18734
19791
  email_forward_id: TypeId<"email_forward">;
18735
19792
  };
@@ -18808,7 +19865,13 @@ export interface operations {
18808
19865
  delete_email_forward_v1_email_forwards__email_forward_id__delete: {
18809
19866
  parameters: {
18810
19867
  query?: never;
18811
- header?: never;
19868
+ header?: {
19869
+ /**
19870
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19871
+ * @example rfc3339
19872
+ */
19873
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19874
+ };
18812
19875
  path: {
18813
19876
  email_forward_id: TypeId<"email_forward">;
18814
19877
  };
@@ -18869,7 +19932,13 @@ export interface operations {
18869
19932
  create_email_forward_alias_v1_email_forwards__email_forward_id__aliases_post: {
18870
19933
  parameters: {
18871
19934
  query?: never;
18872
- header?: never;
19935
+ header?: {
19936
+ /**
19937
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
19938
+ * @example rfc3339
19939
+ */
19940
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
19941
+ };
18873
19942
  path: {
18874
19943
  email_forward_id: TypeId<"email_forward">;
18875
19944
  };
@@ -18968,7 +20037,13 @@ export interface operations {
18968
20037
  update_email_forward_alias_v1_email_forwards__email_forward_id__aliases__alias_id__put: {
18969
20038
  parameters: {
18970
20039
  query?: never;
18971
- header?: never;
20040
+ header?: {
20041
+ /**
20042
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20043
+ * @example rfc3339
20044
+ */
20045
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20046
+ };
18972
20047
  path: {
18973
20048
  email_forward_id: TypeId<"email_forward">;
18974
20049
  alias_id: TypeId<"email_forward_alias">;
@@ -19053,7 +20128,13 @@ export interface operations {
19053
20128
  delete_email_forward_alias_v1_email_forwards__email_forward_id__aliases__alias_id__delete: {
19054
20129
  parameters: {
19055
20130
  query?: never;
19056
- header?: never;
20131
+ header?: {
20132
+ /**
20133
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20134
+ * @example rfc3339
20135
+ */
20136
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20137
+ };
19057
20138
  path: {
19058
20139
  email_forward_id: TypeId<"email_forward">;
19059
20140
  alias_id: TypeId<"email_forward_alias">;
@@ -19132,7 +20213,13 @@ export interface operations {
19132
20213
  disable_email_forward_v1_email_forwards__email_forward_id__disable_patch: {
19133
20214
  parameters: {
19134
20215
  query?: never;
19135
- header?: never;
20216
+ header?: {
20217
+ /**
20218
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20219
+ * @example rfc3339
20220
+ */
20221
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20222
+ };
19136
20223
  path: {
19137
20224
  email_forward_id: TypeId<"email_forward">;
19138
20225
  };
@@ -19209,7 +20296,13 @@ export interface operations {
19209
20296
  enable_email_forward_v1_email_forwards__email_forward_id__enable_patch: {
19210
20297
  parameters: {
19211
20298
  query?: never;
19212
- header?: never;
20299
+ header?: {
20300
+ /**
20301
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20302
+ * @example rfc3339
20303
+ */
20304
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20305
+ };
19213
20306
  path: {
19214
20307
  email_forward_id: TypeId<"email_forward">;
19215
20308
  };
@@ -19289,7 +20382,13 @@ export interface operations {
19289
20382
  start_time?: Date | null;
19290
20383
  end_time?: Date | null;
19291
20384
  };
19292
- header?: never;
20385
+ header?: {
20386
+ /**
20387
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20388
+ * @example rfc3339
20389
+ */
20390
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20391
+ };
19293
20392
  path: {
19294
20393
  email_forward_id: TypeId<"email_forward">;
19295
20394
  };
@@ -19378,7 +20477,13 @@ export interface operations {
19378
20477
  subtype?: components["schemas"]["EventSubtype"] | null;
19379
20478
  acknowledged?: boolean | null;
19380
20479
  };
19381
- header?: never;
20480
+ header?: {
20481
+ /**
20482
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20483
+ * @example rfc3339
20484
+ */
20485
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20486
+ };
19382
20487
  path?: never;
19383
20488
  cookie?: never;
19384
20489
  };
@@ -19423,7 +20528,13 @@ export interface operations {
19423
20528
  get_event_v1_events__event_id__get: {
19424
20529
  parameters: {
19425
20530
  query?: never;
19426
- header?: never;
20531
+ header?: {
20532
+ /**
20533
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20534
+ * @example rfc3339
20535
+ */
20536
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20537
+ };
19427
20538
  path: {
19428
20539
  event_id: TypeId<"event">;
19429
20540
  };
@@ -19487,7 +20598,13 @@ export interface operations {
19487
20598
  acknowledge_event_v1_events__event_id__patch: {
19488
20599
  parameters: {
19489
20600
  query?: never;
19490
- header?: never;
20601
+ header?: {
20602
+ /**
20603
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20604
+ * @example rfc3339
20605
+ */
20606
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20607
+ };
19491
20608
  path: {
19492
20609
  event_id: TypeId<"event">;
19493
20610
  };
@@ -19549,7 +20666,13 @@ export interface operations {
19549
20666
  create_host_v1_hosts_post: {
19550
20667
  parameters: {
19551
20668
  query?: never;
19552
- 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
+ };
19553
20676
  path?: never;
19554
20677
  cookie?: never;
19555
20678
  };
@@ -19657,7 +20780,13 @@ export interface operations {
19657
20780
  get_host_v1_hosts__host_reference__get: {
19658
20781
  parameters: {
19659
20782
  query?: never;
19660
- header?: never;
20783
+ header?: {
20784
+ /**
20785
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20786
+ * @example rfc3339
20787
+ */
20788
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20789
+ };
19661
20790
  path: {
19662
20791
  host_reference: TypeId<"host"> | string;
19663
20792
  };
@@ -19729,7 +20858,13 @@ export interface operations {
19729
20858
  update_host_v1_hosts__host_reference__put: {
19730
20859
  parameters: {
19731
20860
  query?: never;
19732
- header?: never;
20861
+ header?: {
20862
+ /**
20863
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20864
+ * @example rfc3339
20865
+ */
20866
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20867
+ };
19733
20868
  path: {
19734
20869
  host_reference: TypeId<"host"> | string;
19735
20870
  };
@@ -19805,7 +20940,13 @@ export interface operations {
19805
20940
  delete_host_v1_hosts__host_reference__delete: {
19806
20941
  parameters: {
19807
20942
  query?: never;
19808
- header?: never;
20943
+ header?: {
20944
+ /**
20945
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
20946
+ * @example rfc3339
20947
+ */
20948
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
20949
+ };
19809
20950
  path: {
19810
20951
  host_reference: TypeId<"host"> | string;
19811
20952
  };
@@ -19892,7 +21033,13 @@ export interface operations {
19892
21033
  get_job_v1_job__job_id__get: {
19893
21034
  parameters: {
19894
21035
  query?: never;
19895
- header?: never;
21036
+ header?: {
21037
+ /**
21038
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21039
+ * @example rfc3339
21040
+ */
21041
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21042
+ };
19896
21043
  path: {
19897
21044
  /** @description Job ID */
19898
21045
  job_id: TypeId<"job">;
@@ -19941,7 +21088,13 @@ export interface operations {
19941
21088
  delete_job_v1_job__job_id__delete: {
19942
21089
  parameters: {
19943
21090
  query?: never;
19944
- 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
+ };
19945
21098
  path: {
19946
21099
  /** @description Job ID */
19947
21100
  job_id: TypeId<"job">;
@@ -19988,7 +21141,13 @@ export interface operations {
19988
21141
  pause_job_v1_job__job_id__pause_post: {
19989
21142
  parameters: {
19990
21143
  query?: never;
19991
- header?: never;
21144
+ header?: {
21145
+ /**
21146
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21147
+ * @example rfc3339
21148
+ */
21149
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21150
+ };
19992
21151
  path: {
19993
21152
  /** @description Job ID */
19994
21153
  job_id: TypeId<"job">;
@@ -20035,7 +21194,13 @@ export interface operations {
20035
21194
  resume_job_v1_job__job_id__resume_post: {
20036
21195
  parameters: {
20037
21196
  query?: never;
20038
- header?: never;
21197
+ header?: {
21198
+ /**
21199
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21200
+ * @example rfc3339
21201
+ */
21202
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21203
+ };
20039
21204
  path: {
20040
21205
  /** @description Job ID */
20041
21206
  job_id: TypeId<"job">;
@@ -20084,7 +21249,13 @@ export interface operations {
20084
21249
  retry_job_v1_job__job_id__retry_post: {
20085
21250
  parameters: {
20086
21251
  query?: never;
20087
- header?: never;
21252
+ header?: {
21253
+ /**
21254
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21255
+ * @example rfc3339
21256
+ */
21257
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21258
+ };
20088
21259
  path: {
20089
21260
  /** @description Job ID */
20090
21261
  job_id: TypeId<"job">;
@@ -20160,7 +21331,13 @@ export interface operations {
20160
21331
  /** @description Number of batches per page */
20161
21332
  page_size?: number;
20162
21333
  };
20163
- header?: never;
21334
+ header?: {
21335
+ /**
21336
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21337
+ * @example rfc3339
21338
+ */
21339
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21340
+ };
20164
21341
  path?: never;
20165
21342
  cookie?: never;
20166
21343
  };
@@ -20189,7 +21366,13 @@ export interface operations {
20189
21366
  create_batch_v1_jobs_post: {
20190
21367
  parameters: {
20191
21368
  query?: never;
20192
- header?: never;
21369
+ header?: {
21370
+ /**
21371
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21372
+ * @example rfc3339
21373
+ */
21374
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21375
+ };
20193
21376
  path?: never;
20194
21377
  cookie?: never;
20195
21378
  };
@@ -20255,7 +21438,13 @@ export interface operations {
20255
21438
  get_batch_v1_jobs__batch_id__get: {
20256
21439
  parameters: {
20257
21440
  query?: never;
20258
- header?: never;
21441
+ header?: {
21442
+ /**
21443
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21444
+ * @example rfc3339
21445
+ */
21446
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21447
+ };
20259
21448
  path: {
20260
21449
  /** @description Batch ID */
20261
21450
  batch_id: TypeId<"batch">;
@@ -20321,7 +21510,13 @@ export interface operations {
20321
21510
  delete_batch_v1_jobs__batch_id__delete: {
20322
21511
  parameters: {
20323
21512
  query?: never;
20324
- header?: never;
21513
+ header?: {
21514
+ /**
21515
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21516
+ * @example rfc3339
21517
+ */
21518
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21519
+ };
20325
21520
  path: {
20326
21521
  /** @description Batch ID */
20327
21522
  batch_id: TypeId<"batch">;
@@ -20379,7 +21574,13 @@ export interface operations {
20379
21574
  /** @description Number of jobs per page */
20380
21575
  page_size?: number;
20381
21576
  };
20382
- header?: never;
21577
+ header?: {
21578
+ /**
21579
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21580
+ * @example rfc3339
21581
+ */
21582
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21583
+ };
20383
21584
  path: {
20384
21585
  /** @description Batch ID */
20385
21586
  batch_id: TypeId<"batch">;
@@ -20445,7 +21646,13 @@ export interface operations {
20445
21646
  pause_batch_v1_jobs__batch_id__pause_post: {
20446
21647
  parameters: {
20447
21648
  query?: never;
20448
- header?: never;
21649
+ header?: {
21650
+ /**
21651
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21652
+ * @example rfc3339
21653
+ */
21654
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21655
+ };
20449
21656
  path: {
20450
21657
  /** @description Batch ID */
20451
21658
  batch_id: TypeId<"batch">;
@@ -20492,7 +21699,13 @@ export interface operations {
20492
21699
  resume_batch_v1_jobs__batch_id__resume_post: {
20493
21700
  parameters: {
20494
21701
  query?: never;
20495
- header?: never;
21702
+ header?: {
21703
+ /**
21704
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21705
+ * @example rfc3339
21706
+ */
21707
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21708
+ };
20496
21709
  path: {
20497
21710
  /** @description Batch ID */
20498
21711
  batch_id: TypeId<"batch">;
@@ -20542,7 +21755,13 @@ export interface operations {
20542
21755
  /** @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
21756
  error_class?: string[] | null;
20544
21757
  };
20545
- header?: never;
21758
+ header?: {
21759
+ /**
21760
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21761
+ * @example rfc3339
21762
+ */
21763
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21764
+ };
20546
21765
  path: {
20547
21766
  /** @description Batch ID */
20548
21767
  batch_id: TypeId<"batch">;
@@ -20598,7 +21817,13 @@ export interface operations {
20598
21817
  search?: string | null;
20599
21818
  country_code?: string | null;
20600
21819
  };
20601
- header?: never;
21820
+ header?: {
21821
+ /**
21822
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21823
+ * @example rfc3339
21824
+ */
21825
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21826
+ };
20602
21827
  path?: never;
20603
21828
  cookie?: never;
20604
21829
  };
@@ -20659,7 +21884,13 @@ export interface operations {
20659
21884
  create_organization_v1_organizations_post: {
20660
21885
  parameters: {
20661
21886
  query?: never;
20662
- header?: never;
21887
+ header?: {
21888
+ /**
21889
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21890
+ * @example rfc3339
21891
+ */
21892
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21893
+ };
20663
21894
  path?: never;
20664
21895
  cookie?: never;
20665
21896
  };
@@ -20734,7 +21965,13 @@ export interface operations {
20734
21965
  /** @description Optional list of attribute keys to filter */
20735
21966
  keys?: string[] | null;
20736
21967
  };
20737
- header?: never;
21968
+ header?: {
21969
+ /**
21970
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
21971
+ * @example rfc3339
21972
+ */
21973
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
21974
+ };
20738
21975
  path?: never;
20739
21976
  cookie?: never;
20740
21977
  };
@@ -20795,7 +22032,13 @@ export interface operations {
20795
22032
  update_current_organization_attributes_v1_organizations_attributes_patch: {
20796
22033
  parameters: {
20797
22034
  query?: never;
20798
- header?: never;
22035
+ header?: {
22036
+ /**
22037
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22038
+ * @example rfc3339
22039
+ */
22040
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22041
+ };
20799
22042
  path?: never;
20800
22043
  cookie?: never;
20801
22044
  };
@@ -20860,7 +22103,13 @@ export interface operations {
20860
22103
  list_ip_restrictions_v1_organizations_ip_restrictions_get: {
20861
22104
  parameters: {
20862
22105
  query?: never;
20863
- header?: never;
22106
+ header?: {
22107
+ /**
22108
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22109
+ * @example rfc3339
22110
+ */
22111
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22112
+ };
20864
22113
  path?: never;
20865
22114
  cookie?: never;
20866
22115
  };
@@ -20921,7 +22170,13 @@ export interface operations {
20921
22170
  create_ip_restriction_v1_organizations_ip_restrictions_post: {
20922
22171
  parameters: {
20923
22172
  query?: never;
20924
- header?: never;
22173
+ header?: {
22174
+ /**
22175
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22176
+ * @example rfc3339
22177
+ */
22178
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22179
+ };
20925
22180
  path?: never;
20926
22181
  cookie?: never;
20927
22182
  };
@@ -20986,7 +22241,13 @@ export interface operations {
20986
22241
  get_ip_restriction_v1_organizations_ip_restrictions__ip_restriction_id__get: {
20987
22242
  parameters: {
20988
22243
  query?: never;
20989
- header?: never;
22244
+ header?: {
22245
+ /**
22246
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22247
+ * @example rfc3339
22248
+ */
22249
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22250
+ };
20990
22251
  path: {
20991
22252
  ip_restriction_id: number;
20992
22253
  };
@@ -21049,7 +22310,13 @@ export interface operations {
21049
22310
  delete_ip_restriction_v1_organizations_ip_restrictions__ip_restriction_id__delete: {
21050
22311
  parameters: {
21051
22312
  query?: never;
21052
- header?: never;
22313
+ header?: {
22314
+ /**
22315
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22316
+ * @example rfc3339
22317
+ */
22318
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22319
+ };
21053
22320
  path: {
21054
22321
  ip_restriction_id: number;
21055
22322
  };
@@ -21110,7 +22377,13 @@ export interface operations {
21110
22377
  update_ip_restriction_v1_organizations_ip_restrictions__ip_restriction_id__patch: {
21111
22378
  parameters: {
21112
22379
  query?: never;
21113
- header?: never;
22380
+ header?: {
22381
+ /**
22382
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22383
+ * @example rfc3339
22384
+ */
22385
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22386
+ };
21114
22387
  path: {
21115
22388
  ip_restriction_id: number;
21116
22389
  };
@@ -21177,7 +22450,13 @@ export interface operations {
21177
22450
  list_role_permissions_v1_organizations_role_permissions_get: {
21178
22451
  parameters: {
21179
22452
  query?: never;
21180
- header?: never;
22453
+ header?: {
22454
+ /**
22455
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22456
+ * @example rfc3339
22457
+ */
22458
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22459
+ };
21181
22460
  path?: never;
21182
22461
  cookie?: never;
21183
22462
  };
@@ -21238,7 +22517,13 @@ export interface operations {
21238
22517
  list_roles_v1_organizations_roles_get: {
21239
22518
  parameters: {
21240
22519
  query?: never;
21241
- header?: never;
22520
+ header?: {
22521
+ /**
22522
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22523
+ * @example rfc3339
22524
+ */
22525
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22526
+ };
21242
22527
  path?: never;
21243
22528
  cookie?: never;
21244
22529
  };
@@ -21299,7 +22584,13 @@ export interface operations {
21299
22584
  create_role_v1_organizations_roles_post: {
21300
22585
  parameters: {
21301
22586
  query?: never;
21302
- header?: never;
22587
+ header?: {
22588
+ /**
22589
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22590
+ * @example rfc3339
22591
+ */
22592
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22593
+ };
21303
22594
  path?: never;
21304
22595
  cookie?: never;
21305
22596
  };
@@ -21380,7 +22671,13 @@ export interface operations {
21380
22671
  get_role_v1_organizations_roles__label__get: {
21381
22672
  parameters: {
21382
22673
  query?: never;
21383
- header?: never;
22674
+ header?: {
22675
+ /**
22676
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22677
+ * @example rfc3339
22678
+ */
22679
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22680
+ };
21384
22681
  path: {
21385
22682
  label: string;
21386
22683
  };
@@ -21460,7 +22757,13 @@ export interface operations {
21460
22757
  delete_role_v1_organizations_roles__label__delete: {
21461
22758
  parameters: {
21462
22759
  query?: never;
21463
- header?: never;
22760
+ header?: {
22761
+ /**
22762
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22763
+ * @example rfc3339
22764
+ */
22765
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22766
+ };
21464
22767
  path: {
21465
22768
  label: string;
21466
22769
  };
@@ -21556,7 +22859,13 @@ export interface operations {
21556
22859
  update_role_v1_organizations_roles__label__patch: {
21557
22860
  parameters: {
21558
22861
  query?: never;
21559
- header?: never;
22862
+ header?: {
22863
+ /**
22864
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22865
+ * @example rfc3339
22866
+ */
22867
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22868
+ };
21560
22869
  path: {
21561
22870
  label: string;
21562
22871
  };
@@ -21663,7 +22972,13 @@ export interface operations {
21663
22972
  sort_order?: components["schemas"]["SortOrder"];
21664
22973
  search?: string | null;
21665
22974
  };
21666
- header?: never;
22975
+ header?: {
22976
+ /**
22977
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
22978
+ * @example rfc3339
22979
+ */
22980
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
22981
+ };
21667
22982
  path?: never;
21668
22983
  cookie?: never;
21669
22984
  };
@@ -21724,7 +23039,13 @@ export interface operations {
21724
23039
  get_organization_v1_organizations__organization_id__get: {
21725
23040
  parameters: {
21726
23041
  query?: never;
21727
- header?: never;
23042
+ header?: {
23043
+ /**
23044
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23045
+ * @example rfc3339
23046
+ */
23047
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23048
+ };
21728
23049
  path: {
21729
23050
  organization_id: TypeId<"organization">;
21730
23051
  };
@@ -21787,7 +23108,13 @@ export interface operations {
21787
23108
  delete_organization_v1_organizations__organization_id__delete: {
21788
23109
  parameters: {
21789
23110
  query?: never;
21790
- header?: never;
23111
+ header?: {
23112
+ /**
23113
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23114
+ * @example rfc3339
23115
+ */
23116
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23117
+ };
21791
23118
  path: {
21792
23119
  organization_id: TypeId<"organization">;
21793
23120
  };
@@ -21848,7 +23175,13 @@ export interface operations {
21848
23175
  update_organization_v1_organizations__organization_id__patch: {
21849
23176
  parameters: {
21850
23177
  query?: never;
21851
- header?: never;
23178
+ header?: {
23179
+ /**
23180
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23181
+ * @example rfc3339
23182
+ */
23183
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23184
+ };
21852
23185
  path: {
21853
23186
  organization_id: TypeId<"organization">;
21854
23187
  };
@@ -21918,7 +23251,13 @@ export interface operations {
21918
23251
  /** @description Optional list of attribute keys to filter */
21919
23252
  keys?: string[] | null;
21920
23253
  };
21921
- header?: never;
23254
+ header?: {
23255
+ /**
23256
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23257
+ * @example rfc3339
23258
+ */
23259
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23260
+ };
21922
23261
  path: {
21923
23262
  organization_id: TypeId<"organization">;
21924
23263
  };
@@ -21981,7 +23320,13 @@ export interface operations {
21981
23320
  update_organization_attributes_v1_organizations__organization_id__attributes_patch: {
21982
23321
  parameters: {
21983
23322
  query?: never;
21984
- header?: never;
23323
+ header?: {
23324
+ /**
23325
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23326
+ * @example rfc3339
23327
+ */
23328
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23329
+ };
21985
23330
  path: {
21986
23331
  organization_id: TypeId<"organization">;
21987
23332
  };
@@ -22051,7 +23396,13 @@ export interface operations {
22051
23396
  page?: number;
22052
23397
  page_size?: number;
22053
23398
  };
22054
- header?: never;
23399
+ header?: {
23400
+ /**
23401
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23402
+ * @example rfc3339
23403
+ */
23404
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23405
+ };
22055
23406
  path: {
22056
23407
  organization_id: TypeId<"organization">;
22057
23408
  };
@@ -22085,7 +23436,13 @@ export interface operations {
22085
23436
  product_action?: components["schemas"]["BillingTransactionAction"] | null;
22086
23437
  product_class?: string | null;
22087
23438
  };
22088
- header?: never;
23439
+ header?: {
23440
+ /**
23441
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23442
+ * @example rfc3339
23443
+ */
23444
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23445
+ };
22089
23446
  path: {
22090
23447
  organization_id: TypeId<"organization">;
22091
23448
  product_type: components["schemas"]["BillingTransactionProductType"];
@@ -22162,7 +23519,13 @@ export interface operations {
22162
23519
  completed_after?: Date | null;
22163
23520
  completed_before?: Date | null;
22164
23521
  };
22165
- header?: never;
23522
+ header?: {
23523
+ /**
23524
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23525
+ * @example rfc3339
23526
+ */
23527
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23528
+ };
22166
23529
  path: {
22167
23530
  organization_id: TypeId<"organization">;
22168
23531
  };
@@ -22225,7 +23588,13 @@ export interface operations {
22225
23588
  get_transaction_v1_organizations__organization_id__transactions__transaction_id__get: {
22226
23589
  parameters: {
22227
23590
  query?: never;
22228
- header?: never;
23591
+ header?: {
23592
+ /**
23593
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23594
+ * @example rfc3339
23595
+ */
23596
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23597
+ };
22229
23598
  path: {
22230
23599
  organization_id: TypeId<"organization">;
22231
23600
  transaction_id: TypeId<"billing_transaction">;
@@ -22299,7 +23668,13 @@ export interface operations {
22299
23668
  enabled?: boolean | null;
22300
23669
  compliance_status?: components["schemas"]["ComplianceStatus"] | null;
22301
23670
  };
22302
- header?: never;
23671
+ header?: {
23672
+ /**
23673
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23674
+ * @example rfc3339
23675
+ */
23676
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23677
+ };
22303
23678
  path?: never;
22304
23679
  cookie?: never;
22305
23680
  };
@@ -22363,7 +23738,13 @@ export interface operations {
22363
23738
  start_time?: Date | null;
22364
23739
  end_time?: Date | null;
22365
23740
  };
22366
- header?: never;
23741
+ header?: {
23742
+ /**
23743
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23744
+ * @example rfc3339
23745
+ */
23746
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23747
+ };
22367
23748
  path?: never;
22368
23749
  cookie?: never;
22369
23750
  };
@@ -22424,7 +23805,13 @@ export interface operations {
22424
23805
  signup_for_parking_v1_parking_signup_post: {
22425
23806
  parameters: {
22426
23807
  query?: never;
22427
- header?: never;
23808
+ header?: {
23809
+ /**
23810
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23811
+ * @example rfc3339
23812
+ */
23813
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23814
+ };
22428
23815
  path?: never;
22429
23816
  cookie?: never;
22430
23817
  };
@@ -22489,7 +23876,13 @@ export interface operations {
22489
23876
  get_parking_signup_status_v1_parking_signup_status_get: {
22490
23877
  parameters: {
22491
23878
  query?: never;
22492
- header?: never;
23879
+ header?: {
23880
+ /**
23881
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23882
+ * @example rfc3339
23883
+ */
23884
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23885
+ };
22493
23886
  path?: never;
22494
23887
  cookie?: never;
22495
23888
  };
@@ -22553,7 +23946,13 @@ export interface operations {
22553
23946
  start_time?: Date | null;
22554
23947
  end_time?: Date | null;
22555
23948
  };
22556
- header?: never;
23949
+ header?: {
23950
+ /**
23951
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
23952
+ * @example rfc3339
23953
+ */
23954
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
23955
+ };
22557
23956
  path: {
22558
23957
  parking_reference: TypeId<"parking"> | string;
22559
23958
  };
@@ -22640,7 +24039,13 @@ export interface operations {
22640
24039
  created_after?: Date | null;
22641
24040
  created_before?: Date | null;
22642
24041
  };
22643
- header?: never;
24042
+ header?: {
24043
+ /**
24044
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24045
+ * @example rfc3339
24046
+ */
24047
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24048
+ };
22644
24049
  path?: never;
22645
24050
  cookie?: never;
22646
24051
  };
@@ -22669,7 +24074,13 @@ export interface operations {
22669
24074
  create_report_v1_reports_post: {
22670
24075
  parameters: {
22671
24076
  query?: never;
22672
- header?: never;
24077
+ header?: {
24078
+ /**
24079
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24080
+ * @example rfc3339
24081
+ */
24082
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24083
+ };
22673
24084
  path?: never;
22674
24085
  cookie?: never;
22675
24086
  };
@@ -22702,7 +24113,13 @@ export interface operations {
22702
24113
  get_report_v1_reports__report_id__get: {
22703
24114
  parameters: {
22704
24115
  query?: never;
22705
- header?: never;
24116
+ header?: {
24117
+ /**
24118
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24119
+ * @example rfc3339
24120
+ */
24121
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24122
+ };
22706
24123
  path: {
22707
24124
  report_id: string;
22708
24125
  };
@@ -22733,7 +24150,13 @@ export interface operations {
22733
24150
  download_report_v1_reports__report_id__download_get: {
22734
24151
  parameters: {
22735
24152
  query?: never;
22736
- header?: never;
24153
+ header?: {
24154
+ /**
24155
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24156
+ * @example rfc3339
24157
+ */
24158
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24159
+ };
22737
24160
  path: {
22738
24161
  report_id: string;
22739
24162
  };
@@ -22772,7 +24195,13 @@ export interface operations {
22772
24195
  tag_types?: components["schemas"]["TagType"][] | null;
22773
24196
  search?: string | null;
22774
24197
  };
22775
- header?: never;
24198
+ header?: {
24199
+ /**
24200
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24201
+ * @example rfc3339
24202
+ */
24203
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24204
+ };
22776
24205
  path?: never;
22777
24206
  cookie?: never;
22778
24207
  };
@@ -22817,7 +24246,13 @@ export interface operations {
22817
24246
  create_tag_v1_tags_post: {
22818
24247
  parameters: {
22819
24248
  query?: never;
22820
- header?: never;
24249
+ header?: {
24250
+ /**
24251
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24252
+ * @example rfc3339
24253
+ */
24254
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24255
+ };
22821
24256
  path?: never;
22822
24257
  cookie?: never;
22823
24258
  };
@@ -22883,7 +24318,13 @@ export interface operations {
22883
24318
  bulk_update_object_tags_v1_tags_objects_post: {
22884
24319
  parameters: {
22885
24320
  query?: never;
22886
- header?: never;
24321
+ header?: {
24322
+ /**
24323
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24324
+ * @example rfc3339
24325
+ */
24326
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24327
+ };
22887
24328
  path?: never;
22888
24329
  cookie?: never;
22889
24330
  };
@@ -22966,7 +24407,13 @@ export interface operations {
22966
24407
  get_tag_v1_tags__tag_id__get: {
22967
24408
  parameters: {
22968
24409
  query?: never;
22969
- header?: never;
24410
+ header?: {
24411
+ /**
24412
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24413
+ * @example rfc3339
24414
+ */
24415
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24416
+ };
22970
24417
  path: {
22971
24418
  tag_id: TypeId<"tag">;
22972
24419
  };
@@ -23030,7 +24477,13 @@ export interface operations {
23030
24477
  delete_tag_v1_tags__tag_id__delete: {
23031
24478
  parameters: {
23032
24479
  query?: never;
23033
- header?: never;
24480
+ header?: {
24481
+ /**
24482
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24483
+ * @example rfc3339
24484
+ */
24485
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24486
+ };
23034
24487
  path: {
23035
24488
  tag_id: TypeId<"tag">;
23036
24489
  };
@@ -23092,7 +24545,13 @@ export interface operations {
23092
24545
  update_tag_v1_tags__tag_id__patch: {
23093
24546
  parameters: {
23094
24547
  query?: never;
23095
- header?: never;
24548
+ header?: {
24549
+ /**
24550
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24551
+ * @example rfc3339
24552
+ */
24553
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24554
+ };
23096
24555
  path: {
23097
24556
  tag_id: TypeId<"tag">;
23098
24557
  };
@@ -23177,7 +24636,13 @@ export interface operations {
23177
24636
  update_tag_objects_v1_tags__tag_id__objects_post: {
23178
24637
  parameters: {
23179
24638
  query?: never;
23180
- header?: never;
24639
+ header?: {
24640
+ /**
24641
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24642
+ * @example rfc3339
24643
+ */
24644
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24645
+ };
23181
24646
  path: {
23182
24647
  tag_id: TypeId<"tag">;
23183
24648
  };
@@ -23248,7 +24713,13 @@ export interface operations {
23248
24713
  fields?: string | null;
23249
24714
  tlds?: string | null;
23250
24715
  };
23251
- header?: never;
24716
+ header?: {
24717
+ /**
24718
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24719
+ * @example rfc3339
24720
+ */
24721
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24722
+ };
23252
24723
  path?: never;
23253
24724
  cookie?: never;
23254
24725
  };
@@ -23281,7 +24752,13 @@ export interface operations {
23281
24752
  get_tld_portfolio_v1_tlds_portfolio_get: {
23282
24753
  parameters: {
23283
24754
  query?: never;
23284
- header?: never;
24755
+ header?: {
24756
+ /**
24757
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24758
+ * @example rfc3339
24759
+ */
24760
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24761
+ };
23285
24762
  path?: never;
23286
24763
  cookie?: never;
23287
24764
  };
@@ -23310,7 +24787,13 @@ export interface operations {
23310
24787
  get_tld_spec_v1_tlds__tld__get: {
23311
24788
  parameters: {
23312
24789
  query?: never;
23313
- header?: never;
24790
+ header?: {
24791
+ /**
24792
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24793
+ * @example rfc3339
24794
+ */
24795
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24796
+ };
23314
24797
  path: {
23315
24798
  tld: string;
23316
24799
  };
@@ -23357,7 +24840,13 @@ export interface operations {
23357
24840
  create_user_v1_users_post: {
23358
24841
  parameters: {
23359
24842
  query?: never;
23360
- header?: never;
24843
+ header?: {
24844
+ /**
24845
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24846
+ * @example rfc3339
24847
+ */
24848
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24849
+ };
23361
24850
  path?: never;
23362
24851
  cookie?: never;
23363
24852
  };
@@ -23392,7 +24881,13 @@ export interface operations {
23392
24881
  query?: {
23393
24882
  attributes?: string[] | null;
23394
24883
  };
23395
- header?: never;
24884
+ header?: {
24885
+ /**
24886
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24887
+ * @example rfc3339
24888
+ */
24889
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24890
+ };
23396
24891
  path?: never;
23397
24892
  cookie?: never;
23398
24893
  };
@@ -23423,7 +24918,13 @@ export interface operations {
23423
24918
  query?: {
23424
24919
  attributes?: string[] | null;
23425
24920
  };
23426
- header?: never;
24921
+ header?: {
24922
+ /**
24923
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24924
+ * @example rfc3339
24925
+ */
24926
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24927
+ };
23427
24928
  path: {
23428
24929
  user_id: TypeId<"user">;
23429
24930
  };
@@ -23454,7 +24955,13 @@ export interface operations {
23454
24955
  delete_user_v1_users__user_id__delete: {
23455
24956
  parameters: {
23456
24957
  query?: never;
23457
- header?: never;
24958
+ header?: {
24959
+ /**
24960
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
24961
+ * @example rfc3339
24962
+ */
24963
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
24964
+ };
23458
24965
  path: {
23459
24966
  user_id: TypeId<"user">;
23460
24967
  };
@@ -23492,7 +24999,13 @@ export interface operations {
23492
24999
  update_user_v1_users__user_id__patch: {
23493
25000
  parameters: {
23494
25001
  query?: never;
23495
- header?: never;
25002
+ header?: {
25003
+ /**
25004
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25005
+ * @example rfc3339
25006
+ */
25007
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25008
+ };
23496
25009
  path: {
23497
25010
  user_id: TypeId<"user">;
23498
25011
  };
@@ -23527,7 +25040,13 @@ export interface operations {
23527
25040
  get_user_permissions_v1_users__user_id__permissions_get: {
23528
25041
  parameters: {
23529
25042
  query?: never;
23530
- header?: never;
25043
+ header?: {
25044
+ /**
25045
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25046
+ * @example rfc3339
25047
+ */
25048
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25049
+ };
23531
25050
  path: {
23532
25051
  user_id: TypeId<"user">;
23533
25052
  };
@@ -23558,7 +25077,13 @@ export interface operations {
23558
25077
  get_role_v1_users__user_id__role_get: {
23559
25078
  parameters: {
23560
25079
  query?: never;
23561
- header?: never;
25080
+ header?: {
25081
+ /**
25082
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25083
+ * @example rfc3339
25084
+ */
25085
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25086
+ };
23562
25087
  path: {
23563
25088
  user_id: TypeId<"user">;
23564
25089
  };
@@ -23589,7 +25114,13 @@ export interface operations {
23589
25114
  set_user_role_v1_users__user_id__role_put: {
23590
25115
  parameters: {
23591
25116
  query?: never;
23592
- header?: never;
25117
+ header?: {
25118
+ /**
25119
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25120
+ * @example rfc3339
25121
+ */
25122
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25123
+ };
23593
25124
  path: {
23594
25125
  user_id: TypeId<"user">;
23595
25126
  };
@@ -23660,7 +25191,13 @@ export interface operations {
23660
25191
  page?: number;
23661
25192
  page_size?: number;
23662
25193
  };
23663
- header?: never;
25194
+ header?: {
25195
+ /**
25196
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25197
+ * @example rfc3339
25198
+ */
25199
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25200
+ };
23664
25201
  path?: never;
23665
25202
  cookie?: never;
23666
25203
  };
@@ -23689,7 +25226,13 @@ export interface operations {
23689
25226
  create_vanity_nameserver_set_v1_vanity_nameserver_sets_post: {
23690
25227
  parameters: {
23691
25228
  query?: never;
23692
- header?: never;
25229
+ header?: {
25230
+ /**
25231
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25232
+ * @example rfc3339
25233
+ */
25234
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25235
+ };
23693
25236
  path?: never;
23694
25237
  cookie?: never;
23695
25238
  };
@@ -23722,7 +25265,13 @@ export interface operations {
23722
25265
  check_vanity_nameserver_set_v1_vanity_nameserver_sets_check_post: {
23723
25266
  parameters: {
23724
25267
  query?: never;
23725
- header?: never;
25268
+ header?: {
25269
+ /**
25270
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25271
+ * @example rfc3339
25272
+ */
25273
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25274
+ };
23726
25275
  path?: never;
23727
25276
  cookie?: never;
23728
25277
  };
@@ -23755,7 +25304,13 @@ export interface operations {
23755
25304
  clear_vanity_nameserver_set_default_v1_vanity_nameserver_sets_default_delete: {
23756
25305
  parameters: {
23757
25306
  query?: never;
23758
- header?: never;
25307
+ header?: {
25308
+ /**
25309
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25310
+ * @example rfc3339
25311
+ */
25312
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25313
+ };
23759
25314
  path?: never;
23760
25315
  cookie?: never;
23761
25316
  };
@@ -23784,7 +25339,13 @@ export interface operations {
23784
25339
  get_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__get: {
23785
25340
  parameters: {
23786
25341
  query?: never;
23787
- header?: never;
25342
+ header?: {
25343
+ /**
25344
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25345
+ * @example rfc3339
25346
+ */
25347
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25348
+ };
23788
25349
  path: {
23789
25350
  set_id: TypeId<"vns">;
23790
25351
  };
@@ -23815,7 +25376,13 @@ export interface operations {
23815
25376
  delete_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__delete: {
23816
25377
  parameters: {
23817
25378
  query?: never;
23818
- header?: never;
25379
+ header?: {
25380
+ /**
25381
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25382
+ * @example rfc3339
25383
+ */
25384
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25385
+ };
23819
25386
  path: {
23820
25387
  set_id: TypeId<"vns">;
23821
25388
  };
@@ -23846,7 +25413,13 @@ export interface operations {
23846
25413
  set_vanity_nameserver_set_default_v1_vanity_nameserver_sets__set_id__default_patch: {
23847
25414
  parameters: {
23848
25415
  query?: never;
23849
- header?: never;
25416
+ header?: {
25417
+ /**
25418
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25419
+ * @example rfc3339
25420
+ */
25421
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25422
+ };
23850
25423
  path: {
23851
25424
  set_id: TypeId<"vns">;
23852
25425
  };
@@ -23877,7 +25450,13 @@ export interface operations {
23877
25450
  restore_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__restore_post: {
23878
25451
  parameters: {
23879
25452
  query?: never;
23880
- header?: never;
25453
+ header?: {
25454
+ /**
25455
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25456
+ * @example rfc3339
25457
+ */
25458
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25459
+ };
23881
25460
  path: {
23882
25461
  set_id: TypeId<"vns">;
23883
25462
  };
@@ -23908,7 +25487,13 @@ export interface operations {
23908
25487
  retry_vanity_nameserver_set_v1_vanity_nameserver_sets__set_id__retry_post: {
23909
25488
  parameters: {
23910
25489
  query?: never;
23911
- header?: never;
25490
+ header?: {
25491
+ /**
25492
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25493
+ * @example rfc3339
25494
+ */
25495
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25496
+ };
23912
25497
  path: {
23913
25498
  set_id: TypeId<"vns">;
23914
25499
  };
@@ -23942,7 +25527,13 @@ export interface operations {
23942
25527
  page?: number;
23943
25528
  page_size?: number;
23944
25529
  };
23945
- header?: never;
25530
+ header?: {
25531
+ /**
25532
+ * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
25533
+ * @example rfc3339
25534
+ */
25535
+ "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
25536
+ };
23946
25537
  path: {
23947
25538
  set_id: TypeId<"vns">;
23948
25539
  };