Log a Meeting
Log a meeting booked in an external system against an existing Nexor lead.
POST
Log an external meeting
To change a meeting’s outcome later, use the dedicated endpoints: Mark as No-show, Cancel, and Mark as Completed.
Lead matching. Leads are matched by
email, scoped to your account. If one lead matches it is used; if multiple share the email the most recently updated wins. Pass lead_id directly to skip email matching. If no lead matches, the API returns 200 OK with success: true, skipped: true, and reason: "lead_not_found"; no meeting is saved. Create the lead first with POST /leads before retrying.
Times and response status. The endpoint returns 200 OK when it saves or updates a meeting. If timezone is omitted, timestamps without an explicit offset are interpreted in the account’s configured timezone. Offset-aware timestamps retain their stated instant.
Idempotency. If you supply both external_calendar_provider and external_event_id, replaying the request updates the existing meeting instead of creating a duplicate. Safe for webhook retries.Authorizations
Body
application/json
Last modified on September 8, 2026
Log an external meeting