Skip to main content
Seam provides shared test accounts for every manufacturer it supports, so you can connect virtual devices in a sandbox workspace and build your integration without any physical hardware. When you connect a device—in the Seam Console or through a Connect Webview—enter the test-account credentials below instead of real manufacturer credentials.

​
The standard sandbox login

Most manufacturers accept the same test-account login: Use jane@example.com exactly. Some providers accept any address in the example.com domain and create an account on the fly, but many only accept a specific seeded address, so an arbitrary address is not a safe default. A few providers seed a different address instead—Genie, for example, expects john@example.com. If a sandbox login is rejected, check that brand’s sandbox guide for the exact accounts it accepts.

​
Two-factor prompts

Most providers never ask for a verification code. The ones that do accept 123456:
  • August
  • Yale Home
  • Latch
  • Avigilon Alta—only for its MFA-enabled test account.
These are shared, non-secret sandbox fixtures. They work only in sandbox workspaces and grant no access to real accounts or devices, so they are safe to commit to code and share with your team.

​
Brands that need extra credentials

The following integrations require something beyond the standard login—an API key, an additional field, or extra setup steps. See each brand’s sandbox guide for the exact values to enter.

​
Per-brand details

Each manufacturer’s sandbox guide lists its exact accepted accounts and the virtual devices pre-seeded with each one. To trigger test events on a virtual device or reset a sandbox workspace, see Sandbox Workspaces.