@seamapi/types 1.415.0 → 1.416.1

package/dist/connect.cjs

@@ -849,6 +849,9 @@ var connected_account = zod.z.object({
   custom_metadata,
   automatically_manage_new_devices: zod.z.boolean().describe(
     "Indicates whether Seam should [import all new devices](https://docs.seam.co/latest/core-concepts/connect-webviews/customizing-connect-webviews#automatically_manage_new_devices) for the connected account to make these devices available for use and management by the Seam API."
+  ),
+  customer_key: zod.z.string().optional().describe(
+    "Your unique key for the customer associated with this connected account."
   )
 }).describe(`
   ---
@@ -2452,6 +2455,7 @@ var unmanaged_acs_access_group = common_acs_access_group.extend({
 }).describe(`
   ---
   route_path: /acs/access_groups/unmanaged
+  undocumented: Unreleased.
   ---
 `);
 var acs_entrance_assa_abloy_vostio_metadata = zod.z.object({
@@ -2688,6 +2692,7 @@ var unmanaged_acs_credential = common_acs_credential.merge(
 ).describe(`
   ---
   route_path: /acs/credentials/unmanaged
+  undocumented: Unreleased.
   ---
   Means by which an [ACS user](https://docs.seam.co/latest/capability-guides/access-systems/user-management) gains access at an [entrance](https://docs.seam.co/latest/capability-guides/access-systems/retrieving-entrance-details). The \`unmanaged_acs_credential\` object, which is not managed by Seam, represents a [credential](https://docs.seam.co/latest/capability-guides/access-systems/managing-credentials) that provides an ACS user access within an [access control system](https://docs.seam.co/latest/capability-guides/access-systems). For each \`acs_credential\` object, you define the access method. You can also specify additional properties, such as a PIN code.
 `);
@@ -3379,6 +3384,7 @@ var unmanaged_acs_user = common_acs_user.merge(
 ).describe(`
   ---
   route_path: /acs/users/unmanaged
+  undocumented: Unreleased.
   ---
   Represents an unmanaged [user](https://docs.seam.co/latest/capability-guides/access-systems/user-management) in an [access control system](https://docs.seam.co/latest/capability-guides/access-systems).
 `);
@@ -7177,7 +7183,8 @@ var openapi_default = {
           "workspace_id"
         ],
         type: "object",
-        "x-route-path": "/acs/credential_pools"
+        "x-route-path": "/acs/credential_pools",
+        "x-undocumented": "Will be removed."
       },
       acs_credential_provisioning_automation: {
         properties: {
@@ -7198,7 +7205,8 @@ var openapi_default = {
           "workspace_id"
         ],
         type: "object",
-        "x-route-path": "/acs/credential_provisioning_automations"
+        "x-route-path": "/acs/credential_provisioning_automations",
+        "x-undocumented": "Will be removed."
       },
       acs_encoder: {
         description: "Represents a hardware device that encodes [credential](https://docs.seam.co/latest/capability-guides/access-systems/managing-credentials) data onto physical cards within an [access control system](https://docs.seam.co/latest/capability-guides/access-systems).\n\nSome access control systems require credentials to be encoded onto plastic key cards using a card encoder. This process involves the following two key steps:\n\n1. Credential creation\n   Configure the access parameters for the credential.\n2. Card encoding\n   Write the credential data onto the card using a compatible card encoder.\n\nSeparately, the Seam API also supports card scanning, which enables you to scan and read the encoded data on a card. You can use this action to confirm consistency with access control system records or diagnose discrepancies if needed.\n\n See [Working with Card Encoders and Scanners](https://docs.seam.co/latest/capability-guides/access-systems/working-with-card-encoders-and-scanners).\n\nTo verify if your access control system requires a card encoder, see the corresponding [system integration guide](https://docs.seam.co/latest/device-and-system-integration-guides/overview#access-control-systems).",
@@ -9395,7 +9403,8 @@ var openapi_default = {
                           "is_managed"
                         ],
                         type: "object",
-                        "x-route-path": "/acs/credentials/unmanaged"
+                        "x-route-path": "/acs/credentials/unmanaged",
+                        "x-undocumented": "Unreleased."
                       }
                     ],
                     "x-route-path": "/acs/credentials"
@@ -10454,7 +10463,8 @@ var openapi_default = {
                       "is_managed"
                     ],
                     type: "object",
-                    "x-route-path": "/acs/credentials/unmanaged"
+                    "x-route-path": "/acs/credentials/unmanaged",
+                    "x-undocumented": "Unreleased."
                   }
                 ]
               },
@@ -12129,6 +12139,10 @@ var openapi_default = {
             description: "Set of key:value pairs. Adding custom metadata to a resource, such as a [Connect Webview](https://docs.seam.co/latest/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview), [connected account](https://docs.seam.co/latest/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account), or [device](https://docs.seam.co/latest/core-concepts/devices/adding-custom-metadata-to-a-device), enables you to store custom information, like customer details or internal IDs from your application.",
             type: "object"
           },
+          customer_key: {
+            description: "Your unique key for the customer associated with this connected account.",
+            type: "string"
+          },
           errors: {
             description: "Errors associated with the connected account.",
             items: {
@@ -22592,7 +22606,8 @@ var openapi_default = {
           "is_managed"
         ],
         type: "object",
-        "x-route-path": "/acs/access_groups/unmanaged"
+        "x-route-path": "/acs/access_groups/unmanaged",
+        "x-undocumented": "Unreleased."
       },
       unmanaged_acs_credential: {
         description: "Means by which an [ACS user](https://docs.seam.co/latest/capability-guides/access-systems/user-management) gains access at an [entrance](https://docs.seam.co/latest/capability-guides/access-systems/retrieving-entrance-details). The `unmanaged_acs_credential` object, which is not managed by Seam, represents a [credential](https://docs.seam.co/latest/capability-guides/access-systems/managing-credentials) that provides an ACS user access within an [access control system](https://docs.seam.co/latest/capability-guides/access-systems). For each `acs_credential` object, you define the access method. You can also specify additional properties, such as a PIN code.",
@@ -22904,7 +22919,8 @@ var openapi_default = {
           "is_managed"
         ],
         type: "object",
-        "x-route-path": "/acs/credentials/unmanaged"
+        "x-route-path": "/acs/credentials/unmanaged",
+        "x-undocumented": "Unreleased."
       },
       unmanaged_acs_user: {
         description: "Represents an unmanaged [user](https://docs.seam.co/latest/capability-guides/access-systems/user-management) in an [access control system](https://docs.seam.co/latest/capability-guides/access-systems).",
@@ -23494,7 +23510,8 @@ var openapi_default = {
           "is_managed"
         ],
         type: "object",
-        "x-route-path": "/acs/users/unmanaged"
+        "x-route-path": "/acs/users/unmanaged",
+        "x-undocumented": "Unreleased."
       },
       unmanaged_device: {
         description: "Represents an [unmanaged device](https://docs.seam.co/latest/core-concepts/devices/managed-and-unmanaged-devices). An unmanaged device has a limited set of visible properties and a subset of supported events. You cannot control an unmanaged device. Any [access codes](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes/migrating-existing-access-codes) on an unmanaged device are unmanaged. To control an unmanaged device with Seam, [convert it to a managed device](https://docs.seam.co/latest/core-concepts/devices/managed-and-unmanaged-devices#convert-an-unmanaged-device-to-managed).",