Embedding a Connect Webview in Your App

• Redirect to the Connect Webview URL. Recommended.
• Embed the Connect Webview in an inline frame (iframe).

​

Step 1: Open a Connect Webview

​

Step 2: Display the Connect Webview

​

Redirect to the Connect Webview URL

1. Create the Connect Webview.
   • Make sure to set a custom_redirect_url so that the Connect Webview redirects back to the desired page within your app after the Connect Webview flow completes. This is required for a redirect flow. Without it, the Connect Webview finishes on a success screen that asks the user to close the window—and a page your app navigated to cannot close itself or return the user to your app. Seam can only close the window automatically when Seam itself opened the Connect Webview in a popup.
   • If you want to redirect to a different page when there is an error, you can set the custom_redirect_failure_url to the URL for the desired page.
   • We recommend setting wait_for_device_creation to true so that the Connect Webview does not complete until Seam completes the first sync of the connected account and devices or ACS.
2. Redirect your app to the URL for the created Connect Webview.
   Pass the Connect Webview url to the client portion of your app and redirect your app to this URL.
   The resulting page displays the authorization flow through which your app user can link their device or ACS account to Seam.\ Once the user has completed the authorization flow, the Connect Webview redirects back to your app (specifically to the custom_redirect_url). Note that Seam appends the following search parameters to the URL after the redirect:
   • connect_webview_id
   • If there is an error, error_code and error_message
3. Your user completes the Connect Webview authorization flow.
4. Learn when the device or ACS account connection has completed successfully.
5. Retrieve the devices or ACS that your user has just connected to Seam.
6. Use the Seam API to control your users’ connected devices or ACS.

​

Embed the Connect Webview in an iframe

1. Create the Connect Webview.
   We recommend setting wait_for_device_creation to true so that the Connect Webview does not complete until Seam completes the first sync of the connected account and devices or ACS.
2. Display the URL for the created Connect Webview in an iframe.
   Pass the Connect Webview url to the client portion of your app and use an HTML iframe to display the Connect Webview URL. For example:
   <iframe
     style="border: none;min-height: 600px;height: 100%;width: 100%"
     allow="clipboard-write"
     src="<your connect_webview.url>"
   />
   
3. Your user completes the Connect Webview authorization flow.
   Provider behavior limits what an iframe can do, and Seam cannot abstract it away:

   • Some providers move to a new tab partway through their authentication flow for security reasons.
   • Some providers refuse to load their login page in an iframe at all, which breaks the connection flow for that brand. Nuki is one known example.

   Because each provider controls this, a brand that embeds correctly today can stop doing so after a provider-side update, with no change on your part and no warning from Seam. If you support more than a handful of brands, prefer the full-page redirect.
4. Learn when the device or ACS account connection has completed successfully.
   When the connection completes successfully, you can close the iframe.
5. Retrieve the devices or ACS that your user has just connected to Seam.
6. Use the Seam API to control your users’ connected devices or ACS.

​

Opening Connect Webviews in iOS or Android Apps

someWebView.navigationDelegate = self

extension YourViewController: WKNavigationDelegate {
func webView(_ webView: WKWebView, decidePolicyFor navigationAction: WKNavigationAction, decisionHandler: @escaping (WKNavigationActionPolicy) -> Void) {
if let url = navigationAction.request.url, navigationAction.navigationType == .linkActivated {
if (url.host != "getseam.com" || url.host != "seam.co") {
UIApplication.shared.open(url)
decisionHandler(.cancel)
return
}
}
decisionHandler(.allow)
}
}

webView.webViewClient = object : WebViewClient() {
  override fun shouldOverrideUrlLoading(view: WebView, url: String): Boolean {
    if (Uri.parse(url).host != "getseam.com" || Uri.parse(url).host != "seam.co") {
      val intent = Intent(Intent.ACTION_VIEW, Uri.parse(url))
      view.context.startActivity(intent)
      return true
    }
    return false
  }
}

• iOS WKNavigationDelegate
• Android shouldOverrideUrlLoading