@seamapi/http 2.11.1 → 2.12.0

package/src/lib/resources/phone.ts

@@ -15,7 +15,7 @@ export type Phone = {
   /**
    * Optional [custom metadata](https://docs.seam.co/core-concepts/devices/adding-custom-metadata-to-a-device) for the phone.
    */
-  custom_metadata: Record<string, unknown>
+  custom_metadata: Record<string, string | boolean>
 
   /**
    * ID of the phone.

package/src/lib/resources/unmanaged-device.ts

@@ -112,7 +112,7 @@ export type UnmanagedDevice = {
   /**
    * Set of key:value pairs. Adding custom metadata to a resource, such as a [Connect Webview](https://docs.seam.co/core-concepts/connect-webviews/attaching-custom-data-to-the-connect-webview), [connected account](https://docs.seam.co/core-concepts/connected-accounts/adding-custom-metadata-to-a-connected-account), or [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. Keys set to `null` or to an empty string are omitted.
    */
-  custom_metadata: Record<string, unknown>
+  custom_metadata: Record<string, string | boolean>
 
   /**
    * ID of the device.

package/src/lib/routes/connect-webviews/connect-webviews.ts

@@ -336,7 +336,7 @@ export type ConnectWebviewsCreateParameters = {
   /**
    * 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.
    */
-  custom_metadata?: Record<string, unknown> | undefined
+  custom_metadata?: Record<string, string | boolean> | undefined
   /**
    * Alternative URL that you want to redirect the user to on an error. If you do not set this parameter, the Connect Webview falls back to the `custom_redirect_url`.
    */
@@ -424,7 +424,7 @@ export type ConnectWebviewsListParameters = {
   /**
    * 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 `null` to match a key that is unset. A key given an empty string is omitted from the filter.
    */
-  custom_metadata_has?: Record<string, unknown> | undefined
+  custom_metadata_has?: Record<string, string | boolean> | undefined
   /**
    * Customer key for which you want to list connect webviews.
    */

package/src/lib/routes/connected-accounts/connected-accounts.ts

@@ -313,7 +313,7 @@ export type ConnectedAccountsListParameters = {
   /**
    * 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 `null` to match a key that is unset. A key given an empty string is omitted from the filter.
    */
-  custom_metadata_has?: Record<string, unknown> | undefined
+  custom_metadata_has?: Record<string, string | boolean> | undefined
   /**
    * Customer key by which you want to filter connected accounts.
    */
@@ -391,7 +391,7 @@ export type ConnectedAccountsUpdateParameters = {
   /**
    * 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.
    */
-  custom_metadata?: Record<string, unknown> | undefined
+  custom_metadata?: Record<string, string | boolean> | undefined
   /**
    * 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. May only be provided if the connected account is not already associated with a customer.
    */

package/src/lib/routes/customers/customers.ts

@@ -728,7 +728,7 @@ export type CustomersCreatePortalParameters = {
               /**
                * Set key:value pairs. Accepts string or Boolean values. Adding custom metadata to a property listing enables you to store custom information, like customer details or internal IDs from your application. Set a key to `null` or to an empty string to remove that key from the custom metadata.
                */
-              custom_metadata?: Record<string, unknown> | undefined
+              custom_metadata?: Record<string, string | boolean> | undefined
               /**
                * Your display name for this location resource.
                */
@@ -755,7 +755,7 @@ export type CustomersCreatePortalParameters = {
               /**
                * Set key:value pairs for filtering reservations by custom criteria. Set a key to `null` or to an empty string to remove that key from the custom metadata.
                */
-              custom_metadata?: Record<string, unknown> | undefined
+              custom_metadata?: Record<string, string | boolean> | undefined
               /**
                * Ending date and time for the access grant.
                */
@@ -1469,7 +1469,7 @@ export type CustomersPushDataParameters = {
         /**
          * Set key:value pairs. Accepts string or Boolean values. Adding custom metadata to a property listing enables you to store custom information, like customer details or internal IDs from your application. Set a key to `null` or to an empty string to remove that key from the custom metadata.
          */
-        custom_metadata?: Record<string, unknown> | undefined
+        custom_metadata?: Record<string, string | boolean> | undefined
         /**
          * Your display name for this location resource.
          */
@@ -1496,7 +1496,7 @@ export type CustomersPushDataParameters = {
         /**
          * Set key:value pairs for filtering reservations by custom criteria. Set a key to `null` or to an empty string to remove that key from the custom metadata.
          */
-        custom_metadata?: Record<string, unknown> | undefined
+        custom_metadata?: Record<string, string | boolean> | undefined
         /**
          * Ending date and time for the access grant.
          */

package/src/lib/routes/devices/devices.ts

@@ -315,7 +315,7 @@ export type DevicesListParameters = {
   /**
    * 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 `null` to match a key that is unset. A key given an empty string is omitted from the filter.
    */
-  custom_metadata_has?: Record<string, unknown> | undefined
+  custom_metadata_has?: Record<string, string | boolean> | undefined
   /**
    * Customer key for which you want to list devices.
    */
@@ -1899,7 +1899,7 @@ export type DevicesUpdateParameters = {
   /**
    * 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.
    */
-  custom_metadata?: Record<string, unknown> | undefined
+  custom_metadata?: Record<string, string | boolean> | undefined
   /**
    * ID of the device that you want to update.
    */

package/src/lib/routes/devices/unmanaged/unmanaged.ts

@@ -458,7 +458,7 @@ export type DevicesUnmanagedUpdateParameters = {
   /**
    * 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.
    */
-  custom_metadata?: Record<string, unknown> | undefined
+  custom_metadata?: Record<string, string | boolean> | undefined
   /**
    * ID of the unmanaged device that you want to update.
    */

package/src/lib/version.ts

@@ -1,3 +1,3 @@
-const seamapiJavascriptHttpVersion = '2.11.1'
+const seamapiJavascriptHttpVersion = '2.12.0'
 
 export default seamapiJavascriptHttpVersion