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.
Every call to the API, whether from your server, the SDK or the project MCP server, writes exactly one event, including calls that fail or are refused. Its ID is the Request-Id header on the response. Events are kept for 30 days.
What an event records
| Area | Fields |
|---|---|
| Who | project_id, env, external_user_id, connection_id |
| Which device | device_id, device_kind, vendor, model, firmware, adapter_version |
| What | capability, intent, risk_tier |
| Why there | route_decision with the target, reason and candidates, plus profile_id and profile_version |
| How it went | outcome (ok, error or denied), error_code, confirmation |
| Cost | latency_ms for the API, device delivery and user response, bytes_in, bytes_out, cost_units |
Webhooks
Webhook delivery comes with the developer portal. These are the events it will send; the connection events are already recorded today.
| Event | When |
|---|---|
connection.created, connection.revoked, connection.needs_reauth | A connection changes |
device.online, device.offline | A device comes or goes |
action.completed, action.failed | An action reaches a final status |
ask.answered | The user answers a question |
input.utterance | The user speaks to a device |
Analytics
The developer portal and an analytics API will report active users and devices by kind, your device mix, top capabilities and intents, error rates by vendor and firmware, latency at p50 and p95, where routed messages landed, profile comparisons, and usage for billing.