Skip to main content
GET
Retrieve a conference
Retrieves the details of a particular conference by its name. The response includes the conference runtime, member count, and detailed information about each member currently in the conference.
Known limitation: A live conference can return 200 OK with {"error":"failed"} instead of conference details. Check the response body before using it, and capture ConferenceMemberID from conference enter callbacks when you need to target a member.
Authentication required:
  • X-Auth-ID - Your account Auth ID
  • X-Auth-Token - Your account Auth Token
  • Content-Type: application/json
Use Cases: Monitor active conferences, check participant status, verify member states (muted/deaf), track join times, and gather call UUIDs for further operations.

Path parameters

No request body needed. Simply use the GET method with the conference name in the URL path.

Response

When available, the response contains conference details and active members. The current failure response for a live conference is:
Response - 200 OK
An ended or unknown conference returns 404 Not Found with {"error":"conference not found"}.
Response - 200 OK

Response Fields

  • conference_name - Name of the conference
  • conference_run_time - Duration in seconds since conference started
  • conference_member_count - Number of active members
  • members - Array of member objects with detailed information
  • api_id - Unique identifier for this API request
Member Information: Each member object includes their ID, mute/deaf status, caller details, direction (inbound/outbound), call UUID, and join time. See The Conference Object documentation for detailed attribute descriptions.

Example Request

Retrieve Conference by Name

cURL Request
Conference names with spaces must be URL-encoded (space becomes %20).

Response with Multiple Members

JSON Response
Common Use Cases:
  • Monitor conference status: Check how long a conference has been running
  • Verify participants: See who is currently in the conference
  • Check member states: Identify which members are muted or deaf
  • Track join times: Determine when each participant joined
  • Get call UUIDs: Retrieve call UUIDs for further call operations
  • Dashboard display: Show real-time conference information in admin panels
Best Practices:
  • URL-encode conference names that contain spaces or special characters
  • Do not rely on this endpoint as the only source for dashboard updates
  • Capture member IDs from conference enter callbacks when performing member operations
  • Use call_uuid to correlate conference members with CDR records
  • Handle 404 responses gracefully - conference may have ended between requests

Authorizations

X-Auth-ID
string
header
required

Your Vobiz account Auth ID

X-Auth-Token
string
header
required

Your Vobiz account Auth Token

Path Parameters

auth_id
string
required

Your account Auth ID

Example:

"MA_XXXXXX"

conference_name
string
required
Example:

"My Conf Room"

Response

Conference details or the current live-retrieval failure payload

conference_name
string
required
conference_run_time
string
required

Conference runtime in seconds

conference_member_count
string
required
members
object[]
required
api_id
string
required