Whereby
Joining Whereby rooms as a meetbot — supported URL patterns, knock-to-enter behavior, integration notes.
The whereby adapter joins Whereby rooms via browser automation on
the public web client (whereby.com/<room> and subdomains). Whereby
is WebRTC-native with no anti-bot fingerprint surface, so the
integration is significantly cleaner than Meet/Teams/Zoom.
Supported URL patterns
| Pattern | Notes |
|---|---|
https://whereby.com/<room> | Public room |
https://<tenant>.whereby.com/<room> | Hosted-subdomain (Whereby Embedded) |
The platform discriminator is auto-detected by host; pass
platform: "whereby" explicitly if you want to bypass detection.
curl -X POST https://api.meetbot.dev/api/v1/jobs \
-H "authorization: Bearer $MEETBOT_API_KEY" \
-H "content-type: application/json" \
-d '{
"externalId": "whereby-demo-2026-05-09",
"meetingUrl": "https://whereby.com/teamname-room",
"platform": "whereby",
"displayName": "meetbot",
"webhooks": {"onFinalize": "https://yours.example/hook/meetbot"}
}'Lobby behavior
- Personal rooms auto-admit; the bot lands directly in the meeting.
- Knock-to-enter rooms show a "Waiting for someone to let you
in" screen; the host has to accept. The bot stays in
entering_lobbyuntil admitted orafterEntryDelaySecondsexpires (default 600s / 10 min). - Locked rooms trip a retryable failure — the host can unlock and the bot's existing retry budget (3 hard attempts) will re-knock.
Captions
Whereby has no native captions toggle today (the platform relies on
third-party transcription integrations). The adapter logs
whereby:captions-skipped and audio capture continues normally —
your downstream STT pipeline (Whisper, Deepgram, etc) processes the
per-speaker WebRTC tracks the bot ships.
Roster + competing-bot detection
Roster is scraped from the participant tiles
([data-testid^="participant-"]); the same evaluateAutoLeave shared
across all platforms applies. Set autoLeave.onBotDetected: true to
have the bot leave when a competing notetaker (Otter, Fireflies, etc)
is observed in the room.
Known quirks
- Whereby Embedded customers (white-labeled tenants) keep the same
DOM contract as
whereby.com— the adapter works without modification. - The bot's join is reliable enough that we recommend it as the default test platform for new meetbot deployments — easier signal-to-noise than fighting Meet's anti-bot stack.
Failure codes
| Whereby sentinel | failure_code |
|---|---|
| "That room does not exist" | meeting_not_found |
| "The meeting has ended" | meeting_ended |
| "This room is locked" (after retry budget) | host_denied_admission |
Stuck in knock past afterEntryDelaySeconds | lobby_timeout |