Live API

Use the Live API for a direct voice conversation with resia-fullplex-1. A WebSocket carries audio, transcripts, and commands in both directions. HTTP endpoints return your organization's session records, charges, recordings, and available voices.

Reference Contents
Connect a live session Authentication, session start parameters, audio formats, and delegation settings.
Session events Client commands, server events, and errors.
Session records and voices HTTP parameters, response fields, and errors.

Access and cost

Complete Get access before you connect. An API key needs editor or owner scope to open a paid session. A reader key cannot open one.

See Fullplex prices for live sessions and telephone calls. See Billing for balances and charges.

The default limit is five concurrent live sessions per organization. GET /v1/rate-limits reports fullplex.concurrent_sessions and fullplex.in_progress. See Rate limits.

A session lasts at most 3,600 seconds. A session with no audio input ends 30 seconds after session.started. Send session.close to end a session sooner.

Stored audio

Set session.store to true to save a stereo recording. The left channel contains input audio; the right channel contains output audio. The recording becomes available after the session closes and stays until it is deleted. An absent or false store value saves no session recording. See Session records and voices.