Using URL parameters
With Whereby Embedded you can use URL parameters to customize the meeting experience for your users. It’s possible for each participant in a meeting to have different parameter combinations.
URL parameters are added to the
roomURL when embedding a room in your web page or app.Several parameters can be combined by using the ampersand symbol (&). For instance, the following URL parameters would open the room with the screenshare and people buttons hidden:
https://subdomain.whereby.com/room?screenshare=off&people=off
URL Parameter | Description |
|---|---|
Applies a minimal UI. Turns off all controls except for cam and mic. | |
Participant joins the room with camera turned off. | |
Participant joins the room with microphone turned off. | |
Camera permissions are not requested or used at all. On by default. | |
Show/hide the screenshare button. | |
Show/hide the chat button. | |
Hide the people button. | |
Show/hide the leave button. | |
Set display name of participant. | |
Set the profile avatar of participant. | |
Hide the room background. | |
Hide the logo in the room header. | |
Hide the room lock button. | |
Hide the participant counter. | |
Hide the settings button. | |
Hide the Picture in Picture button. | |
Hide the more button. | |
Show/hide the entire top toolbar. | |
Show/hide the entire bottom toolbar. | |
Set the room UI language. | |
Float the self view to the bottom right. | |
Show/hide the breakout room feature for the meeting host. | |
Predefine up to 20 groups for the breakout groups function. | |
Show/hide the meeting timer. | |
Determines if users see the pre-call review step. | |
Skips the request permissions UI and asks for devices | |
Enable name labels for participants in the subgrid | |
Gets passed on to the corresponding webhooks. | |
Use a lower resolution by default | |
Automatically spotlight the local participant on room join | |
Enables YouTube and Miro integrations in the meeting | |
Specify custom virtual background which should be applied to the local participant | |
Specify custom help link in pre-call review step pointing users to additional support pages |
The minimal parameter applies a combination of UI adjustments to simplify the embedded meeting interface.
Hidden items: Status bar, chat button, screensharing button, leave button, and Whereby’s branding.
Shown items: Video and audio buttons.
For further adjustments, additional parameters can be combined with
?minimal. For example
?minimal&chat=on will show the chat button.Participants join the meeting with their camera off, they can turn it on whenever they want.
Use case: A sales representative showcasing a product to a customer relaxing at home.
Participants join the meeting with their microphone off, they can turn it on whenever they want.
Use case: A presentation is being given in a big meeting where attendees are not expected to participate verbally.
Whereby will not request access to participants' cameras when this is set to off, and there are no video controls.
Use case: A voice-only meeting where attendees are not expected to show themselves on camera.
Show/hide the screensharing button for the meeting participant.
Screensharing is available on all browsers that support this natively. Currently no mobile browsers support screensharing.
Show/hide the chat button. Messages are not stored after the meeting has ended.
Hide the people button.
Use case: The people button shows the participant list, which can be useful for bulk management of participants in bigger meetings.
Hide the leave button.
Use case: Can be used if you want to control the leave flow in other ways, like adding a custom link or button outside the embedded room to control what happens when users leave the call.
Set the display name for a participant instead of prompting the user for this information.
Use case: A participant’s name may be known before they join the meeting. Including this information as a parameter will save the user from entering their name again.
Set the avatar / profile picture of the participant instead of the automatically assigned name initials. The image can be a .png or .jpeg, and must be a square maximum of 64x64.
Note: You must make sure to list the origin of the image URL in the allowed domains section of the dashboard. The image URL must be https and cannot contain query params.
Hide the default meeting background.
Use case: Hiding the meeting background allows the meeting to appear more integrated by allowing the app or service’s branding shine through as the new background.
Hide the logo in the room header.
Use case: Control whether or not your company logo is displayed in the room header.
Hide the room lock button.
Use case: When set to off the lock button won’t be displayed in the room header. Also, hosts won’t be able to lock/unlock the room through the settings menu or the keyboard shortcut.
Hide the participant counter.
Use case: Will display the current and maximum number of participants in the room, e.g. “2/4” or “13/200”.
Hide the settings button.
Use case: Control whether or not the settings button is displayed in the room header.
Hide the Picture in Picture button.
Use case: Control whether or not the Picture in Picture button is displayed in the room header. Picture in Picture lets you pop out your meeting guests’ faces while browsing other tabs or applications.
Hide the “…” button.
Use case: Control whether or not the “…” button is displayed in the room header.
Used to toggle the entire top toolbar on/off.
Use case: When using the
minimal parameter, the top toolbar is hidden along with many other UI elements. Using topToolbar=on will cause the top toolbar to display, which is required if you want to enable breakout groups using breakout=on.Show/hide the entire bottom tool bar.
User case: Hiding the bottom toolbar entirely can be useful in cases where you are hoping to control in room items like camera or microphone via your own websites UI. This can be achieved when embedding Whereby with the Whereby Embed Element.
Set the meeting UI language to match your product or service. Select from either English
en, French fr, Italian it, German de, Norwegian nb, Dutch nl, Portuguese pt, Polish pl, Spanish es, Hindi hi, or Japanese jp.Float the self view to the bottom right.
Use case: Floating the self view to the bottom right maximizes the space for other meeting participants.
Use case: Combine bigger meetings with smaller, collaborative sessions. Your hosts can start breakout sessions where participants are split into smaller groups.
Predefine up to 20 groups for the breakout groups function.
Use case: Setting up groups ahead of time can save the host time during the meeting. Hosts will still be able to modify the group setup during the session using the in-room controls if needed.
Show/hide the meeting timer within the room.
Use case: Set this to “on” to have the meeting timer be displayed in the room. When set to “off”, room hosts can still activate the meeting timer from the “…” button, unless this button has been hidden via the
?minimal or ?moreButton=off parameters.Determines if users see the pre-call review step.
Use case: The pre-call review step will allow users to check their video/audio settings before joining the room, but this can be skipped by setting this parameter to “off”.
Skips the request permissions UI and asks for devices
Use case: This parameter will prevent the "Request Permissions" step during the pre-call phase and cause the browser to automatically request device permissions (if requested in the iFrame). This flag is required for Android app integration.
Used to toggle name labels for the participants in the subgrid.
Use case: Set this to “on” to show name labels for the participants that are rendered as small tiles in the subgrid. Makes it easier to distinguish participants with their camera off.
Can be used to pass any URL-encoded string so that it is included in the corresponding webhooks. The decoded string has a limit of 512 characters.
Use case: Set it to the user’s ID so that you can easily track through webhooks when a particular user joins or leaves a room.
Use a lower resolution by default
Use case: In some situations for users with poor network connections or devices with CPU constraints, it can be helpful to have lower resolution video feeds loading on the call. This can alleviate problems for users reporting issues with choppy video/audio or connecting to rooms.
Automatically spotlight the local participant on room join.
Note: Only works when the participant joining has host privileges.
Use case: Apply this parameter to ensure focus is directed at the local participant by spotlighting them. The spotlight ensures everyone else in the meeting has a bigger view of this participant.
Integrations are disabled for Whereby Embedded by default while using the
?minimal parameter. We set this by default because Content Security Policy restrictions can sometimes cause integrations to fail in unexpected ways. Currently only our YouTube and Miro integrations will work in an embedded setting.It is recommended you do testing to verify these integrations behave as expected before releasing to your users.
Specify a image url to use as the virtual background for the participant. The image must be provided in 1280x720 resolution in either
image/jpeg or image/png format. In addition, the image should be retrievable using CORS.Specify custom help link on the pre-call review step pointing users to additional support pages. This parameter should only be applied when pre-call review is enabled.
Use case: Apply this parameter to point users with camera or mic permission problems to bespoke help pages published on your own domain and brand, rather than to Whereby's help docs.
Last modified 4d ago