@seamapi/types 1.887.0 → 1.889.0

package/dist/connect.d.cts

@@ -7329,6 +7329,19 @@ declare const acs_system: z.ZodObject<{
         created_at: string;
         warning_code: "time_zone_does_not_match_location";
         misconfigured_acs_entrance_ids?: string[] | undefined;
+    }>, z.ZodObject<{
+        created_at: z.ZodString;
+        message: z.ZodString;
+    } & {
+        warning_code: z.ZodLiteral<"setup_required">;
+    }, "strip", z.ZodTypeAny, {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
+    }, {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
     }>]>, "many">;
 }, "strip", z.ZodTypeAny, {
     name: string;
@@ -7379,6 +7392,10 @@ declare const acs_system: z.ZodObject<{
         created_at: string;
         warning_code: "time_zone_does_not_match_location";
         misconfigured_acs_entrance_ids?: string[] | undefined;
+    } | {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
     })[];
     image_alt_text: string;
     location: {
@@ -7448,6 +7465,10 @@ declare const acs_system: z.ZodObject<{
         created_at: string;
         warning_code: "time_zone_does_not_match_location";
         misconfigured_acs_entrance_ids?: string[] | undefined;
+    } | {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
     })[];
     image_alt_text: string;
     location: {
@@ -14619,6 +14640,19 @@ declare const connected_account_warning: z.ZodDiscriminatedUnion<"warning_code",
     message: string;
     created_at: string;
     warning_code: "provider_service_unavailable";
+}>, z.ZodObject<{
+    created_at: z.ZodString;
+    message: z.ZodString;
+} & {
+    warning_code: z.ZodLiteral<"setup_required">;
+}, "strip", z.ZodTypeAny, {
+    message: string;
+    created_at: string;
+    warning_code: "setup_required";
+}, {
+    message: string;
+    created_at: string;
+    warning_code: "setup_required";
 }>]>;
 declare const connected_account: z.ZodObject<{
     connected_account_id: z.ZodString;
@@ -14878,6 +14912,19 @@ declare const connected_account: z.ZodObject<{
         message: string;
         created_at: string;
         warning_code: "provider_service_unavailable";
+    }>, z.ZodObject<{
+        created_at: z.ZodString;
+        message: z.ZodString;
+    } & {
+        warning_code: z.ZodLiteral<"setup_required">;
+    }, "strip", z.ZodTypeAny, {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
+    }, {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
     }>]>, "many">;
     custom_metadata: z.ZodRecord<z.ZodString, z.ZodUnion<[z.ZodString, z.ZodBoolean]>>;
     automatically_manage_new_devices: z.ZodBoolean;
@@ -14951,6 +14998,10 @@ declare const connected_account: z.ZodObject<{
         message: string;
         created_at: string;
         warning_code: "provider_service_unavailable";
+    } | {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
     })[];
     custom_metadata: Record<string, string | boolean>;
     automatically_manage_new_devices: boolean;
@@ -15034,6 +15085,10 @@ declare const connected_account: z.ZodObject<{
         message: string;
         created_at: string;
         warning_code: "provider_service_unavailable";
+    } | {
+        message: string;
+        created_at: string;
+        warning_code: "setup_required";
     })[];
     custom_metadata: Record<string, string | boolean>;
     automatically_manage_new_devices: boolean;
@@ -31606,7 +31661,9 @@ type Routes = {
           
           Seam supports programming two types of access codes: [ongoing](https://docs.seam.co/low-level-apis/smart-locks/access-codes#ongoing-access-codes) and [time-bound](https://docs.seam.co/low-level-apis/smart-locks/access-codes#time-bound-access-codes). To differentiate between the two, refer to the `type` property of the access code. Ongoing codes display as `ongoing`, whereas time-bound codes are labeled `time_bound`. An ongoing access code is active, until it has been removed from the device. To specify an ongoing access code, leave both `starts_at` and `ends_at` empty. A time-bound access code will be programmed at the `starts_at` time and removed at the `ends_at` time.
           
-          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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. */
+          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach and work across both standalone smart locks and access systems. Use the lower-level Access Codes API directly only when you specifically need to manage individual PIN codes. */
             access_code: {
                 /** Unique identifier for the Seam workspace associated with the access code. */
                 workspace_id: string;
@@ -34641,7 +34698,9 @@ type Routes = {
           
           Seam supports programming two types of access codes: [ongoing](https://docs.seam.co/low-level-apis/smart-locks/access-codes#ongoing-access-codes) and [time-bound](https://docs.seam.co/low-level-apis/smart-locks/access-codes#time-bound-access-codes). To differentiate between the two, refer to the `type` property of the access code. Ongoing codes display as `ongoing`, whereas time-bound codes are labeled `time_bound`. An ongoing access code is active, until it has been removed from the device. To specify an ongoing access code, leave both `starts_at` and `ends_at` empty. A time-bound access code will be programmed at the `starts_at` time and removed at the `ends_at` time.
           
-          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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. */
+          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach and work across both standalone smart locks and access systems. Use the lower-level Access Codes API directly only when you specifically need to manage individual PIN codes. */
             access_code: {
                 /** Unique identifier for the Seam workspace associated with the access code. */
                 workspace_id: string;
@@ -36034,7 +36093,9 @@ type Routes = {
           
           Seam supports programming two types of access codes: [ongoing](https://docs.seam.co/low-level-apis/smart-locks/access-codes#ongoing-access-codes) and [time-bound](https://docs.seam.co/low-level-apis/smart-locks/access-codes#time-bound-access-codes). To differentiate between the two, refer to the `type` property of the access code. Ongoing codes display as `ongoing`, whereas time-bound codes are labeled `time_bound`. An ongoing access code is active, until it has been removed from the device. To specify an ongoing access code, leave both `starts_at` and `ends_at` empty. A time-bound access code will be programmed at the `starts_at` time and removed at the `ends_at` time.
           
-          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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. */
+          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach and work across both standalone smart locks and access systems. Use the lower-level Access Codes API directly only when you specifically need to manage individual PIN codes. */
             backup_access_code: {
                 /** Unique identifier for the Seam workspace associated with the access code. */
                 workspace_id: string;
@@ -36679,7 +36740,9 @@ type Routes = {
           
           Seam supports programming two types of access codes: [ongoing](https://docs.seam.co/low-level-apis/smart-locks/access-codes#ongoing-access-codes) and [time-bound](https://docs.seam.co/low-level-apis/smart-locks/access-codes#time-bound-access-codes). To differentiate between the two, refer to the `type` property of the access code. Ongoing codes display as `ongoing`, whereas time-bound codes are labeled `time_bound`. An ongoing access code is active, until it has been removed from the device. To specify an ongoing access code, leave both `starts_at` and `ends_at` empty. A time-bound access code will be programmed at the `starts_at` time and removed at the `ends_at` time.
           
-          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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. */
+          In addition, for certain devices, Seam also supports [offline access codes](https://docs.seam.co/low-level-apis/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.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach and work across both standalone smart locks and access systems. Use the lower-level Access Codes API directly only when you specifically need to manage individual PIN codes. */
             access_code: {
                 /** Unique identifier for the Seam workspace associated with the access code. */
                 workspace_id: string;
@@ -44695,6 +44758,13 @@ type Routes = {
                         message: string;
                         /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
                         warning_code: 'provider_service_unavailable';
+                    } | {
+                        /** Date and time at which Seam created the warning. */
+                        created_at: string;
+                        /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                        message: string;
+                        /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                        warning_code: 'setup_required';
                     })[];
                     /** 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. */
                     custom_metadata: {
@@ -44840,6 +44910,13 @@ type Routes = {
                         /**
                          * @deprecated this field is deprecated.*/
                         misconfigured_acs_entrance_ids?: string[] | undefined;
+                    } | {
+                        /** Date and time at which Seam created the warning. */
+                        created_at: string;
+                        /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                        message: string;
+                        /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                        warning_code: 'setup_required';
                     })[];
                 }[] | undefined;
                 user_identities?: {
@@ -54961,7 +55038,9 @@ type Routes = {
           
           An access control system generally uses digital means of access to authorize a user trying to get through a specific entrance. Examples of credentials include plastic key cards, mobile keys, biometric identifiers, and PIN codes. The electronic nature of these credentials, as well as the fact that access is centralized, enables both the rapid provisioning and rescinding of access and the ability to compile access audit logs.
           
-          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type. */
+          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach. Use the lower-level ACS credential API directly only when you specifically need to manage individual credentials. */
             acs_credential: {
                 /** ID of the [credential](https://docs.seam.co/low-level-apis/access-systems/managing-credentials). */
                 acs_credential_id: string;
@@ -55162,7 +55241,9 @@ type Routes = {
           
           An access control system generally uses digital means of access to authorize a user trying to get through a specific entrance. Examples of credentials include plastic key cards, mobile keys, biometric identifiers, and PIN codes. The electronic nature of these credentials, as well as the fact that access is centralized, enables both the rapid provisioning and rescinding of access and the ability to compile access audit logs.
           
-          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type. */
+          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach. Use the lower-level ACS credential API directly only when you specifically need to manage individual credentials. */
             acs_credential: {
                 /** ID of the [credential](https://docs.seam.co/low-level-apis/access-systems/managing-credentials). */
                 acs_credential_id: string;
@@ -55320,7 +55401,9 @@ type Routes = {
           
           An access control system generally uses digital means of access to authorize a user trying to get through a specific entrance. Examples of credentials include plastic key cards, mobile keys, biometric identifiers, and PIN codes. The electronic nature of these credentials, as well as the fact that access is centralized, enables both the rapid provisioning and rescinding of access and the ability to compile access audit logs.
           
-          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type. */
+          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach. Use the lower-level ACS credential API directly only when you specifically need to manage individual credentials. */
             acs_credential: {
                 /** ID of the [credential](https://docs.seam.co/low-level-apis/access-systems/managing-credentials). */
                 acs_credential_id: string;
@@ -55483,7 +55566,9 @@ type Routes = {
           
           An access control system generally uses digital means of access to authorize a user trying to get through a specific entrance. Examples of credentials include plastic key cards, mobile keys, biometric identifiers, and PIN codes. The electronic nature of these credentials, as well as the fact that access is centralized, enables both the rapid provisioning and rescinding of access and the ability to compile access audit logs.
           
-          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type. */
+          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach. Use the lower-level ACS credential API directly only when you specifically need to manage individual credentials. */
             acs_credential: {
                 /** ID of the [credential](https://docs.seam.co/low-level-apis/access-systems/managing-credentials). */
                 acs_credential_id: string;
@@ -56007,7 +56092,9 @@ type Routes = {
           
           An access control system generally uses digital means of access to authorize a user trying to get through a specific entrance. Examples of credentials include plastic key cards, mobile keys, biometric identifiers, and PIN codes. The electronic nature of these credentials, as well as the fact that access is centralized, enables both the rapid provisioning and rescinding of access and the ability to compile access audit logs.
           
-          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type. */
+          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach. Use the lower-level ACS credential API directly only when you specifically need to manage individual credentials. */
             acs_credential: {
                 /** ID of the [credential](https://docs.seam.co/low-level-apis/access-systems/managing-credentials). */
                 acs_credential_id: string;
@@ -56466,7 +56553,9 @@ type Routes = {
           
           An access control system generally uses digital means of access to authorize a user trying to get through a specific entrance. Examples of credentials include plastic key cards, mobile keys, biometric identifiers, and PIN codes. The electronic nature of these credentials, as well as the fact that access is centralized, enables both the rapid provisioning and rescinding of access and the ability to compile access audit logs.
           
-          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type. */
+          For each `acs_credential`, you define the access method. You can also specify additional properties, such as a PIN code, depending on the credential type.
+          
+          For granting a person access to a space, [Access Grants](https://docs.seam.co/use-cases/granting-access) are the default and recommended approach. Use the lower-level ACS credential API directly only when you specifically need to manage individual credentials. */
             acs_credential: {
                 /** ID of the [credential](https://docs.seam.co/low-level-apis/access-systems/managing-credentials). */
                 acs_credential_id: string;
@@ -64218,6 +64307,13 @@ type Routes = {
                     /**
                      * @deprecated this field is deprecated.*/
                     misconfigured_acs_entrance_ids?: string[] | undefined;
+                } | {
+                    /** Date and time at which Seam created the warning. */
+                    created_at: string;
+                    /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                    message: string;
+                    /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                    warning_code: 'setup_required';
                 })[];
             };
         };
@@ -64361,6 +64457,13 @@ type Routes = {
                     /**
                      * @deprecated this field is deprecated.*/
                     misconfigured_acs_entrance_ids?: string[] | undefined;
+                } | {
+                    /** Date and time at which Seam created the warning. */
+                    created_at: string;
+                    /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                    message: string;
+                    /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                    warning_code: 'setup_required';
                 })[];
             }[];
         };
@@ -64500,6 +64603,13 @@ type Routes = {
                     /**
                      * @deprecated this field is deprecated.*/
                     misconfigured_acs_entrance_ids?: string[] | undefined;
+                } | {
+                    /** Date and time at which Seam created the warning. */
+                    created_at: string;
+                    /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                    message: string;
+                    /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                    warning_code: 'setup_required';
                 })[];
             }[];
         };
@@ -70403,6 +70513,13 @@ type Routes = {
                     message: string;
                     /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
                     warning_code: 'provider_service_unavailable';
+                } | {
+                    /** Date and time at which Seam created the warning. */
+                    created_at: string;
+                    /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                    message: string;
+                    /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                    warning_code: 'setup_required';
                 })[];
                 /** 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. */
                 custom_metadata: {
@@ -70586,6 +70703,13 @@ type Routes = {
                     message: string;
                     /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
                     warning_code: 'provider_service_unavailable';
+                } | {
+                    /** Date and time at which Seam created the warning. */
+                    created_at: string;
+                    /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                    message: string;
+                    /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                    warning_code: 'setup_required';
                 })[];
                 /** 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. */
                 custom_metadata: {
@@ -70803,6 +70927,13 @@ type Routes = {
                     message: string;
                     /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
                     warning_code: 'provider_service_unavailable';
+                } | {
+                    /** Date and time at which Seam created the warning. */
+                    created_at: string;
+                    /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                    message: string;
+                    /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                    warning_code: 'setup_required';
                 })[];
                 /** 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. */
                 custom_metadata: {
@@ -113257,6 +113388,13 @@ type Routes = {
                         message: string;
                         /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
                         warning_code: 'provider_service_unavailable';
+                    } | {
+                        /** Date and time at which Seam created the warning. */
+                        created_at: string;
+                        /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                        message: string;
+                        /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                        warning_code: 'setup_required';
                     })[];
                     /** 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. */
                     custom_metadata: {
@@ -113402,6 +113540,13 @@ type Routes = {
                         /**
                          * @deprecated this field is deprecated.*/
                         misconfigured_acs_entrance_ids?: string[] | undefined;
+                    } | {
+                        /** Date and time at which Seam created the warning. */
+                        created_at: string;
+                        /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                        message: string;
+                        /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                        warning_code: 'setup_required';
                     })[];
                 }[] | undefined;
                 access_methods?: {
@@ -137040,6 +137185,13 @@ type Routes = {
                     /**
                      * @deprecated this field is deprecated.*/
                     misconfigured_acs_entrance_ids?: string[] | undefined;
+                } | {
+                    /** Date and time at which Seam created the warning. */
+                    created_at: string;
+                    /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                    message: string;
+                    /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                    warning_code: 'setup_required';
                 })[];
             }[];
         };
@@ -139570,6 +139722,13 @@ type Routes = {
                         /**
                          * @deprecated this field is deprecated.*/
                         misconfigured_acs_entrance_ids?: string[] | undefined;
+                    } | {
+                        /** Date and time at which Seam created the warning. */
+                        created_at: string;
+                        /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                        message: string;
+                        /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                        warning_code: 'setup_required';
                     })[];
                 }[] | undefined;
                 acs_users?: {
@@ -143066,6 +143225,13 @@ type Routes = {
                         message: string;
                         /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
                         warning_code: 'provider_service_unavailable';
+                    } | {
+                        /** Date and time at which Seam created the warning. */
+                        created_at: string;
+                        /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
+                        message: string;
+                        /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
+                        warning_code: 'setup_required';
                     })[];
                     /** 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. */
                     custom_metadata: {