API Reference
Authentication and core endpoints from the Dialit backend.
Use the authenticated backend.
Workspace requests use a valid Supabase bearer session, checked by the API. Never put provider keys, service-role credentials or a backend secret in a browser bundle. Your deployed API base URL is supplied with your workspace configuration.
These paths are present in the checked backend source. This reference does not issue credentials or prove access to a production route.
| Method & path | Purpose |
|---|---|
GET /api/v1/auth/me | Read the authenticated account. |
GET /api/v1/agents | List agents accessible to this account. |
GET /api/v1/templates | Read the template catalogue. |
GET /api/v1/integrations | List accessible configured integrations. |
GET /api/v1/calls | Read accessible call records. |
GET /api/v1/calls/{call_id}/intelligence | Read available messages, analysis and timeline. |
POST /api/v1/calls/dispatch | Request an authorized outbound call; not a demo or free read operation. |
Read-only example
GET /api/v1/auth/me
Authorization: Bearer <your current session access token>Supply the actual backend host privately in your client configuration. Do not paste session tokens in support messages.
Dispatch is an explicit side effect
The dispatch route accepts an agent ID and destination, and supports an Idempotency-Key header. It returns an accepted/queued state, not proof that the phone rang or audio worked. Entitlement, runtime and concurrency checks still apply. Never send a test request to a live destination without approval.
Errors and provider callbacks
An expired or invalid session must not be treated as an empty account. Handle authorization, validation, account limits and provider failures visibly. Callback authentication is provider-specific and configured server-side; do not emulate a provider callback as a production test.