Update meeting

PUT

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

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

OperationId:UpdateMeeting

Changes a meeting's settings, schedule, or attendees. Send only the fields to change.

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.

Some fields act at once: meeting-lock-enabled locks or unlocks the meeting for the attendees connected now, meeting-recording-enabled starts or stops recording, meeting-status ended ends the current instance, and attendees replaces the attendee list and emails the new attendees. Each change raises meeting-ordinal-sequence so calendar invitations update in place. Sending back the masked meeting-passcode a read returned leaves the passcode unchanged. A change never moves the meeting to another owner or domain.

202 means the change 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 change is accepted and applied shortly after.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

cURL

RescheduleLockEnd

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//users//meetings/482913570' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "meeting-schedule-start-datetime": "2026-09-16T16:00:00+00:00",
    "meeting-schedule-duration-minutes": 45
}'

Response Example

202 - Accepted

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

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

Delete meeting