CHAMPREP RTC
Open: CHAMPREP RTC
CHAMPREP RTC means CHAMPREP Real-Time Communication. It provides the communication building blocks for applications that need live audio, video, screen sharing, and recording. You control your application’s interface and authenticate its users; RTC provides rooms and authorized media sessions.
RTC or Meet?
Section titled “RTC or Meet?”| Choose | When you need |
|---|---|
| CHAMPREP Meet | A ready-to-use meeting experience for your team |
| CHAMPREP RTC | Communication embedded into an application you build |
RTC does not automatically replace existing Meet or Chat calls. Using a common CHAMPREP account does not mean those applications already use RTC for media.
What you can do
Section titled “What you can do”- Organize integrations into projects and issue project-scoped API keys.
- Create audio/video rooms and issue short-lived participant credentials.
- Join a room from the console to try microphone, camera, screen sharing, and receive-quality controls.
- Start and stop recording jobs and retrieve individual recorded tracks.
- Deliver recordings to your own S3 or S3-compatible bucket on plans that include it.
- Transcribe recordings after the call, with exact speakers, in about 100 languages, and export them as JSON, WebVTT, SRT or text.
- Send signed webhook events to several endpoints, with event filters, a delivery log, test sends and replays, and inspect completed connection usage.
- Use the same sign-in, profile selection, and billing foundation as CHAMPREP.
Availability depends on the active profile, permissions, and plan. Signing up for CHAMPREP alone does not enable RTC: it is a subscription add-on with a free trial. See RTC plans and billing.
Start here
Section titled “Start here”| Guide | What it covers |
|---|---|
| Getting started | Open a workspace, create a project, and test a room |
| Authentication and keys | Choose scopes, protect keys, and authorize your users |
| Rooms and Web SDK | Build a join flow and manage browser media |
| API reference | Customer server API methods, inputs, and responses |
| Recordings | Recording lifecycle, track downloads, and privacy |
| Bring your own storage | Deliver recordings to your own bucket, deletion, and retention |
| Transcription | Transcripts of recordings: languages, formats, billing, privacy |
| Join tokens | Server-minted credentials, project signing keys, and offline minting |
| Webhooks | Endpoints, event catalog, signature verification, retries, and replay |
| Errors | Error shapes, request ids, and the stable code catalog |
| Rate limits | Per-IP, per-key, and per-organization limits and headers |
| API versioning | What may change under /v1, RTC-Version, and OpenAPI |
| Plans and billing | Trial, tiers, packs, the subscription API, and refusals |
| Limits and troubleshooting | Plan allowances, current constraints, and recovery |
Release status
Section titled “Release status”RTC supports production integrations. Validate your complete workflow, including device permissions, reconnects, and media delivery, before release. This guide is not an availability SLA.
Use the supported JavaScript/TypeScript browser SDK distribution. Contact CHAMPREP for current package access and installation instructions; do not install an unofficial package.
Python and Node.js server SDKs, and guides for Angular, React, MEAN, MERN, and MongoDB/Express/Node (MEN) applications, are coming soon. They are not available releases or delivery-date commitments. Server applications can use the documented HTTPS API today when RTC access is enabled.
A connected account, separate application responsibilities
Section titled “A connected account, separate application responsibilities”Your CHAMPREP identity opens the developer console. Your application’s users do not need your CHAMPREP login credentials or secret project API key. Your backend authenticates them, checks which room each may join, and returns only that participant’s temporary credentials.
RTC’s customer server API uses its own project keys. Do not assume a general CHAMPREP API Gateway key, CLI command, or MCP tool supports RTC unless its own reference explicitly lists that support.