Add Video Calls to Your Site with Whereby Embedded
Adding video calls to your site is a critical requirement for telemedicine, EdTech, and SaaS. Manually building WebRTC with ICE candidates and STUN servers takes tens of hours, leads to N+1 requests, memory leaks, and browser incompatibility. Whereby Embedded solves this in one hour: a single <whereby-embed> gives you ready video calls with screen sharing, chat, and recording. Over 5 years we've integrated Whereby into 50+ projects—from doctor consultations to online schools. Our engineers are certified on the Whereby API and guarantee functionality across all devices. In one project, we reduced video delivery time from 3 weeks to 1 day, and infrastructure costs by 6x (saving over $30,000 per year). Below, we dive into the technical details that will save you time and budget.
Problems We Solve
WebRTC complexity. Self-built video requires setting up ICE servers, NAT handling, and codec management. One mistake and the call fails. Whereby handles it all: media servers, relay servers (TURN), and adaptive streaming. You get stable calls without headaches. Infrastructure savings—up to 90%.
Scaling. Growing load requires more server capacity for custom solutions. Whereby processes thousands of concurrent rooms automatically—you just keep your API key. This reduces infrastructure costs by 5–10x, and at 1,000 call hours per month, savings can reach $5,000.
Device support. The ready web component works correctly in all modern browsers (Chrome, Firefox, Safari, Edge) on desktop and mobile. Custom WebRTC needs individual testing for each browser and device.
Why Whereby Embedded Instead of Custom WebRTC?
| Feature | Custom WebRTC | Whereby Embedded |
|---|---|---|
| Development time | 2–4 weeks | 0.5–1 day |
| Server infrastructure | Own TURN/STUN | Ready (Whereby) |
| Browser testing | Each browser | Automatic |
| Scaling | Manual | Automatic |
| Maintenance cost | High | Fixed subscription from $99/month |
Note: As documented in the WebRTC API, implementation requires deep knowledge of network protocols. A ready component gives 10–20x time savings and eliminates stream handling headaches. Additionally, Whereby supports call recording and analytics—these require extra integrations in custom solutions.
Common Issues
Below are frequent mistakes during self-integration and how to avoid them.
| Mistake | Symptom | Solution |
|---|---|---|
| Missing CDN script | Web component not rendering | Add <script> before closing </body> |
| Incorrect endDate | Rooms expire prematurely | Set 1–2 hours buffer beyond scheduled end |
| Missing event handling | UI not updating after call | Subscribe to ready and leave |
| Ignoring hostRoomUrl | Host cannot moderate | Use hostRoomUrl for moderator entry |
Integration Process
The process takes 3 steps:
-
Create a room via API—we send a POST request to
https://api.whereby.dev/v1/meetingswith your API key. The room can be temporary (up to 2 hours) or persistent (with renewal). We automate room creation for your use case. -
Embed the web component—add the script to
<head>and place<whereby-embed>in the desired page section. For React/Next.js, declare the type and subscribe toreadyandleaveevents. Setup takes minutes. -
Customization—adjust display (minimal mode, disable premeeting screen, enable chat or screenshare). Optionally integrate with your CRM for call logging. All parameters are documented.
Example room creation via API
curl -X POST https://api.whereby.dev/v1/meetings \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"endDate": "2025-12-31T23:59:59Z", "roomMode": "normal"}' Available Security Settings
Whereby Embedded provides flexible attributes to control functionality:
-
skip-media-permission-prompt—disable the camera permission request screen. -
chat="off"—hide chat. -
background="off"—disable background blur. -
screenshare="off"—disable screen sharing.
For enterprise projects, audit logs and JWT authentication integration are available. This meets security and privacy requirements.
What's Included
- Whereby API integration—create and manage rooms.
- Web component embedding—correct operation in your framework.
- Documentation—all attributes and events explained.
- Access setup—API key and environment configuration.
- Training—how to manage rooms via admin panel.
- Support—2 weeks post-delivery (bug fixes).
Timeline
Basic integration (room creation + web component) takes 0.5–1 day. If custom logic is needed (automatic room creation on consultation booking, JWT authentication integration), up to 3 days. Timeline is fixed in contract.
Contact us for a free assessment of your project—we'll suggest the best solution and exact timeline. Order Whereby Embedded integration and get stable video calls as early as the next day.