Coviu Telehealth Video API

Name: Coviu Telehealth Video API
Brand: Coviu Telehealth Video API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareAppointment Schedulingoauth2, basic, bearer20 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Coviu Telehealth Video API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Coviu Telehealth Video API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Coviu Telehealth Video API.

Create scheduled or on-demand video consultation sessions for clinicians and patients

Add and remove participants from an active telehealth session

List currently waiting calls for a clinic team and route them to the right practitioner

GET STARTED

Start building with Coviu Telehealth Video API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Coviu Telehealth Video API, keeping it validated and agent-ready. The Coviu API powers the Coviu telehealth video platform, used by clinicians and allied health practices for secure video consultations. It exposes operations for creating and managing video sessions, adding and removing participants, monitoring waiting room queues, and retrieving collections data including submission files and audio recordings. Authentication is via OAuth 2.0 client credentials, HTTP Basic, or bearer token, depending on the integration model.

Use Cases

Patterns agents use Coviu Telehealth Video API for, with concrete tasks.

★ Telehealth Appointment Scheduling

A clinic's practice management system creates a Coviu video session for each scheduled telehealth appointment. POST /sessions returns a session URL that is sent to the patient by SMS or email and embedded into the clinician's calendar. When the appointment is rescheduled, PUT /sessions/{session_id} updates the time without forcing a new link. This keeps the patient-facing URL stable and avoids confusion on the day of the call.

Call POST /sessions with {start: '2026-06-11T10:00:00Z', duration: 30, hostName: 'Dr Patel'} and email the returned roomUrl to the patient.

Waiting Room Triage

When patients arrive in the Coviu waiting room, a triage agent or receptionist polls GET /waiting/{teamId} to see who is queued, then routes each caller to the right clinician. The endpoint returns wait time and queue assignment so a dashboard can highlight long waits and prompt staff to admit or reassign callers. This avoids patients dropping off because nobody noticed they were ready.

Call GET /waiting/{teamId} every 30 seconds and post a Slack alert if any caller has been waiting longer than 5 minutes.

Clinical Collections and Recordings

After a consultation, structured intake forms and audio recordings are stored as submissions inside a Coviu collection. A back-office workflow uses GET /collections/{teamId}/collection/{collectionId} to enumerate submissions and then downloads each file via GET /collections/{teamId}/collection/{collectionId}/submission/{submissionId}/file/{fileId} for archival into the clinic's EHR. This automates record keeping without exposing patient data to staff inboxes.

List submissions for collection 'intake-2026' on team 'sunshine-clinic', then download every audio recording from the last 24 hours and upload to S3 bucket 'clinic-archive'.

Agent-Driven Video Session Lifecycle

An AI scheduling agent embedded in a clinic's chat workflow handles end-to-end session lifecycle: it creates a Coviu session when a patient confirms an appointment, adds the participant, monitors the waiting room, and retrieves the session summary for billing once the call ends. Through Jentic, the agent finds each Coviu operation by intent and executes it without holding raw OAuth credentials.

Search Jentic for 'create telehealth session', execute POST /sessions, then POST /sessions/{id}/participants for the patient, and finally GET /sessions/{id}/summary after the call closes.

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for coviu telehealth video api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/sessions

Create a new video session

GET

/sessions/{session_id}

Get a specific session

POST

/sessions/{session_id}/participants

Add a participant to a session

GET

/waiting/{teamId}

List currently waiting calls

GET

/sessions/{session_id}/summary

Retrieve session summary data

POST

/auth/token

Obtain access token via OAuth client credentials

POST

/sessions

Create a new video session

GET

/sessions/{session_id}

Get a specific session

POST

/sessions/{session_id}/participants

Add a participant to a session

GET

/waiting/{teamId}

List currently waiting calls

GET

/sessions/{session_id}/summary

Retrieve session summary data

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Coviu credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a telehealth session' or 'add a participant to a session', and Jentic returns the matching Coviu operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Coviu Telehealth Video API through Jentic.

Why is there no official OpenAPI spec for Coviu Telehealth Video API?

Coviu does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Coviu Telehealth Video API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Coviu Telehealth Video API use?

Coviu supports OAuth 2.0 client credentials, HTTP Basic with client ID and client secret, or bearer token. The token endpoint is POST /auth/token. Through Jentic, credentials are stored encrypted and the bearer token is fetched and rotated automatically.

Can I create a video consultation through the Coviu API?

Yes. POST /sessions creates a new session and returns a roomUrl that the patient and clinician load to start the call. Optional parameters control duration, host name, and recording settings.

How do I monitor the Coviu waiting room programmatically?

Call GET /waiting/{teamId} to list everyone currently queued, or GET /waiting/{teamId}/queue/{queueId} for a specific queue. The response includes how long each caller has been waiting, which is useful for triage dashboards.

What are the rate limits for the Coviu API?

The OpenAPI spec does not declare numeric rate limits. Coviu enforces fair-use limits in production; in practice polling endpoints like /waiting at 30-60 second intervals is safe. Back off on 429 responses.

How do I download a recording from a completed session through Jentic?

Search Jentic for 'download coviu recording', load the GET /collections/{teamId}/collection/{collectionId}/recording/{submissionId} schema, and execute with the team and submission identifiers. Jentic streams the audio file response back to the agent.

Can I limit what my agent is allowed to do with the Coviu Telehealth Video API?

Yes. Jentic One runs self-hosted, so your own rules decide which Coviu operations and credentials the agent may use. Because Coviu puts the session id in the URL path, such as /sessions/{session_id}/participants and /sessions/{session_id}/summary, you can pin the agent to a single session so it acts only on that call. You also choose the operations it may reach, keeping it to the reads and updates you allow, for example letting it monitor GET /waiting/{teamId} without granting it POST /sessions.

Coviu Telehealth Video API

Connect the Coviu Telehealth Video API to your agent

Capabilities

Start building with Coviu Telehealth Video API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs