End users and connections Beta

Your users stay yours, and each device they link becomes a connection

Beta. The Device SDK is live for design partners: Dopl issues your project's keys while the developer portal is being built, and @dopl/sdk is available on request. Agents that act for one signed in Dopl user can use the hosted MCP server instead.

An end user is one of your users, identified by your own ID as external_user_id. End users never sign up with Dopl. They belong to your app, the way a bank customer never signs up with the service that links their account. Dopl creates the end user the first time you open a Connect session for that ID.

Connections

A connection is one user's grant to one device. Your server holds the opaque connection ID, while device credentials stay in the Dopl vault and never reach your servers or your agent.

StatusMeaning
activeThe device is reachable within the granted scopes
needs_reauthThe user must reconnect the device before Dopl can reach it
revokedYou revoked it, and nothing reaches the device

Each connection lists its grants: a capability scope such as present.*, when it was granted and when it expires, if ever.

How a user connects

  1. Your server creates a Connect session for the user with the scopes your agent needs. The session's link works for 30 minutes.
  2. The user opens the hosted page, which carries your name, logo and accent color, and chooses a device. Each option shows how many of your requested scopes that device supports.
  3. They pair it the way that device pairs. Even Realities G2 glasses show a code on the lens that the user types into the page; a simulated device shows its code on the page.
  4. They approve the scopes, grouped by risk tier. T0 and T1 scopes start ticked and everything from T2 up starts unticked, and the user can grant any subset.
  5. The page returns to your redirect_uri with a one time public_token, which your server exchanges for the connection within 30 minutes.

Connect a device walks through it with code. Revoking a connection takes effect immediately, and revoking one that is already revoked returns it unchanged.

Webhooks

Dopl records connection.created and connection.revoked for every connection today. Delivering them to a URL you register comes with the developer portal, together with connection.needs_reauth, device.online and device.offline.