ProspectBatchChanges

The fields a bulk prospect update sets; omit a field to leave it unchanged. Interest, stage, stageReason, classification and owner mean what they mean on a single prospect update; the note and the project tags to add or remove are bulk-only, and the single update's projectTags, accessExpiry and externalRefs are not available in bulk.

  • Your labels to add to each prospect within this project. Values are trimmed and de-duplicated (case-sensitive) and a multi-word value stays one label. Applied after removeProjectTags.

  • 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.

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

    values
    interestedmaybenot_interested
  • Words logged on each prospect as a note of its own, filed once per prospect with the interest change, or with the classification when no interest is sent. Only valid together with interest or classification. Send an Idempotency-Key header so a retry of the same request does not log it twice.

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

  • Your labels to take off each prospect within this project (exact, case-sensitive match).

  • Correct the prospects' process stage: not_contacted, teaser, im, data_room, bid. Records a manual override that later events can still raise. Omit to leave unchanged; there is no null here.

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