Update meeting attendee

PUT

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

Last modified:2026-10-04 19:30:55

OperationId:UpdateMeetingAttendee

Changes one attendee of a meeting, such as its role or what it may share. 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.

The meeting and the attendee come from the path; the attendee's meeting, ID, domain, and user cannot be changed. A change to role or a restriction is also written to the meeting's event log. 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/jsonRequired

Examples

Responses

🟢202Accepted

application/json

The change is accepted and applied shortly after.

Bodyapplication/json

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

cURL

Make presenterStop screen sharing

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/domains/example.com/users/1001/meetings/482913570/attendee/a1b2c3' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "role": "presenter"
}'

Response Example

202 - Accepted

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

Modified at 2026-10-04 19:30:55

Read meeting as attendee

Create video join token