Events and analytics Beta

One event for every call, recorded from the first request

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

AreaFields
Whoproject_id, env, external_user_id, connection_id
Which devicedevice_id, device_kind, vendor, model, firmware, adapter_version
Whatcapability, intent, risk_tier
Why thereroute_decision with the target, reason and candidates, plus profile_id and profile_version
How it wentoutcome (ok, error or denied), error_code, confirmation
Costlatency_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.

EventWhen
connection.created, connection.revoked, connection.needs_reauthA connection changes
device.online, device.offlineA device comes or goes
action.completed, action.failedAn action reaches a final status
ask.answeredThe user answers a question
input.utteranceThe 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.