Skip to main content
GET
List conferences
This endpoint returns the conference names currently reported for your account. Use the result as supplementary status information and maintain your own room registry for authoritative discovery and lifecycle tracking.
Known limitation: This endpoint can return 200 OK with an empty conferences array while conferences are active. Do not use it as the source of truth for monitoring, billing, cleanup, or destructive operations.
Authentication required:
  • X-Auth-ID - Your account Auth ID
  • X-Auth-Token - Your account Auth Token
  • Content-Type: application/json
Use cases: Supplement an operational dashboard, inspect room names returned by the API, or troubleshoot a conference already tracked by your application.

Path parameters

No request body or query parameters needed. Simply use the GET method on the base conference endpoint.

Response

The documented response contains conference names and an API request identifier.
Response - 200 OK (Multiple Conferences)
Response - 200 OK (Empty Result)

Response Fields

  • conferences - Array of conference names reported by the API. An empty array is inconclusive and does not prove that no conferences are running.
  • api_id - Unique identifier for this API request
The response only includes conference names, not detailed information. The Retrieve a Conference endpoint is also subject to a known response limitation.

Example Request

List All Active Conferences

cURL Request

Get details for a reported conference

For each name returned by the API, you can request conference details. Do not use this flow as the only way to discover rooms; begin with the room registry maintained by your application.
Do not use this endpoint alone for billing, cleanup, destructive operations, or authoritative room discovery. An empty result can occur while conferences are active.
Best Practices:
  • Do not use this endpoint as the only source for dashboard or conference-state updates
  • Cache results to reduce API calls - refresh only when needed
  • Treat an empty conference array as inconclusive because active rooms may be omitted
  • Iterate through results to get detailed info only when needed
  • Implement rate limiting to avoid excessive API calls
  • Use WebSockets or webhooks for real-time updates instead of frequent polling

Example: Dashboard Implementation

JavaScript Dashboard Logic

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"

Response

200 - application/json

List of conferences

api_id
string
required
conferences
string[]
required

Conference names reported by the API. An empty array is inconclusive.