@seamapi/types 1.588.0 → 1.589.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.
@@ -31186,12 +31186,14 @@ export type Routes = {
31186
31186
  connected_account_id: string;
31187
31187
  /** Indicates whether newly-added devices should appear as [managed devices](https://docs.seam.co/latest/core-concepts/devices/managed-and-unmanaged-devices). */
31188
31188
  automatically_manage_new_devices?: boolean | undefined;
31189
- /** Custom metadata that you want to associate with the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](https://docs.seam.co/latest/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](https://docs.seam.co/latest/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). */
31189
+ /** Custom metadata that you want to associate with the connected account. Entirely replaces the existing custom metadata object. If a new Connect Webview contains custom metadata and is used to reconnect a connected account, the custom metadata from the Connect Webview will entirely replace the entire custom metadata object on the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](https://docs.seam.co/latest/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](https://docs.seam.co/latest/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). */
31190
31190
  custom_metadata?: {
31191
31191
  [x: string]: string | boolean | null;
31192
31192
  } | undefined;
31193
31193
  /** List of accepted device capabilities that restrict the types of devices that can be connected through this connected account. Valid values are `lock`, `thermostat`, `noise_sensor`, and `access_control`. */
31194
31194
  accepted_capabilities?: ('lock' | 'thermostat' | 'noise_sensor' | 'access_control')[] | undefined;
31195
+ /** The customer key to associate with this connected account. If provided, the connected account and all resources under the connected account will be moved to this customer. */
31196
+ customer_key?: string | undefined;
31195
31197
  };
31196
31198
  commonParams: {};
31197
31199
  formData: {};
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@seamapi/types",
3
- "version": "1.588.0",
3
+ "version": "1.589.0",
4
4
  "description": "TypeScript types for the Seam API.",
5
5
  "type": "module",
6
6
  "main": "index.js",
@@ -40267,9 +40267,15 @@ export default {
40267
40267
  ],
40268
40268
  },
40269
40269
  description:
40270
- 'Custom metadata that you want to associate with the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](https://docs.seam.co/latest/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](https://docs.seam.co/latest/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata).',
40270
+ 'Custom metadata that you want to associate with the connected account. Entirely replaces the existing custom metadata object. If a new Connect Webview contains custom metadata and is used to reconnect a connected account, the custom metadata from the Connect Webview will entirely replace the entire custom metadata object on the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](https://docs.seam.co/latest/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](https://docs.seam.co/latest/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata).',
40271
40271
  type: 'object',
40272
40272
  },
40273
+ customer_key: {
40274
+ description:
40275
+ 'The customer key to associate with this connected account. If provided, the connected account and all resources under the connected account will be moved to this customer. ',
40276
+ minLength: 1,
40277
+ type: 'string',
40278
+ },
40273
40279
  },
40274
40280
  required: ['connected_account_id'],
40275
40281
  type: 'object',
@@ -36243,7 +36243,7 @@ export type Routes = {
36243
36243
  connected_account_id: string
36244
36244
  /** Indicates whether newly-added devices should appear as [managed devices](https://docs.seam.co/latest/core-concepts/devices/managed-and-unmanaged-devices). */
36245
36245
  automatically_manage_new_devices?: boolean | undefined
36246
- /** Custom metadata that you want to associate with the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](https://docs.seam.co/latest/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](https://docs.seam.co/latest/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). */
36246
+ /** Custom metadata that you want to associate with the connected account. Entirely replaces the existing custom metadata object. If a new Connect Webview contains custom metadata and is used to reconnect a connected account, the custom metadata from the Connect Webview will entirely replace the entire custom metadata object on the connected account. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a connected account](https://docs.seam.co/latest/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter connected accounts by the desired metadata](https://docs.seam.co/latest/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). */
36247
36247
  custom_metadata?:
36248
36248
  | {
36249
36249
  [x: string]: string | boolean | null
@@ -36253,6 +36253,8 @@ export type Routes = {
36253
36253
  accepted_capabilities?:
36254
36254
  | ('lock' | 'thermostat' | 'noise_sensor' | 'access_control')[]
36255
36255
  | undefined
36256
+ /** The customer key to associate with this connected account. If provided, the connected account and all resources under the connected account will be moved to this customer. */
36257
+ customer_key?: string | undefined
36256
36258
  }
36257
36259
  commonParams: {}
36258
36260
  formData: {}