Skip to main content
POST
Mark a Meeting as No-Show
The status change cascades the same side effects the native providers trigger:
  • A meeting.no_show outbound webhook fires, so the outcome reaches any subscribed endpoint or CRM.
  • A timeline activity (meeting_no_show) is logged on the lead.
  • If the client has the re-engage agent active with a matching recontact rule, the agent reaches out to the lead (e.g. to reschedule).
Idempotency: re-marking a meeting that is already no_show is a safe no-op. The response carries "idempotent": true and no duplicate activity or webhook is emitted.

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
reason
string

Stored as no_show_reason (defaults to api_marked).

notes
string

Free-text outcome notes.

Response

Outcome applied (or already marked, idempotent)

success
boolean
meeting
object
Last modified on June 26, 2026