Sales

Mark Lead Discovery Held

Mark a discovery call as actually held — keyed by lead_id, not booking_uid.

Track B Workflow #1 — UI version of POST /api/cal/booking/{uid}/held.

The dashboard already knows the lead_id (it's the row the user is acting on), so calling by lead_id is friction-free. The booking-uid endpoint remains available for flows that only know the cal.com uid (Slack reaction handlers reading from the booking link, etc.).

Idempotent: subsequent calls are no-ops (booking_held_at stays at the first-mark value). Returns 404 if the lead has no booking_scheduled_at.

post/api/sales/leads/{lead_id}/mark-held

Request

  • Base URL: https://api.ruzora.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.ruzora.com/api/sales/leads/{lead_id}/mark-held
  • Auth: HTTP bearer

Path parameters

lead_idstring required

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.