C2c Mirotalk MiroTalk C2C API
★ Only Publicly Available OpenAPI DocumentCommunicationsVideo ConferencingapiKey2 EndpointsREST
For Agents
Create on-demand video meetings and generate participant join links via the MiroTalk C2C peer-to-peer video calling API.
Use for: I need to create a new MiroTalk video meeting on demand, Generate a join link for a participant in an existing meeting, Set up a one-off video room for a customer support session, Spin up a peer-to-peer video call between two users
Not supported: Does not handle recording storage, screen sharing controls, or chat transcripts — use for creating MiroTalk meetings and issuing join links only.
Jentic publishes the only available OpenAPI specification for MiroTalk C2C API, keeping it validated and agent-ready. MiroTalk C2C is a peer-to-peer video calling platform; the API lets external applications spin up a meeting on demand and hand the user a direct join link without operating their own signalling infrastructure. Two operations are exposed: POST /meeting to create a new meeting and POST /join to generate a join URL for a participant. Authentication is an API key secret passed in the Authorization header, which makes this a small, drop-in video integration for support tools, telehealth flows, or scheduled coaching sessions.
Install Jentic One Beta
Connect the MiroTalk C2C API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MiroTalk C2C 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.
1
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 | sh2
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 instanceJentic 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 MiroTalk C2C API.
Create a new MiroTalk meeting room by posting to /meeting
Generate a participant join link for a meeting via /join
Embed peer-to-peer video calls into support, coaching, or telehealth flows
Authorize requests using an API key secret in the Authorization header
Hand the user a direct join URL without running signalling infrastructure
Use Cases
Patterns agents use MiroTalk C2C API for, with concrete tasks.
★ On-Demand Customer Support Video Call
When a support agent escalates a chat to video, the application calls POST /meeting to create a room and POST /join to obtain the customer's join link, then sends the link in the chat thread. The customer joins from the browser without installing software, and the agent joins from their support console. Each call uses a fresh room so links cannot be reused after the session ends.
POST to /meeting to create a room, POST to /join with the customer name to get the join URL, and reply in chat with that URL.
Telehealth Appointment Join Links
Generate a unique meeting per appointment so the patient and clinician each receive their own join link near the appointment time. Because rooms are created per session there is no shared persistent link to leak, and the API is light enough to call from a scheduling worker without operational overhead.
On the appointment trigger, POST /meeting and then POST /join twice to issue separate join URLs for the patient and clinician.
Coaching and 1:1 Session Rooms
For coaching platforms or 1:1 SaaS, create a meeting per scheduled session and provide each participant with a join link in their email or in-app calendar entry. The two-endpoint surface keeps the integration trivially small while still supporting per-session room creation and per-participant join URLs.
POST /meeting at session creation, then POST /join for each participant and attach the resulting URLs to the session record.
AI Agent Video Session Setup via Jentic
Through Jentic, an AI assistant searches for an intent like 'create a video meeting' and is returned the MiroTalk C2C operation along with its input schema. The agent calls POST /meeting and then POST /join without ever holding the raw Authorization header value. Setup is under an hour rather than several days of direct integration.
Use Jentic search for 'create a video meeting', execute /meeting to create the room, then execute /join for each participant.
Key Endpoints
2 endpoints — jentic publishes the only available openapi specification for mirotalk c2c api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/meeting
Create a new MiroTalk meeting room
POST
/join
Generate a participant join link
POST
/meeting
Create a new MiroTalk meeting room
POST
/join
Generate a participant join link
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The MiroTalk C2C Authorization header secret is held encrypted in the Jentic vault. Agents call /meeting and /join by name and Jentic injects the secret at execution time — the raw key never enters the agent prompt or logs.
Intent-based discovery
Agents search Jentic by intent (for example 'create a video meeting' or 'generate a join link') and Jentic returns the matching MiroTalk C2C operation with its input schema, so the agent can call the right endpoint without browsing MiroTalk documentation.
Time to first call
Direct MiroTalk C2C integration: half a day to wire up the two operations and handle Authorization header rotation. Through Jentic: under 30 minutes — search for the operation, load its schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using MiroTalk C2C API through Jentic.
Why is there no official OpenAPI spec for MiroTalk C2C API?
MiroTalk C2C documents the API as a docs page rather than publishing a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MiroTalk C2C API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the MiroTalk C2C API use?
The MiroTalk C2C API uses an API key secret passed in the Authorization HTTP header. Through Jentic, the secret is stored encrypted in the credential vault and injected at execution time, so the agent never holds the raw value.
Can I create a video meeting on demand with the MiroTalk C2C API?
Yes. POST to /meeting to create a new peer-to-peer meeting room, then POST to /join with the participant details to generate a direct join URL. Each meeting is a distinct room rather than a shared persistent link.
What are the rate limits for the MiroTalk C2C API?
The OpenAPI specification does not declare rate limits. Because MiroTalk C2C is a peer-to-peer service the bottleneck is usually the participant browsers rather than the signalling API itself, but check the MiroTalk operator settings before scheduling burst meeting creation.
How do I generate a join link with the MiroTalk C2C API through Jentic?
Run a Jentic search for 'create a video meeting', execute the /meeting operation to obtain a room, then load and execute the /join schema with the participant name to get a direct URL. Install the SDK with pip install jentic and use the async search, load, and execute pattern.
Is the MiroTalk C2C API free?
MiroTalk C2C is open-source signalling backed by a hosted instance at c2c.mirotalk.com. Pricing for the hosted service is set by the MiroTalk operator and is not declared in the OpenAPI spec — check c2c.mirotalk.com or self-host for cost-free use.
GET STARTED