Create a Connect Webview
Creates a new Connect Webview.
To enable a user to connect their devices or systems to Seam, they must sign in to their device or system account. To enable a user to sign in, you create a connect_webview. After creating the Connect Webview, you receive a URL that you can use to display the visual component of this Connect Webview for your user. You can open an iframe or new window to display the Connect Webview.
You should make a new connect_webview for each unique login request. Each connect_webview tracks the user that signed in with it. You receive an error if you reuse a Connect Webview for the same user twice or if you use the same Connect Webview for multiple users.
See also: Connect Webview Process.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
List of accepted device capabilities that restrict the types of devices that can be connected through the Connect Webview. If not provided, defaults will be determined based on the accepted providers.
High-level device capabilities that can be restricted in connect webviews. These represent the main device categories that customers can opt into.
lock, thermostat, noise_sensor, access_control, camera Accepted device provider keys as an alternative to provider_category. Use this parameter to specify accepted providers explicitly. See Customize the Brands to Display in Your Connect Webviews. To list all provider keys, use /devices/list_device_providers with no filters.
hotek, dormakaba_community, legic_connect, akuvox, august, avigilon_alta, brivo, butterflymx, schlage, smartthings, yale, genie, doorking, salto, salto_ks, 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, latch, akiles, assa_abloy_vostio, assa_abloy_vostio_credential_service, tado, salto_space, sensi, keynest, korelock, dormakaba_ambiance, ultraloq, ring, ical, yale_access, hid_cm, google_nest Indicates whether newly-added devices should appear as managed devices. See also: Customize the Behavior Settings of Your Connect Webviews.
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 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 that were connected using the Connect Webview, making it easy to find and filter these resources in your workspace. You can also filter Connect Webviews by custom metadata.
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.
URL that you want to redirect the user to after the provider login is complete.
Associate the Connect Webview, the connected account, and all resources under the connected account with a customer. If the connected account already exists, it will be associated with the customer. If the connected account already exists, but is already associated with a customer, the Connect Webview will show an error.
1none, single, multiple List of provider keys to exclude from the Connect Webview. These providers will not be shown when the user tries to connect an account.
Specifies the category of providers that you want to include. To list all providers within a category, use /devices/list_device_providers with the desired provider_category filter.
stable, consumer_smartlocks, beta, thermostats, noise_sensors, access_control_systems, cameras, connectors, internal_beta Indicates whether Seam should finish syncing all devices in a newly-connected account before completing the associated Connect Webview. See also: Customize the Behavior Settings of Your Connect Webviews.
Response
OK
Represents a Connect Webview.

