Note: The Conference object is returned when you retrieve a specific conference or list all conferences. It provides a complete snapshot of the conference state at the time of the request.
Conferences are created on join, not via REST. There is no “create conference” endpoint. A room comes into existence the moment the first caller enters it through the
<Conference> XML element (<Conference>RoomName</Conference>). The REST Conference endpoints only inspect, control, or record rooms that already have at least one member. Retrieving a name that has no members returns 404.Conference Attributes
Top-Level Attributes
| Field | Type | Required | Description |
|---|---|---|---|
conference_name | string | - | Name used to identify the conference. This is the unique identifier for the conference room. |
conference_run_time | string | - | Time (in seconds) since the conference was initiated. Indicates how long the conference has been active. |
conference_member_count | string | - | Number of members currently active in the conference. Updated in real time as members join or leave. |
members | array | - | Array of member objects, each containing detailed information about an individual participant in the conference. See Member Attributes below. |
Member Attributes
Each member object in themembers array contains the following attributes:
Member Object Attributes
| Field | Type | Required | Description |
|---|---|---|---|
member_id | string | - | Unique ID of the member within the conference. Used to identify the member for operations like mute, deaf, or kick. |
muted | boolean | - | true if the member is currently muted (their audio is not transmitted to other participants). false if they can speak freely. |
deaf | boolean | - | true if the member cannot hear conversations in the conference (they are “deafened”). false if they can hear other participants. |
from | string | - | Source of the call - either a PSTN number or SIP endpoint. Indicates where the member is calling from. |
to | string | - | Conference bridge number - either a Vobiz number or an application URL. The destination the member dialed to join. |
caller_name | string | - | Name of the caller (only available if the call was made from a SIP endpoint). Empty string if not specified or not applicable. |
direction | string | - | Direction of the call - either “inbound” (caller dialed into conference) or “outbound” (conference system called the participant). |
call_uuid | string | - | Unique identifier of the call. Can be used to reference this specific call in other API operations. |
join_time | string | - | Time (in seconds) since the member joined the conference. Indicates how long this participant has been in the conference. |
Example Response
Here’s an example Conference object with one active member:Conference Object Example
Understanding the Example:
- Conference “My Conf Room” has been running for 590 seconds (~9.8 minutes)
- Currently has 1 active member (John)
- John is not muted or deaf - full two-way audio
- John joined via inbound call from number 1456789903
- John has been in the conference for 590 seconds (joined when the conference started)
Multiple Members Example
Multiple Members Conference
Analysis:
- Alice (member 45): Joined when the conference started, speaking
- Unnamed (member 46): Called outbound 5 minutes after start, currently muted
- Bob (member 47): Joined 15 minutes after start, speaking