How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wazo Conferences API

The conferences API from Wazo — 11 operation(s) for conferences.

Wazo Conferences API is one of 113 APIs that Wazo publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Conferences. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, a changelog, authentication docs, and an AsyncAPI specification.

This API exposes 18 operations across 11 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: /1.0, /1.1.

18 operations 11 paths 14 schemas 4 DELETE6 GET2 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{wazo_stack}/api/auth/0.1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Wazo Conferences API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Token (wazo_auth_token). By default, every request must be authenticated.

Paths & Operations 18

Across 11 paths, the API surfaces 18 operations — 4 DELETE, 6 GET, 2 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

conferences 18
GET
/conferences/{conference_id}/participants
List participants of a conference
1 param → 200404503
GET
/users/me/conferences/{conference_id}/participants
List participants of a conference as a user
1 param → 200404503
DELETE
/conferences/{conference_id}/participants/{participant_id}
Kick participant from a conference
2 params → 204404503
PUT
/conferences/{conference_id}/participants/{participant_id}/mute
Mute a participant in a conference
2 params → 204404503
PUT
/conferences/{conference_id}/participants/{participant_id}/unmute
Unmute a participant in a conference
2 params → 204404503
POST
/conferences/{conference_id}/record
Record a conference
1 param → 204400404503
DELETE
/conferences/{conference_id}/record
Stop recording a conference
1 param → 204400404503
GET
/asterisk/confbridge/wazo_default_bridge
List ConfBridge wazodefaultbridge options
list_asterisk_confbridge_wazo_default_bridge → 200
PUT
/asterisk/confbridge/wazo_default_bridge
Update ConfBridge wazodefaultbridge option
update_asterisk_confbridge_wazo_default_bridge body → 204400404
GET
/asterisk/confbridge/wazo_default_user
List ConfBridge wazodefaultuser options
list_asterisk_confbridge_wazo_default_user → 200
PUT
/asterisk/confbridge/wazo_default_user
Update ConfBridge wazodefaultuser option
update_asterisk_confbridge_wazo_default_user body → 204400404
GET
/conferences
List conference
list_conferences 7 params → 200
POST
/conferences
Create conference
create_conference 1 param body → 201400
GET
/conferences/{conference_id}
Get conference
get_conference 2 params → 200404
PUT
/conferences/{conference_id}
Update conference
update_conference 2 params body → 204400404
DELETE
/conferences/{conference_id}
Delete conference
delete_conference 2 params → 204400404
PUT
/conferences/{conference_id}/extensions/{extension_id}
Associate conference and extension
associate_conference_extension 2 params → 204400404
DELETE
/conferences/{conference_id}/extensions/{extension_id}
Dissociate conference and extension
dissociate_conference_extension 2 params → 204400404

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Participant (9 properties), Error (4 properties), ExtensionRelationBase (3 properties), ConferenceRelationBase (2 properties). Each schema is shown below with its type and property counts.

ParticipantList
object
1 property
Participant
object
9 properties
Error
object
Error message for the client
4 properties
ConferenceRelationExtensions
object
1 property
ConfBridgeConfiguration
object
This configuration will be in the file 'confbridge.conf' used by asterisk. Please consult the asterisk documentation for further details on available parameter…
1 property
IncallRelationExtensions
object
1 property
ConferenceRelationBase
object
2 properties
Conference
ConferenceRelationIncall
ExtensionRelationBase
object
3 properties
ConferenceItems
object
2 properties 1 required
Error_2
array
ConferenceRelationIncalls
object
1 property
IncallRelationBase
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wazo-conferences-api-openapi.yml Raw ↑

Other APIs Wazo publishes across the network.

Wazo Phone Provisioning API (wazo-provd)
Wazo Websocket Event Stream (wazo-websocketd)
Wazo Aastra API
Wazo Access Features API
Wazo Action API
Wazo Adhoc Conferences API
Wazo Admin API
Wazo Agent Statistics API
Wazo Agents API
Wazo Applications API
Wazo Asterisk API
Wazo Backends API
Where this information came from

This is an independent, third-party profile of Wazo Conferences API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.