Meet embed cookbook - click-to-conference on any page.
CodeB tenants ship meet.html (host UI) and room.html (join UI). Both accept the same URL contract: ?room=<code>[&dial=<ext>][&trunk=<slug>][&relay=1]. Point a link, an iframe or an email signature at either. European Digital Identity Wallet compatible - visitors can optionally present a wallet credential to unlock host-tier permissions inside the room.
See also: 8 embed recipes
| Integration | Mechanism | Best for | Snippet |
|---|---|---|---|
| Static HTML button | <a href=...> | Landing pages, marketing sites. | meet-button.html |
| JS link generator | buildMeetUrl() | Dynamic UIs that mint per-lead links. | meet-link-generator.js |
| iframe embed | room.html iframe | Whole conference inside your app. | iframe-embed.html |
| React <MeetButton> | React component | React SPAs. | meet-react.jsx |
| Vue <MeetButton> | Vue 3 component | Vue SPAs. | meet-vue.js |
| Angular meet-button | Angular component | Angular SPAs. | meet-angular.ts |
| WordPress shortcode | [codeb_meet_button] | WordPress sites. | meet-wordpress.php |
| Email signature HTML | clipboard snippet | Sales reps, calendar invite bodies. | meet-email-signature-html.txt |
Authentication model
Rooms are addressable by room code alone. Guests join by entering their name and granting mic/camera. Optional gates: knock-to-enter, invite-only tokens (?tok=) and wallet-credential presentation via the verifier cookbook. Never bake &name= into an invite URL - the invitee fills in their own name in room.html.
RASP posture
Room signalling runs on signal.ashx which enforces IpAllowGate, per-tenant rate limits and loud [SIGNAL-*], [ROOM-*], [SFU-*] diagnostics. Media (WebRTC) is peer-to-peer in mesh mode; SFU mode routes through the tenant SFU. Nothing changes when you embed the room in a customer iframe.
NIS2 / DORA / CRA
Meetings inherit the tenant audit trail: CDRs, recording shares (if enabled) and per-join LOUD-diag lines. NIS2 near-real-time signalling and DORA operational-resilience monitoring flow via the same log pipe consumed by the SIEM cookbook. CRA product-side auditability is met by per-tenant filesystem+JSON storage.
FAQ
Structured answers embedded in the schema block above.