@seamapi/types 1.502.0 → 1.503.0

package/lib/seam/connect/route-types.d.ts

@@ -1301,6 +1301,8 @@ export type Routes = {
           
           In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
             access_code: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Unique identifier for a group of access codes that share the same code. */
                 common_code_key: string | null;
                 /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -1855,6 +1857,8 @@ export type Routes = {
         formData: {};
         jsonResponse: {
             access_codes: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Unique identifier for a group of access codes that share the same code. */
                 common_code_key: string | null;
                 /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -3663,6 +3667,8 @@ export type Routes = {
           
           In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
             access_code: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Unique identifier for a group of access codes that share the same code. */
                 common_code_key: string | null;
                 /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -4190,6 +4196,8 @@ export type Routes = {
         formData: {};
         jsonResponse: {
             access_codes: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Unique identifier for a group of access codes that share the same code. */
                 common_code_key: string | null;
                 /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -4724,6 +4732,8 @@ export type Routes = {
           
           In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
             backup_access_code: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Unique identifier for a group of access codes that share the same code. */
                 common_code_key: string | null;
                 /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -5236,6 +5246,8 @@ export type Routes = {
           
           In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
             access_code: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Unique identifier for a group of access codes that share the same code. */
                 common_code_key: string | null;
                 /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -5787,6 +5799,8 @@ export type Routes = {
           
           - [Kwikset](https://docs.seam.co/latest/device-and-system-integration-guides/kwikset-locks) */
             access_code: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
                 type: 'time_bound' | 'ongoing';
                 /** Unique identifier for the access code. */
@@ -7582,6 +7596,8 @@ export type Routes = {
           
           - [Kwikset](https://docs.seam.co/latest/device-and-system-integration-guides/kwikset-locks) */
             access_code: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
                 type: 'time_bound' | 'ongoing';
                 /** Unique identifier for the access code. */
@@ -8088,6 +8104,8 @@ export type Routes = {
         formData: {};
         jsonResponse: {
             access_codes: {
+                /** Unique identifier for the Seam workspace associated with the access code. */
+                workspace_id: string;
                 /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
                 type: 'time_bound' | 'ongoing';
                 /** Unique identifier for the access code. */
@@ -19030,6 +19048,8 @@ export type Routes = {
                     } | undefined;
                 }[] | undefined;
                 access_codes?: {
+                    /** Unique identifier for the Seam workspace associated with the access code. */
+                    workspace_id: string;
                     /** Unique identifier for a group of access codes that share the same code. */
                     common_code_key: string | null;
                     /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -19535,6 +19555,8 @@ export type Routes = {
                     is_offline_access_code: boolean;
                 }[] | undefined;
                 unmanaged_access_codes?: {
+                    /** Unique identifier for the Seam workspace associated with the access code. */
+                    workspace_id: string;
                     /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
                     type: 'time_bound' | 'ongoing';
                     /** Unique identifier for the access code. */
@@ -84435,6 +84457,8 @@ export type Routes = {
                     } | undefined;
                 }[] | undefined;
                 access_codes?: {
+                    /** Unique identifier for the Seam workspace associated with the access code. */
+                    workspace_id: string;
                     /** Unique identifier for a group of access codes that share the same code. */
                     common_code_key: string | null;
                     /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -84940,6 +84964,8 @@ export type Routes = {
                     is_offline_access_code: boolean;
                 }[] | undefined;
                 unmanaged_access_codes?: {
+                    /** Unique identifier for the Seam workspace associated with the access code. */
+                    workspace_id: string;
                     /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
                     type: 'time_bound' | 'ongoing';
                     /** Unique identifier for the access code. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seamapi/types",
-  "version": "1.502.0",
+  "version": "1.503.0",
   "description": "TypeScript types for the Seam API.",
   "type": "module",
   "main": "index.js",

package/src/lib/seam/connect/models/access-codes/managed-access-code.ts

@@ -495,6 +495,12 @@ const _access_code_warning_map = z.object({
 export type AccessCodeWarningMap = z.infer<typeof _access_code_warning_map>
 
 export const access_code = z.object({
+  workspace_id: z
+    .string()
+    .uuid()
+    .describe(
+      'Unique identifier for the Seam workspace associated with the access code.',
+    ),
   common_code_key: z
     .string()
     .nullable()

package/src/lib/seam/connect/models/access-codes/unmanaged-access-code.ts

@@ -4,6 +4,7 @@ import { access_code } from './managed-access-code.js'
 
 export const unmanaged_access_code = access_code
   .pick({
+    workspace_id: true,
     type: true,
     access_code_id: true,
     device_id: true,

package/src/lib/seam/connect/openapi.ts

@@ -1792,8 +1792,15 @@ export default {
               thermostats: { name: 'Thermostats' },
             },
           },
+          workspace_id: {
+            description:
+              'Unique identifier for the Seam workspace associated with the access code.',
+            format: 'uuid',
+            type: 'string',
+          },
         },
         required: [
+          'workspace_id',
           'common_code_key',
           'type',
           'access_code_id',
@@ -22266,8 +22273,15 @@ export default {
               thermostats: { name: 'Thermostats' },
             },
           },
+          workspace_id: {
+            description:
+              'Unique identifier for the Seam workspace associated with the access code.',
+            format: 'uuid',
+            type: 'string',
+          },
         },
         required: [
+          'workspace_id',
           'type',
           'access_code_id',
           'device_id',

package/src/lib/seam/connect/route-types.ts

@@ -1482,6 +1482,8 @@ export type Routes = {
     
     In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
       access_code: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Unique identifier for a group of access codes that share the same code. */
         common_code_key: string | null
         /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -2091,6 +2093,8 @@ export type Routes = {
     formData: {}
     jsonResponse: {
       access_codes: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Unique identifier for a group of access codes that share the same code. */
         common_code_key: string | null
         /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -4135,6 +4139,8 @@ export type Routes = {
     
     In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
       access_code: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Unique identifier for a group of access codes that share the same code. */
         common_code_key: string | null
         /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -4717,6 +4723,8 @@ export type Routes = {
     formData: {}
     jsonResponse: {
       access_codes: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Unique identifier for a group of access codes that share the same code. */
         common_code_key: string | null
         /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -5306,6 +5314,8 @@ export type Routes = {
     
     In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
       backup_access_code: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Unique identifier for a group of access codes that share the same code. */
         common_code_key: string | null
         /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -5873,6 +5883,8 @@ export type Routes = {
     
     In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes#offline-access-codes). Offline access (PIN) codes are designed for door locks that might not always maintain an internet connection. For this type of access code, the device manufacturer uses encryption keys (tokens) to create server-based registries of algorithmically-generated offline PIN codes. Because the tokens remain synchronized with the managed devices, the locks do not require an active internet connection—and you do not need to be near the locks—to create an offline access code. Then, owners or managers can share these offline codes with users through a variety of mechanisms, such as messaging applications. That is, lock users do not need to install a smartphone application to receive an offline access code. */
       access_code: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Unique identifier for a group of access codes that share the same code. */
         common_code_key: string | null
         /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -6479,6 +6491,8 @@ export type Routes = {
     
     - [Kwikset](https://docs.seam.co/latest/device-and-system-integration-guides/kwikset-locks) */
       access_code: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
         type: 'time_bound' | 'ongoing'
         /** Unique identifier for the access code. */
@@ -8510,6 +8524,8 @@ export type Routes = {
     
     - [Kwikset](https://docs.seam.co/latest/device-and-system-integration-guides/kwikset-locks) */
       access_code: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
         type: 'time_bound' | 'ongoing'
         /** Unique identifier for the access code. */
@@ -9071,6 +9087,8 @@ export type Routes = {
     formData: {}
     jsonResponse: {
       access_codes: {
+        /** Unique identifier for the Seam workspace associated with the access code. */
+        workspace_id: string
         /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
         type: 'time_bound' | 'ongoing'
         /** Unique identifier for the access code. */
@@ -22132,6 +22150,8 @@ export type Routes = {
           | undefined
         access_codes?:
           | {
+              /** Unique identifier for the Seam workspace associated with the access code. */
+              workspace_id: string
               /** Unique identifier for a group of access codes that share the same code. */
               common_code_key: string | null
               /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -22694,6 +22714,8 @@ export type Routes = {
           | undefined
         unmanaged_access_codes?:
           | {
+              /** Unique identifier for the Seam workspace associated with the access code. */
+              workspace_id: string
               /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
               type: 'time_bound' | 'ongoing'
               /** Unique identifier for the access code. */
@@ -100394,6 +100416,8 @@ export type Routes = {
           | undefined
         access_codes?:
           | {
+              /** Unique identifier for the Seam workspace associated with the access code. */
+              workspace_id: string
               /** Unique identifier for a group of access codes that share the same code. */
               common_code_key: string | null
               /** Indicates whether the code is set on the device according to a preconfigured schedule. */
@@ -100956,6 +100980,8 @@ export type Routes = {
           | undefined
         unmanaged_access_codes?:
           | {
+              /** Unique identifier for the Seam workspace associated with the access code. */
+              workspace_id: string
               /** Type of the access code. `ongoing` access codes are active continuously until deactivated manually. `time_bound` access codes have a specific duration. */
               type: 'time_bound' | 'ongoing'
               /** Unique identifier for the access code. */