Reecall
Core Concepts

Channels & Calls

A Channel stores the connection and routing configuration for an Assistant. Reuse it for successive calls. An individual call is a live conversation, recorded as an Exchange.

Choose a Channel type

ChannelConnectsSetup
SIPCallers using your phone system or SIP providerConfigure permitted destination numbers or source addresses, and route SIP traffic to Reecall
WebRTCCallers in a browser or applicationCreate a Channel, request a connection token on your backend, and connect with a LiveKit client

Each Channel points to one Assistant through assistantId. An Assistant can have one SIP Channel and one WebRTC Channel. A second Channel of the same type for that Assistant is rejected.

Phone calls through SIP

Creating a SIP Channel provisions its inbound trunk and routing configuration. Configure at least one non-empty whitelist of destination phone numbers or permitted source IP addresses. Your phone system or SIP provider must then send calls to the provisioned endpoint.

The Channel connects an existing telephony setup to the Assistant. Creating it does not purchase a phone number or configure your provider for you.

See the SIP Channel guide for routing and whitelist configuration.

Browser and app calls through WebRTC

For each new conversation, your backend sends POST /calls/{channelId} using a Reecall API key. The response contains a LiveKit WebSocket URL, wsUrl, and a room-scoped connection token with a one-hour lifetime.

The browser connects to LiveKit with these values, publishes microphone audio, and plays the Assistant's audio. Requesting a token prepares the connection; the browser still needs to join and enable its microphone.

Keep the Reecall API key on your backend

Pass only wsUrl and the connection token to the browser. A LiveKit token grants access to the call's room; it does not replace your Reecall API key for managing resources.

Use the Quickstart for a working browser example, or the WebRTC Channel guide for integration details.

Keep resource IDs distinct

IDIdentifiesUsed for
assistantIdThe Assistant configurationAssigning an Assistant to a Channel
channelIdThe reusable connection configurationRequesting a WebRTC connection token
exchangeIdA conversation recordReading the transcript and results for one call

The Calls API returns connection credentials. It does not return an Exchange ID. Read conversation records through the Data API after the Assistant starts handling the call.

Next steps

Last modified on