Delete meeting

DELETE

/domains/{domain}/users/{user}/meetings/{meeting}

Last modified:2026-10-09 00:44:35

OperationId:DeleteMeeting

Cancels a meeting, cancels one occurrence of it, removes it for good, or removes some of its attendees. The type field in the body chooses which.

Only the meeting's owner, its hosts, Office Manager for the meeting's domain, Reseller for its territory, and Super User can change it. Anyone else gets 403. A host who is not the owner puts its own user in the path.

meeting marks the meeting cancelled, removes its audio bridge, and emails a cancellation to the attendees. It returns 412 while anyone is connected.

instance cancels one occurrence of a recurring meeting, named by meeting-instance-schedule-start-datetime.

record removes the meeting, its attendees, and its audio bridge.

attendee removes the attendees listed in attendeeids.

202 means the delete is accepted and applied shortly after.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Body Params application/json

Examples

Responses

🟢202Accepted

application/json

The delete is accepted and applied shortly after.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

🟠412Precondition Failed

Request Example

Shell

JavaScript

Java

Swift

cURL

Cancel meetingCancel occurrenceRemove attendeesRemove for good

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//users//meetings/482913570' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "type": "meeting"
}'

Response Example

202 - Accepted

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-10-09 00:44:35

Update meeting

Reserve meeting ID