canonical: https://jentic.com/apis/c2c.mirotalk.com/mirotalk-c2c

# C2c Mirotalk MiroTalk C2C API

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.

## For AI agents

Create on-demand video meetings and generate participant join links via the MiroTalk C2C peer-to-peer video calling API.

## Scope

Does not handle recording storage, screen sharing controls, or chat transcripts - use for creating MiroTalk meetings and issuing join links only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Use Jentic search for 'create a video meeting', execute /meeting to create the room, then execute /join for each participant.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /meeting | Create a new MiroTalk meeting room |
| POST | /join | Generate a participant join link |

## Key resources

- **Meeting** — Create a new peer-to-peer video meeting room.
- **Join** — Generate a direct join link for a participant in a meeting.

## Why Jentic

- **Setup:** Wiring the MiroTalk C2C API by hand means passing your secret in the authorization header on every call and chaining /meeting to create a room before /join issues a link. Through Jentic you install once, import MiroTalk C2C from the API Directory, store the secret once, and your agent calls it.
- **Permission scoping:** MiroTalk C2C addresses each request by endpoint rather than a resource id in the URL path, so scoping stays at the operation level: you limit the agent to the operations it needs, such as creating a meeting on /meeting or issuing a link on /join, and leave the other out unless you add it.
- **Credential handling:** Your MiroTalk C2C authorization secret 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a video meeting' or 'generate a join link', and Jentic returns the matching MiroTalk C2C operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **CallFire API** — CallFire handles voice and SMS while MiroTalk C2C handles peer-to-peer video - combine for multi-channel outreach.
- **Call Control API** — Call Control supplies phone-reputation data; pair with MiroTalk C2C when video sessions are scheduled via inbound phone calls.
- **Caller API** — Caller API enriches phone numbers - not a true video alternative, but listed for agents comparing communications-adjacent third-party APIs.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the MiroTalk C2C API?

Yes. Because you run Jentic One yourself, your own rules decide which MiroTalk C2C operations and credentials the agent may use. Scoping is at the operation level: you can allow the agent to create a room on POST /meeting or issue a link on POST /join, and leave the other operation out unless you add it. The authorization secret is held by your own instance and injected at execution time, so the agent only ever calls the endpoints you have granted.