@seamapi/types 1.1015.0 → 1.1017.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.
|
@@ -41103,7 +41103,7 @@ export type Routes = {
|
|
|
41103
41103
|
accepted_providers?: ('hotek' | 'dormakaba_community' | 'legic_connect' | 'akuvox' | 'august' | 'avigilon_alta' | 'brivo' | 'butterflymx' | 'schlage' | 'smartthings' | 'yale' | 'genie' | 'doorking' | 'salto' | 'salto_ks' | 'salto_ks_accept' | 'lockly' | 'ttlock' | 'linear' | 'noiseaware' | 'nuki' | 'igloo' | 'kwikset' | 'minut' | 'my_2n' | 'controlbyweb' | 'nest' | 'igloohome' | 'ecobee' | 'four_suites' | 'dormakaba_oracode' | 'pti' | 'wyze' | 'seam_passport' | 'visionline' | 'assa_abloy_credential_service' | 'tedee' | 'honeywell_resideo' | 'first_alert' | 'latch' | 'akiles' | 'assa_abloy_vostio' | 'assa_abloy_vostio_credential_service' | 'tado' | 'salto_space' | 'sensi' | 'keynest' | 'korelock' | 'keyincode' | 'dormakaba_ambiance' | 'ultraloq' | 'yacan' | 'dusaw' | 'sifely' | 'thirty_three_lock' | 'ring' | 'ical' | 'lodgify' | 'hostaway' | 'guesty' | 'acuity_scheduling' | 'omnitec' | 'kisi' | 'aqara' | 'yale_access' | 'hid_cm' | 'google_nest' | 'slack')[] | undefined;
|
|
41104
41104
|
/** Specifies the category of providers that you want to include. To list all providers within a category, use [`/devices/list_device_providers`](https://docs.seam.co/api/devices/list_device_providers) with the desired `provider_category` filter. */
|
|
41105
41105
|
provider_category?: ('stable' | 'consumer_smartlocks' | 'beta' | 'thermostats' | 'noise_sensors' | 'access_control_systems' | 'cameras' | 'connectors' | 'internal_beta') | undefined;
|
|
41106
|
-
/** Custom metadata that you want to associate with the Connect Webview. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a Connect Webview](https://docs.seam.co/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview) enables you to store custom information, like customer details or internal IDs from your application. The custom metadata is then transferred to any [connected accounts](https://docs.seam.co/core-concepts/connected-accounts) that were connected using the Connect Webview, making it easy to find and filter these resources in your [workspace](https://docs.seam.co/core-concepts/workspaces). You can also [filter Connect Webviews by custom metadata](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
41106
|
+
/** Custom metadata that you want to associate with the Connect Webview. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a Connect Webview](https://docs.seam.co/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview) enables you to store custom information, like customer details or internal IDs from your application. The custom metadata is then transferred to any [connected accounts](https://docs.seam.co/core-concepts/connected-accounts) that were connected using the Connect Webview, making it easy to find and filter these resources in your [workspace](https://docs.seam.co/core-concepts/workspaces). You can also [filter Connect Webviews by custom metadata](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
41107
41107
|
custom_metadata?: {
|
|
41108
41108
|
[x: string]: string | boolean | null;
|
|
41109
41109
|
} | undefined;
|
|
@@ -41277,7 +41277,7 @@ export type Routes = {
|
|
|
41277
41277
|
customer_key?: string | undefined;
|
|
41278
41278
|
/** Your user ID for the user by which you want to filter Connect Webviews. */
|
|
41279
41279
|
user_identifier_key?: string | undefined;
|
|
41280
|
-
/** Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string. */
|
|
41280
|
+
/** Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string. */
|
|
41281
41281
|
custom_metadata_has?: {
|
|
41282
41282
|
[x: string]: string | boolean;
|
|
41283
41283
|
} | undefined;
|
|
@@ -41571,7 +41571,7 @@ export type Routes = {
|
|
|
41571
41571
|
commonParams: {
|
|
41572
41572
|
/** Your user ID for the user by which you want to filter connected accounts. */
|
|
41573
41573
|
user_identifier_key?: string | undefined;
|
|
41574
|
-
/** Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string. */
|
|
41574
|
+
/** Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string. */
|
|
41575
41575
|
custom_metadata_has?: {
|
|
41576
41576
|
[x: string]: string | boolean;
|
|
41577
41577
|
} | undefined;
|
|
@@ -41817,7 +41817,7 @@ export type Routes = {
|
|
|
41817
41817
|
automatically_manage_new_devices?: boolean | undefined;
|
|
41818
41818
|
/** Human-readable name for the connected account, shown in the dashboard. For example, `Booking from Airbnb House 1`. */
|
|
41819
41819
|
display_name?: string | undefined;
|
|
41820
|
-
/** 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/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
41820
|
+
/** 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, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a connected account](https://docs.seam.co/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
41821
41821
|
custom_metadata?: {
|
|
41822
41822
|
[x: string]: string | boolean | null;
|
|
41823
41823
|
} | undefined;
|
|
@@ -44446,7 +44446,7 @@ export type Routes = {
|
|
|
44446
44446
|
created_before?: Date | undefined;
|
|
44447
44447
|
/** Your own internal user ID for the user for which you want to list devices. */
|
|
44448
44448
|
user_identifier_key?: string | undefined;
|
|
44449
|
-
/** Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Specify an empty string to match a key that is unset or set to an empty string. */
|
|
44449
|
+
/** Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string. */
|
|
44450
44450
|
custom_metadata_has?: {
|
|
44451
44451
|
[x: string]: string | boolean;
|
|
44452
44452
|
} | undefined;
|
|
@@ -47176,7 +47176,7 @@ export type Routes = {
|
|
|
47176
47176
|
device_id: string;
|
|
47177
47177
|
/** Indicates whether the device is managed. Set this parameter to `true` to convert an unmanaged device to managed. */
|
|
47178
47178
|
is_managed?: true | undefined;
|
|
47179
|
-
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
47179
|
+
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
47180
47180
|
custom_metadata?: {
|
|
47181
47181
|
[x: string]: string | boolean | null;
|
|
47182
47182
|
} | undefined;
|
|
@@ -47201,7 +47201,7 @@ export type Routes = {
|
|
|
47201
47201
|
name?: (string | null) | undefined;
|
|
47202
47202
|
/** Indicates whether the device is managed. To unmanage a device, set `is_managed` to `false`. */
|
|
47203
47203
|
is_managed?: boolean;
|
|
47204
|
-
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
47204
|
+
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
47205
47205
|
custom_metadata?: {
|
|
47206
47206
|
[x: string]: string | boolean | null;
|
|
47207
47207
|
} | undefined;
|
|
@@ -78952,7 +78952,7 @@ export type Routes = {
|
|
|
78952
78952
|
queryParams: {};
|
|
78953
78953
|
jsonBody: {
|
|
78954
78954
|
/** Name of the workspace feature flag to update. */
|
|
78955
|
-
feature_flag_name: 'RESERVATION_LEGACY' | 'EXPERIMENTAL_DASHBOARD_API_ENABLED' | 'ICAL_CONNECTOR' | 'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS' | '
|
|
78955
|
+
feature_flag_name: 'RESERVATION_LEGACY' | 'EXPERIMENTAL_DASHBOARD_API_ENABLED' | 'ICAL_CONNECTOR' | 'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS' | 'SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES' | 'MANAGE_DEVICES_CONFIRMATION_MODAL' | 'RECLAIM_ORPHANED_BACKUP_ACCESS_CODES' | 'RECONCILE_ORPHANED_SMARTTHINGS_ACCESS_CODES' | 'LYNX_MIGRATION_ENABLED' | 'AURORA_CUSTOMER_FILTER_ENABLED' | 'ACCESS_METHOD_DEADLINE_ERRORS' | 'GUARD_MATERIALIZATION_ON_UNREACHABLE_DEVICE' | 'TARGETED_ACCESS_GRANT_ISSUANCE';
|
|
78956
78956
|
/** Whether the feature flag should be enabled for the workspace. */
|
|
78957
78957
|
enabled: boolean;
|
|
78958
78958
|
};
|
|
@@ -78960,7 +78960,7 @@ export type Routes = {
|
|
|
78960
78960
|
formData: {};
|
|
78961
78961
|
jsonResponse: {
|
|
78962
78962
|
feature_flag: {
|
|
78963
|
-
feature_flag_name: 'RESERVATION_LEGACY' | 'EXPERIMENTAL_DASHBOARD_API_ENABLED' | 'ICAL_CONNECTOR' | 'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS' | '
|
|
78963
|
+
feature_flag_name: 'RESERVATION_LEGACY' | 'EXPERIMENTAL_DASHBOARD_API_ENABLED' | 'ICAL_CONNECTOR' | 'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS' | 'SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES' | 'MANAGE_DEVICES_CONFIRMATION_MODAL' | 'RECLAIM_ORPHANED_BACKUP_ACCESS_CODES' | 'RECONCILE_ORPHANED_SMARTTHINGS_ACCESS_CODES' | 'LYNX_MIGRATION_ENABLED' | 'AURORA_CUSTOMER_FILTER_ENABLED' | 'ACCESS_METHOD_DEADLINE_ERRORS' | 'GUARD_MATERIALIZATION_ON_UNREACHABLE_DEVICE' | 'TARGETED_ACCESS_GRANT_ISSUANCE';
|
|
78964
78964
|
enabled: boolean;
|
|
78965
78965
|
};
|
|
78966
78966
|
};
|
|
@@ -85181,7 +85181,6 @@ export type Routes = {
|
|
|
85181
85181
|
business_vertical?: ('neutral' | 'short_term_rental' | 'hospitality' | 'multi_family' | 'gym_management' | 'property_tours') | undefined;
|
|
85182
85182
|
feature_flags?: {
|
|
85183
85183
|
RESERVATION_LEGACY?: boolean | undefined;
|
|
85184
|
-
SALTO_KS_ENTRANCES_ONLY_FOR_SPACES?: boolean | undefined;
|
|
85185
85184
|
SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES?: boolean | undefined;
|
|
85186
85185
|
MANAGE_DEVICES_CONFIRMATION_MODAL?: boolean | undefined;
|
|
85187
85186
|
} | undefined;
|
package/package.json
CHANGED
|
@@ -50884,7 +50884,7 @@ const openapi: OpenAPISpec = {
|
|
|
50884
50884
|
],
|
|
50885
50885
|
},
|
|
50886
50886
|
description:
|
|
50887
|
-
'Custom metadata that you want to associate with the Connect Webview. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a Connect Webview](https://docs.seam.co/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview) enables you to store custom information, like customer details or internal IDs from your application. The custom metadata is then transferred to any [connected accounts](https://docs.seam.co/core-concepts/connected-accounts) that were connected using the Connect Webview, making it easy to find and filter these resources in your [workspace](https://docs.seam.co/core-concepts/workspaces). You can also [filter Connect Webviews by custom metadata](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
50887
|
+
'Custom metadata that you want to associate with the Connect Webview. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a Connect Webview](https://docs.seam.co/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview) enables you to store custom information, like customer details or internal IDs from your application. The custom metadata is then transferred to any [connected accounts](https://docs.seam.co/core-concepts/connected-accounts) that were connected using the Connect Webview, making it easy to find and filter these resources in your [workspace](https://docs.seam.co/core-concepts/workspaces). You can also [filter Connect Webviews by custom metadata](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
50888
50888
|
type: 'object',
|
|
50889
50889
|
},
|
|
50890
50890
|
custom_redirect_failure_url: {
|
|
@@ -51231,7 +51231,7 @@ const openapi: OpenAPISpec = {
|
|
|
51231
51231
|
oneOf: [{ type: 'string' }, { type: 'boolean' }],
|
|
51232
51232
|
},
|
|
51233
51233
|
description:
|
|
51234
|
-
'Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51234
|
+
'Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51235
51235
|
type: 'object',
|
|
51236
51236
|
},
|
|
51237
51237
|
},
|
|
@@ -51320,7 +51320,7 @@ const openapi: OpenAPISpec = {
|
|
|
51320
51320
|
oneOf: [{ type: 'string' }, { type: 'boolean' }],
|
|
51321
51321
|
},
|
|
51322
51322
|
description:
|
|
51323
|
-
'Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51323
|
+
'Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51324
51324
|
type: 'object',
|
|
51325
51325
|
},
|
|
51326
51326
|
customer_key: {
|
|
@@ -51659,7 +51659,7 @@ const openapi: OpenAPISpec = {
|
|
|
51659
51659
|
oneOf: [{ type: 'string' }, { type: 'boolean' }],
|
|
51660
51660
|
},
|
|
51661
51661
|
description:
|
|
51662
|
-
'Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51662
|
+
'Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51663
51663
|
type: 'object',
|
|
51664
51664
|
},
|
|
51665
51665
|
},
|
|
@@ -51768,7 +51768,7 @@ const openapi: OpenAPISpec = {
|
|
|
51768
51768
|
oneOf: [{ type: 'string' }, { type: 'boolean' }],
|
|
51769
51769
|
},
|
|
51770
51770
|
description:
|
|
51771
|
-
'Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51771
|
+
'Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string.',
|
|
51772
51772
|
type: 'object',
|
|
51773
51773
|
},
|
|
51774
51774
|
customer_key: {
|
|
@@ -52007,7 +52007,7 @@ const openapi: OpenAPISpec = {
|
|
|
52007
52007
|
],
|
|
52008
52008
|
},
|
|
52009
52009
|
description:
|
|
52010
|
-
'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/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
52010
|
+
'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, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a connected account](https://docs.seam.co/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
52011
52011
|
type: 'object',
|
|
52012
52012
|
},
|
|
52013
52013
|
customer_key: {
|
|
@@ -52109,7 +52109,7 @@ const openapi: OpenAPISpec = {
|
|
|
52109
52109
|
],
|
|
52110
52110
|
},
|
|
52111
52111
|
description:
|
|
52112
|
-
'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/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
52112
|
+
'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, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a connected account](https://docs.seam.co/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
52113
52113
|
type: 'object',
|
|
52114
52114
|
},
|
|
52115
52115
|
customer_key: {
|
|
@@ -55485,7 +55485,7 @@ const openapi: OpenAPISpec = {
|
|
|
55485
55485
|
oneOf: [{ type: 'string' }, { type: 'boolean' }],
|
|
55486
55486
|
},
|
|
55487
55487
|
description:
|
|
55488
|
-
'Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Specify an empty string to match a key that is unset or set to an empty string.',
|
|
55488
|
+
'Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string.',
|
|
55489
55489
|
type: 'object',
|
|
55490
55490
|
},
|
|
55491
55491
|
},
|
|
@@ -55675,7 +55675,7 @@ const openapi: OpenAPISpec = {
|
|
|
55675
55675
|
oneOf: [{ type: 'string' }, { type: 'boolean' }],
|
|
55676
55676
|
},
|
|
55677
55677
|
description:
|
|
55678
|
-
'Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Specify an empty string to match a key that is unset or set to an empty string.',
|
|
55678
|
+
'Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string.',
|
|
55679
55679
|
type: 'object',
|
|
55680
55680
|
},
|
|
55681
55681
|
customer_key: {
|
|
@@ -58832,7 +58832,7 @@ const openapi: OpenAPISpec = {
|
|
|
58832
58832
|
],
|
|
58833
58833
|
},
|
|
58834
58834
|
description:
|
|
58835
|
-
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
58835
|
+
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
58836
58836
|
type: 'object',
|
|
58837
58837
|
},
|
|
58838
58838
|
device_id: {
|
|
@@ -58900,7 +58900,7 @@ const openapi: OpenAPISpec = {
|
|
|
58900
58900
|
],
|
|
58901
58901
|
},
|
|
58902
58902
|
description:
|
|
58903
|
-
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
58903
|
+
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
58904
58904
|
type: 'object',
|
|
58905
58905
|
},
|
|
58906
58906
|
device_id: {
|
|
@@ -58975,7 +58975,7 @@ const openapi: OpenAPISpec = {
|
|
|
58975
58975
|
],
|
|
58976
58976
|
},
|
|
58977
58977
|
description:
|
|
58978
|
-
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
58978
|
+
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
58979
58979
|
type: 'object',
|
|
58980
58980
|
},
|
|
58981
58981
|
device_id: {
|
|
@@ -59064,7 +59064,7 @@ const openapi: OpenAPISpec = {
|
|
|
59064
59064
|
],
|
|
59065
59065
|
},
|
|
59066
59066
|
description:
|
|
59067
|
-
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
59067
|
+
'Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata.',
|
|
59068
59068
|
type: 'object',
|
|
59069
59069
|
},
|
|
59070
59070
|
device_id: {
|
|
@@ -67431,7 +67431,6 @@ const openapi: OpenAPISpec = {
|
|
|
67431
67431
|
'EXPERIMENTAL_DASHBOARD_API_ENABLED',
|
|
67432
67432
|
'ICAL_CONNECTOR',
|
|
67433
67433
|
'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS',
|
|
67434
|
-
'SALTO_KS_ENTRANCES_ONLY_FOR_SPACES',
|
|
67435
67434
|
'SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES',
|
|
67436
67435
|
'MANAGE_DEVICES_CONFIRMATION_MODAL',
|
|
67437
67436
|
'RECLAIM_ORPHANED_BACKUP_ACCESS_CODES',
|
|
@@ -67466,7 +67465,6 @@ const openapi: OpenAPISpec = {
|
|
|
67466
67465
|
'EXPERIMENTAL_DASHBOARD_API_ENABLED',
|
|
67467
67466
|
'ICAL_CONNECTOR',
|
|
67468
67467
|
'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS',
|
|
67469
|
-
'SALTO_KS_ENTRANCES_ONLY_FOR_SPACES',
|
|
67470
67468
|
'SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES',
|
|
67471
67469
|
'MANAGE_DEVICES_CONFIRMATION_MODAL',
|
|
67472
67470
|
'RECLAIM_ORPHANED_BACKUP_ACCESS_CODES',
|
|
@@ -73110,9 +73108,6 @@ const openapi: OpenAPISpec = {
|
|
|
73110
73108
|
SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES: {
|
|
73111
73109
|
type: 'boolean',
|
|
73112
73110
|
},
|
|
73113
|
-
SALTO_KS_ENTRANCES_ONLY_FOR_SPACES: {
|
|
73114
|
-
type: 'boolean',
|
|
73115
|
-
},
|
|
73116
73111
|
},
|
|
73117
73112
|
type: 'object',
|
|
73118
73113
|
},
|
|
@@ -73606,9 +73601,6 @@ const openapi: OpenAPISpec = {
|
|
|
73606
73601
|
SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES: {
|
|
73607
73602
|
type: 'boolean',
|
|
73608
73603
|
},
|
|
73609
|
-
SALTO_KS_ENTRANCES_ONLY_FOR_SPACES: {
|
|
73610
|
-
type: 'boolean',
|
|
73611
|
-
},
|
|
73612
73604
|
},
|
|
73613
73605
|
type: 'object',
|
|
73614
73606
|
},
|
|
@@ -48219,7 +48219,7 @@ export type Routes = {
|
|
|
48219
48219
|
| 'internal_beta'
|
|
48220
48220
|
)
|
|
48221
48221
|
| undefined
|
|
48222
|
-
/** Custom metadata that you want to associate with the Connect Webview. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a Connect Webview](https://docs.seam.co/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview) enables you to store custom information, like customer details or internal IDs from your application. The custom metadata is then transferred to any [connected accounts](https://docs.seam.co/core-concepts/connected-accounts) that were connected using the Connect Webview, making it easy to find and filter these resources in your [workspace](https://docs.seam.co/core-concepts/workspaces). You can also [filter Connect Webviews by custom metadata](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
48222
|
+
/** Custom metadata that you want to associate with the Connect Webview. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a Connect Webview](https://docs.seam.co/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview) enables you to store custom information, like customer details or internal IDs from your application. The custom metadata is then transferred to any [connected accounts](https://docs.seam.co/core-concepts/connected-accounts) that were connected using the Connect Webview, making it easy to find and filter these resources in your [workspace](https://docs.seam.co/core-concepts/workspaces). You can also [filter Connect Webviews by custom metadata](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
48223
48223
|
custom_metadata?:
|
|
48224
48224
|
| {
|
|
48225
48225
|
[x: string]: string | boolean | null
|
|
@@ -48403,7 +48403,7 @@ export type Routes = {
|
|
|
48403
48403
|
customer_key?: string | undefined
|
|
48404
48404
|
/** Your user ID for the user by which you want to filter Connect Webviews. */
|
|
48405
48405
|
user_identifier_key?: string | undefined
|
|
48406
|
-
/** Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string. */
|
|
48406
|
+
/** Custom metadata pairs by which you want to [filter Connect Webviews](https://docs.seam.co/core-concepts/connect-webviews/filtering-connect-webviews-by-custom-metadata). Returns Connect Webviews with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string. */
|
|
48407
48407
|
custom_metadata_has?:
|
|
48408
48408
|
| {
|
|
48409
48409
|
[x: string]: string | boolean
|
|
@@ -48735,7 +48735,7 @@ export type Routes = {
|
|
|
48735
48735
|
commonParams: {
|
|
48736
48736
|
/** Your user ID for the user by which you want to filter connected accounts. */
|
|
48737
48737
|
user_identifier_key?: string | undefined
|
|
48738
|
-
/** Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Specify an empty string to match a key that is unset or set to an empty string. */
|
|
48738
|
+
/** Custom metadata pairs by which you want to filter connected accounts. Returns connected accounts with `custom_metadata` that contains all of the provided key:value pairs. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string. */
|
|
48739
48739
|
custom_metadata_has?:
|
|
48740
48740
|
| {
|
|
48741
48741
|
[x: string]: string | boolean
|
|
@@ -49015,7 +49015,7 @@ export type Routes = {
|
|
|
49015
49015
|
automatically_manage_new_devices?: boolean | undefined
|
|
49016
49016
|
/** Human-readable name for the connected account, shown in the dashboard. For example, `Booking from Airbnb House 1`. */
|
|
49017
49017
|
display_name?: string | undefined
|
|
49018
|
-
/** 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/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
49018
|
+
/** 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, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a connected account](https://docs.seam.co/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/core-concepts/connected-accounts/filtering-connected-accounts-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
49019
49019
|
custom_metadata?:
|
|
49020
49020
|
| {
|
|
49021
49021
|
[x: string]: string | boolean | null
|
|
@@ -52345,7 +52345,7 @@ export type Routes = {
|
|
|
52345
52345
|
created_before?: Date | undefined
|
|
52346
52346
|
/** Your own internal user ID for the user for which you want to list devices. */
|
|
52347
52347
|
user_identifier_key?: string | undefined
|
|
52348
|
-
/** Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Specify an empty string to match a key that is unset or set to an empty string. */
|
|
52348
|
+
/** Set of key:value [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) pairs for which you want to list devices. Key names cannot contain a period (.). Specify an empty string to match a key that is unset or set to an empty string. */
|
|
52349
52349
|
custom_metadata_has?:
|
|
52350
52350
|
| {
|
|
52351
52351
|
[x: string]: string | boolean
|
|
@@ -57277,7 +57277,7 @@ export type Routes = {
|
|
|
57277
57277
|
device_id: string
|
|
57278
57278
|
/** Indicates whether the device is managed. Set this parameter to `true` to convert an unmanaged device to managed. */
|
|
57279
57279
|
is_managed?: true | undefined
|
|
57280
|
-
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
57280
|
+
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
57281
57281
|
custom_metadata?:
|
|
57282
57282
|
| {
|
|
57283
57283
|
[x: string]: string | boolean | null
|
|
@@ -57306,7 +57306,7 @@ export type Routes = {
|
|
|
57306
57306
|
name?: (string | null) | undefined
|
|
57307
57307
|
/** Indicates whether the device is managed. To unmanage a device, set `is_managed` to `false`. */
|
|
57308
57308
|
is_managed?: boolean
|
|
57309
|
-
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs. [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
57309
|
+
/** Custom metadata that you want to associate with the device. Supports up to 50 JSON key:value pairs, with key names up to 40 characters long that cannot contain a period (.). [Adding custom metadata to a device](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) enables you to store custom information, like customer details or internal IDs from your application. Then, you can [filter devices by the desired metadata](https://docs.seam.co/core-concepts/devices/filtering-devices-by-custom-metadata). Set a key to `null` or to an empty string to remove that key from the custom metadata. */
|
|
57310
57310
|
custom_metadata?:
|
|
57311
57311
|
| {
|
|
57312
57312
|
[x: string]: string | boolean | null
|
|
@@ -94944,7 +94944,6 @@ export type Routes = {
|
|
|
94944
94944
|
| 'EXPERIMENTAL_DASHBOARD_API_ENABLED'
|
|
94945
94945
|
| 'ICAL_CONNECTOR'
|
|
94946
94946
|
| 'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS'
|
|
94947
|
-
| 'SALTO_KS_ENTRANCES_ONLY_FOR_SPACES'
|
|
94948
94947
|
| 'SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES'
|
|
94949
94948
|
| 'MANAGE_DEVICES_CONFIRMATION_MODAL'
|
|
94950
94949
|
| 'RECLAIM_ORPHANED_BACKUP_ACCESS_CODES'
|
|
@@ -94966,7 +94965,6 @@ export type Routes = {
|
|
|
94966
94965
|
| 'EXPERIMENTAL_DASHBOARD_API_ENABLED'
|
|
94967
94966
|
| 'ICAL_CONNECTOR'
|
|
94968
94967
|
| 'VISIONLINE_SERIALIZE_BRIDGE_REQUESTS'
|
|
94969
|
-
| 'SALTO_KS_ENTRANCES_ONLY_FOR_SPACES'
|
|
94970
94968
|
| 'SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES'
|
|
94971
94969
|
| 'MANAGE_DEVICES_CONFIRMATION_MODAL'
|
|
94972
94970
|
| 'RECLAIM_ORPHANED_BACKUP_ACCESS_CODES'
|
|
@@ -102353,7 +102351,6 @@ export type Routes = {
|
|
|
102353
102351
|
feature_flags?:
|
|
102354
102352
|
| {
|
|
102355
102353
|
RESERVATION_LEGACY?: boolean | undefined
|
|
102356
|
-
SALTO_KS_ENTRANCES_ONLY_FOR_SPACES?: boolean | undefined
|
|
102357
102354
|
SALTO_KS_DEVICES_AND_ENTRANCES_FOR_SPACES?: boolean | undefined
|
|
102358
102355
|
MANAGE_DEVICES_CONFIRMATION_MODAL?: boolean | undefined
|
|
102359
102356
|
}
|