Log meeting event

POST

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

Last modified:2026-10-09 00:42:40

OperationId:CreateMeetingLogEvent

Adds an event to the log of one instance of a meeting, recorded as written by the user in the path with file-source apiv2.

Only the meeting's hosts and attendees, its owner, and Office Manager or higher for its domain can use its event log. An attendee puts its own user in the path.

Only event, target, and details are taken from the body. 202 means the event 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 event is accepted and applied shortly after.

Bodyapplication/json

🟠400Bad Request

🟠401Authentication Required

🟠403Forbidden

🟠404Record not found

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//users//meetings/482913570/instance/66e6f0a1b2c3d/log' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "event": "part_join",
    "target": "1002",
    "details": {
        "attendee_id": "a1b2c3",
        "name": "Sales Queue"
    }
}'

Response Example

202 - Accepted

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

Modified at 2026-10-09 00:42:40

Delete route profile

Read meeting events