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 Meetings API

The meetings API from Wazo — 16 operation(s) for meetings.

Wazo Meetings 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 Meetings. 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 23 operations across 16 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

23 operations 16 paths 12 schemas 5 DELETE11 GET3 POST4 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 Meetings 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 23

Across 16 paths, the API surfaces 23 operations — 5 DELETE, 11 GET, 3 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

meetings 23
GET
/guests/me/meetings/{meeting_uuid}/status
Get the status of a meeting
1 param → 200404503
GET
/meetings/{meeting_uuid}/participants
List participants of a meeting
1 param → 200404503
GET
/users/me/meetings/{meeting_uuid}/participants
List participants of a meeting as a user
1 param → 200404503
DELETE
/meetings/{meeting_uuid}/participants/{participant_id}
Kick a participant from a meeting
2 params → 204404503
DELETE
/users/me/meetings/{meeting_uuid}/participants/{participant_id}
Kick a participant from a meeting as a user
2 params → 204404503
GET
/meetings
List meetings
list_meetings 7 params → 200
POST
/meetings
Create meeting
create_meeting 1 param body → 201400
GET
/meetings/{meeting_uuid}
Get meeting
get_meeting 2 params → 200404
PUT
/meetings/{meeting_uuid}
Update meeting
update_meeting 2 params body → 204400404
DELETE
/meetings/{meeting_uuid}
Delete meeting
delete_meeting 2 params → 204400404
GET
/users/me/meetings
List user meetings
list_user_meetings 7 params → 200
POST
/users/me/meetings
Create user meeting
create_user_meeting 1 param body → 201400
GET
/users/me/meetings/{meeting_uuid}
Get one of the meetings of the current user
get_user_meeting 2 params → 200404
PUT
/users/me/meetings/{meeting_uuid}
Update one of the meetings of the current user
update_user_meeting 2 params body → 204400404
DELETE
/users/me/meetings/{meeting_uuid}
Delete one of the meetings of the current user
delete_user_meeting 2 params → 204400404
GET
/guests/me/meetings/{meeting_uuid}
Get one guest meeting
get_guest_meeting 1 param → 200
POST
/guests/{guest_uuid}/meetings/{meeting_uuid}/authorizations
Request guest authorization to enter a meeting
create_guest_meeting_authorization 2 params body → 201400404
GET
/guests/{guest_uuid}/meetings/{meeting_uuid}/authorizations/{authorization_uuid}
Read the guest authorization to enter a meeting
get_guest_meeting_authorization 3 params → 200400404
GET
/user/me/meetings/{meeting_uuid}/authorizations
List all guest authorization requests of a meeting
list_user_meeting_authorizations 1 param → 200404
GET
/users/me/meetings/{meeting_uuid}/authorizations/{authorization_uuid}
Read the guest authorization to enter a meeting
get_user_meeting_authorization 3 params → 200400404
DELETE
/users/me/meetings/{meeting_uuid}/authorizations/{authorization_uuid}
Delete the guest authorization to enter a meeting
delete_user_meeting_authorization 3 params → 204400404
PUT
/user/me/meetings/{meeting_uuid}/authorizations/{authorization_uuid}/accept
Accept a guest authorization request
put_user_meeting_authorization_accept 2 params → 200400404
PUT
/user/me/meetings/{meeting_uuid}/authorizations/{authorization_uuid}/reject
Reject a guest authorization request
put_user_meeting_authorization_reject 2 params → 200400404

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Participant (9 properties), Meeting (9 properties), MeetingAuthorization (5 properties), Error (4 properties). Each schema is shown below with its type and property counts.

MeetingStatus
object
1 property
ParticipantList
object
1 property
Participant
object
9 properties
Error
object
Error message for the client
4 properties
MeetingAuthorization
object
5 properties
MeetingAuthorizationRequest
object
1 property
MeetingRequest
object
MeetingItems
object
1 property
Meeting
object
9 properties
MeetingAuthorizationItems
object
2 properties
Error_2
array
MeetingUserRequest
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wazo-meetings-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 Meetings 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.