API
TelAPI — the Delphi REST and WebSocket gateway. Two real surfaces (the browser & SDK API and the async LLM webhook), an open health check, and a shared error model.
TelAPI — the Delphi REST and WebSocket gateway. Two real surfaces (the browser & SDK API and the async LLM webhook), an open health check, and a shared error model.
API keys for external systems — primarily WebRTC call tokens. Feature-gated and only visible when API access is enabled for the team.
Status of the generated, interactive TelAPI reference (Swagger view) and how an export is produced from a platform release.
API server instance scaling and platform-wide request rate limiting.
TelAPI Fastify HTTP/WebSocket API behind a managed load balancer — operations, runbook, configuration, troubleshooting.
How requests to the browser & SDK API are authenticated — tenant-scoped API keys, the bearer header, what a key is bound to, and rotation.
The slice of TelAPI that browser/mobile clients (via the official SDK) talk to — call tokens, the WebSocket channel, conversations, and the API-key auth model behind them. Gated by the `webrtc` feature flag.
The short-lived tokens your backend mints with TelAPI and hands to a client to start a WebRTC call.
How a finished call surfaces as data — the conversation concept that anchors the rest of the API surface.
The TelAPI error envelope, common status codes, and which errors are safe to retry.
End-to-end recipes — mint a call token, post an async LLM callback, retry safely. Snippets to start a real integration.
What each TelAPI scope grants. Scopes are selected when a key is created and cannot be elevated later.
The inbound /api/v1/webhooks endpoint where an async LLM or tool delivers its response back into a live Delphi conversation. Uses its own per-callback auth, not the API-key bearer model.
The realtime control + media channel used by Delphi SDK sessions. You almost never speak to it directly — but understanding it explains everything downstream.