UpdateProspectRequest

Request model for updating a prospect.

  • Schedule when the prospect's room access expires. Accepts a relative ("7d", "1w"), named ("tomorrow", "next_week"), or ISO date/datetime value — must be in the future. An expiry is a deadline, so a date without a time is the START of that day, UTC. Only valid on a prospect connected to a room. Send null to clear a scheduled expiry. Omit to leave unchanged.

  • Single-value pipeline vocabulary kept for existing integrations: not_contacted, contacted, interested, not_interested, bidder. Prefer interest and stage. When sent together with them, interest and stage win.

  • External references for CRM integration. Replaces all existing external refs. Set to empty array to remove all external refs.

    Properties: 2
  • Your judgement of the prospect's appetite: interested, maybe, not_interested. Send null to clear it. Omit to leave unchanged.

    values
    interestedmaybenot_interested
  • Assign a team member as the prospect's owner. Send the member's user id, or "me" for the caller. Send null to unassign. Omit to leave unchanged.

  • Your labels on this prospect within this project. Replaces the whole list; send an empty array (or null) to clear it. Values are trimmed and de-duplicated (case-sensitive) and a multi-word value stays one label. Leaves tags — the contact's or company's network-wide tags — untouched. Omit to leave unchanged.

  • Correct the prospect's process stage: not_contacted, teaser, im, data_room, bid. The stage is normally derived from what has happened; setting it records a manual override (returned as stageOverride) that later events can still raise. Omit to leave unchanged; there is no null here — correct an override by sending another stage, or withdraw it with DELETE .../prospects/{id}/stage-override.

    values
    not_contactedteaserimdata_roombid
  • Why the stage was corrected. Only valid together with stage; kept with the override.