Skip to main content
POST
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

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
accepted_capabilities
enum<string>[]

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.

Available options:
lock,
thermostat,
noise_sensor,
access_control,
camera
accepted_providers
enum<string>[]

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.

Available options:
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,
dormakaba_oracode_iho,
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,
tapo,
arlo,
reolink,
ical,
lodgify,
hostaway,
guesty,
acuity_scheduling,
omnitec,
kisi,
aqara,
yale_access,
hid_cm,
google_nest,
slack
automatically_manage_new_devices
boolean

Indicates whether newly-added devices should appear as managed devices. See also: Customize the Behavior Settings of Your Connect Webviews.

custom_metadata
object

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 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. Set a key to null or to an empty string to remove that key from the custom metadata.

custom_redirect_failure_url
string

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.

custom_redirect_url
string

URL that you want to redirect the user to after the provider login is complete.

customer_key
string

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.

Minimum string length: 1
excluded_providers
string[]

List of provider keys to exclude from the Connect Webview. These providers will not be shown when the user tries to connect an account.

provider_category
enum<string>

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.

Available options:
stable,
consumer_smartlocks,
beta,
thermostats,
noise_sensors,
access_control_systems,
cameras,
connectors,
internal_beta
wait_for_device_creation
boolean
default:false

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

connect_webview
object
required