@seamapi/types 1.299.0 → 1.300.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.
@@ -4173,7 +4173,7 @@ export interface Routes {
4173
4173
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
4174
4174
  starts_at: string;
4175
4175
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
4176
- ends_at: string;
4176
+ ends_at: string | null;
4177
4177
  } | undefined;
4178
4178
  /** ID of the user identity associated with the `acs_user`. */
4179
4179
  user_identity_id?: string | undefined;
@@ -7650,10 +7650,10 @@ export interface Routes {
7650
7650
  acs_access_group_ids?: string[];
7651
7651
  /** ID of the user identity with which to associate the new `acs_user`. */
7652
7652
  user_identity_id?: string | undefined;
7653
- /** `starts_at` and `ends_at` timestamps for the new `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. Only applicable to Salto KS access control systems. */
7653
+ /** `starts_at` and `ends_at` timestamps for the new `acs_user`'s access. If you specify an `access_schedule`, you may include both `starts_at` and `ends_at`. `starts_at` defaults to the current time if not provided. `ends_at` is optional and must be a time in the future and after `starts_at`. */
7654
7654
  access_schedule?: {
7655
- starts_at: string;
7656
- ends_at: string;
7655
+ starts_at?: string | undefined;
7656
+ ends_at?: (string | undefined) | null;
7657
7657
  } | undefined;
7658
7658
  /** Full name of the `acs_user`. */
7659
7659
  full_name?: string | undefined;
@@ -7691,7 +7691,7 @@ export interface Routes {
7691
7691
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
7692
7692
  starts_at: string;
7693
7693
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
7694
- ends_at: string;
7694
+ ends_at: string | null;
7695
7695
  } | undefined;
7696
7696
  /** ID of the user identity associated with the `acs_user`. */
7697
7697
  user_identity_id?: string | undefined;
@@ -7806,7 +7806,7 @@ export interface Routes {
7806
7806
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
7807
7807
  starts_at: string;
7808
7808
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
7809
- ends_at: string;
7809
+ ends_at: string | null;
7810
7810
  } | undefined;
7811
7811
  /** ID of the user identity associated with the `acs_user`. */
7812
7812
  user_identity_id?: string | undefined;
@@ -7917,7 +7917,7 @@ export interface Routes {
7917
7917
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
7918
7918
  starts_at: string;
7919
7919
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
7920
- ends_at: string;
7920
+ ends_at: string | null;
7921
7921
  } | undefined;
7922
7922
  /** ID of the user identity associated with the `acs_user`. */
7923
7923
  user_identity_id?: string | undefined;
@@ -8118,7 +8118,7 @@ export interface Routes {
8118
8118
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
8119
8119
  starts_at: string;
8120
8120
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
8121
- ends_at: string;
8121
+ ends_at: string | null;
8122
8122
  } | undefined;
8123
8123
  /** ID of the user identity associated with the `acs_user`. */
8124
8124
  user_identity_id?: string | undefined;
@@ -8224,7 +8224,7 @@ export interface Routes {
8224
8224
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
8225
8225
  starts_at: string;
8226
8226
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
8227
- ends_at: string;
8227
+ ends_at: string | null;
8228
8228
  } | undefined;
8229
8229
  /** ID of the user identity associated with the `acs_user`. */
8230
8230
  user_identity_id?: string | undefined;
@@ -8310,7 +8310,7 @@ export interface Routes {
8310
8310
  method: 'PATCH' | 'POST';
8311
8311
  queryParams: {};
8312
8312
  jsonBody: {
8313
- /** `starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. Only applicable to Salto KS access control systems. */
8313
+ /** `starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. */
8314
8314
  access_schedule?: ({
8315
8315
  starts_at: string;
8316
8316
  ends_at: string;
@@ -28811,7 +28811,7 @@ export interface Routes {
28811
28811
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
28812
28812
  starts_at: string;
28813
28813
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
28814
- ends_at: string;
28814
+ ends_at: string | null;
28815
28815
  } | undefined;
28816
28816
  /** ID of the user identity associated with the `acs_user`. */
28817
28817
  user_identity_id?: string | undefined;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@seamapi/types",
3
- "version": "1.299.0",
3
+ "version": "1.300.0",
4
4
  "description": "TypeScript types for the Seam API.",
5
5
  "type": "module",
6
6
  "main": "index.js",
@@ -12,7 +12,8 @@ export const start_end_schedule = z.object({
12
12
  .datetime()
13
13
  .describe(
14
14
  "Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.",
15
- ),
15
+ )
16
+ .nullable(),
16
17
  })
17
18
 
18
19
  // export const schedule = z.union([
@@ -1054,6 +1054,7 @@ export default {
1054
1054
  description:
1055
1055
  "Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.",
1056
1056
  format: 'date-time',
1057
+ nullable: true,
1057
1058
  type: 'string',
1058
1059
  },
1059
1060
  starts_at: {
@@ -11102,12 +11103,15 @@ export default {
11102
11103
  properties: {
11103
11104
  access_schedule: {
11104
11105
  description:
11105
- "`starts_at` and `ends_at` timestamps for the new `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. Only applicable to Salto KS access control systems.",
11106
+ "`starts_at` and `ends_at` timestamps for the new `acs_user`'s access. If you specify an `access_schedule`, you may include both `starts_at` and `ends_at`. `starts_at` defaults to the current time if not provided. `ends_at` is optional and must be a time in the future and after `starts_at`.",
11106
11107
  properties: {
11107
- ends_at: { format: 'date-time', type: 'string' },
11108
+ ends_at: {
11109
+ format: 'date-time',
11110
+ nullable: true,
11111
+ type: 'string',
11112
+ },
11108
11113
  starts_at: { format: 'date-time', type: 'string' },
11109
11114
  },
11110
- required: ['starts_at', 'ends_at'],
11111
11115
  type: 'object',
11112
11116
  },
11113
11117
  acs_access_group_ids: {
@@ -11619,6 +11623,7 @@ export default {
11619
11623
  description:
11620
11624
  "Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.",
11621
11625
  format: 'date-time',
11626
+ nullable: true,
11622
11627
  type: 'string',
11623
11628
  },
11624
11629
  starts_at: {
@@ -12011,6 +12016,7 @@ export default {
12011
12016
  description:
12012
12017
  "Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format.",
12013
12018
  format: 'date-time',
12019
+ nullable: true,
12014
12020
  type: 'string',
12015
12021
  },
12016
12022
  starts_at: {
@@ -12433,7 +12439,7 @@ export default {
12433
12439
  properties: {
12434
12440
  access_schedule: {
12435
12441
  description:
12436
- "`starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. Only applicable to Salto KS access control systems.",
12442
+ "`starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`.",
12437
12443
  nullable: true,
12438
12444
  properties: {
12439
12445
  ends_at: { format: 'date-time', type: 'string' },
@@ -12513,7 +12519,7 @@ export default {
12513
12519
  properties: {
12514
12520
  access_schedule: {
12515
12521
  description:
12516
- "`starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. Only applicable to Salto KS access control systems.",
12522
+ "`starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`.",
12517
12523
  nullable: true,
12518
12524
  properties: {
12519
12525
  ends_at: { format: 'date-time', type: 'string' },
@@ -4836,7 +4836,7 @@ export interface Routes {
4836
4836
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
4837
4837
  starts_at: string
4838
4838
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
4839
- ends_at: string
4839
+ ends_at: string | null
4840
4840
  }
4841
4841
  | undefined
4842
4842
  /** ID of the user identity associated with the `acs_user`. */
@@ -8964,11 +8964,11 @@ export interface Routes {
8964
8964
  acs_access_group_ids?: string[]
8965
8965
  /** ID of the user identity with which to associate the new `acs_user`. */
8966
8966
  user_identity_id?: string | undefined
8967
- /** `starts_at` and `ends_at` timestamps for the new `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. Only applicable to Salto KS access control systems. */
8967
+ /** `starts_at` and `ends_at` timestamps for the new `acs_user`'s access. If you specify an `access_schedule`, you may include both `starts_at` and `ends_at`. `starts_at` defaults to the current time if not provided. `ends_at` is optional and must be a time in the future and after `starts_at`. */
8968
8968
  access_schedule?:
8969
8969
  | {
8970
- starts_at: string
8971
- ends_at: string
8970
+ starts_at?: string | undefined
8971
+ ends_at?: (string | undefined) | null
8972
8972
  }
8973
8973
  | undefined
8974
8974
  /** Full name of the `acs_user`. */
@@ -9017,7 +9017,7 @@ export interface Routes {
9017
9017
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9018
9018
  starts_at: string
9019
9019
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9020
- ends_at: string
9020
+ ends_at: string | null
9021
9021
  }
9022
9022
  | undefined
9023
9023
  /** ID of the user identity associated with the `acs_user`. */
@@ -9152,7 +9152,7 @@ export interface Routes {
9152
9152
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9153
9153
  starts_at: string
9154
9154
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9155
- ends_at: string
9155
+ ends_at: string | null
9156
9156
  }
9157
9157
  | undefined
9158
9158
  /** ID of the user identity associated with the `acs_user`. */
@@ -9283,7 +9283,7 @@ export interface Routes {
9283
9283
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9284
9284
  starts_at: string
9285
9285
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9286
- ends_at: string
9286
+ ends_at: string | null
9287
9287
  }
9288
9288
  | undefined
9289
9289
  /** ID of the user identity associated with the `acs_user`. */
@@ -9525,7 +9525,7 @@ export interface Routes {
9525
9525
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9526
9526
  starts_at: string
9527
9527
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9528
- ends_at: string
9528
+ ends_at: string | null
9529
9529
  }
9530
9530
  | undefined
9531
9531
  /** ID of the user identity associated with the `acs_user`. */
@@ -9651,7 +9651,7 @@ export interface Routes {
9651
9651
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9652
9652
  starts_at: string
9653
9653
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
9654
- ends_at: string
9654
+ ends_at: string | null
9655
9655
  }
9656
9656
  | undefined
9657
9657
  /** ID of the user identity associated with the `acs_user`. */
@@ -9747,7 +9747,7 @@ export interface Routes {
9747
9747
  method: 'PATCH' | 'POST'
9748
9748
  queryParams: {}
9749
9749
  jsonBody: {
9750
- /** `starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. Only applicable to Salto KS access control systems. */
9750
+ /** `starts_at` and `ends_at` timestamps for the `acs_user`'s access. If you specify an `access_schedule`, you must include both `starts_at` and `ends_at`. `ends_at` must be a time in the future and after `starts_at`. */
9751
9751
  access_schedule?:
9752
9752
  | ({
9753
9753
  starts_at: string
@@ -35862,7 +35862,7 @@ export interface Routes {
35862
35862
  /** Date and time at which the user's access starts, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
35863
35863
  starts_at: string
35864
35864
  /** Date and time at which the user's access ends, in [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format. */
35865
- ends_at: string
35865
+ ends_at: string | null
35866
35866
  }
35867
35867
  | undefined
35868
35868
  /** ID of the user identity associated with the `acs_user`. */