Create video join token

POST

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

Last modified:2026-10-04 19:31:03

OperationId:CreateMeetingVideoToken

Returns the credentials a client uses to join the video of the meeting in the path.

Requires a token for the user in the path; a Meeting Guest uses its guest_ user. Super User can call it for any user. You can join when you own the meeting, are on it, or are Office Manager or higher for its domain, or when the meeting is open to anyone with its ID and not locked. A Meeting Guest joins only the meeting its token was issued for.

The credentials come from the video service, and every field except access_token is passed through as it sends them. When the video service cannot issue them the answer is 502, or 504 when it does not answer in time. Send no body.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Responses

🟢200OK

application/json

The video credentials.

Bodyapplication/json

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

🔴502Bad Gateway

🔴504Gateway Timeout

Request Example

Shell

JavaScript

Java

Swift

curl --location --request POST 'https://awqacore01.crexendocloud.com/ns-api/v2/domains/example.com/users/1001/meetings/482913570/sfu' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

{
    "access_token": "string",
    "property1": "string",
    "property2": "string"
}

Modified at 2026-10-04 19:31:03

Update meeting attendee

Read recording playback token