@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.
package/dist/connect.cjs CHANGED
@@ -1597,7 +1597,7 @@ var start_end_schedule = zod.z.object({
1597
1597
  ),
1598
1598
  ends_at: zod.z.string().datetime().describe(
1599
1599
  "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."
1600
- )
1600
+ ).nullable()
1601
1601
  });
1602
1602
  var schedule = start_end_schedule;
1603
1603
 
@@ -3812,6 +3812,7 @@ var openapi_default = {
3812
3812
  ends_at: {
3813
3813
  description: "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.",
3814
3814
  format: "date-time",
3815
+ nullable: true,
3815
3816
  type: "string"
3816
3817
  },
3817
3818
  starts_at: {
@@ -13394,12 +13395,15 @@ var openapi_default = {
13394
13395
  schema: {
13395
13396
  properties: {
13396
13397
  access_schedule: {
13397
- description: "`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.",
13398
+ description: "`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`.",
13398
13399
  properties: {
13399
- ends_at: { format: "date-time", type: "string" },
13400
+ ends_at: {
13401
+ format: "date-time",
13402
+ nullable: true,
13403
+ type: "string"
13404
+ },
13400
13405
  starts_at: { format: "date-time", type: "string" }
13401
13406
  },
13402
- required: ["starts_at", "ends_at"],
13403
13407
  type: "object"
13404
13408
  },
13405
13409
  acs_access_group_ids: {
@@ -13894,6 +13898,7 @@ var openapi_default = {
13894
13898
  ends_at: {
13895
13899
  description: "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.",
13896
13900
  format: "date-time",
13901
+ nullable: true,
13897
13902
  type: "string"
13898
13903
  },
13899
13904
  starts_at: {
@@ -14252,6 +14257,7 @@ var openapi_default = {
14252
14257
  ends_at: {
14253
14258
  description: "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.",
14254
14259
  format: "date-time",
14260
+ nullable: true,
14255
14261
  type: "string"
14256
14262
  },
14257
14263
  starts_at: {
@@ -14638,7 +14644,7 @@ var openapi_default = {
14638
14644
  schema: {
14639
14645
  properties: {
14640
14646
  access_schedule: {
14641
- description: "`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.",
14647
+ description: "`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`.",
14642
14648
  nullable: true,
14643
14649
  properties: {
14644
14650
  ends_at: { format: "date-time", type: "string" },
@@ -14715,7 +14721,7 @@ var openapi_default = {
14715
14721
  schema: {
14716
14722
  properties: {
14717
14723
  access_schedule: {
14718
- description: "`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.",
14724
+ description: "`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`.",
14719
14725
  nullable: true,
14720
14726
  properties: {
14721
14727
  ends_at: { format: "date-time", type: "string" },