Skip to main content
POST
Mark a Meeting as Completed
This logs a meeting_completed timeline activity and fires a meeting.completed outbound webhook (so the outcome reaches a subscribed endpoint or CRM). Unlike no-show and cancel, marking a meeting completed does not trigger the re-engage agent. Idempotency: re-marking a meeting that is already completed is a safe no-op ("idempotent": true).

Authorizations

X-API-Key
string
header
required

API key for authentication. Keys are prefixed with nxr_live_.

Path Parameters

id
string<uuid>
required

The meeting ID, from the POST /meetings response or GET /leads/{id}/meetings.

Body

application/json
notes
string

Free-text outcome notes.

Response

Outcome applied

success
boolean
meeting
object
Last modified on June 26, 2026