prospect/post

Tool: create

create a single prospect in the CRM.

Creates one prospect record, validates email uniqueness, and returns the full prospect object. Use this for targeted single-record creation; for multi-row imports use prospect/post_bulk.

baseListId is optional (body field, body-only): omitted → the prospect lands in the account's real "Unassigned" list (the same default prospect/post_bulk uses when its listId is omitted) — not list 0/no-list. Pass a valid baseListId (create/find via the list operations) to assign a different list instead. The Unassigned list is an ordinary list — it can be renamed or deleted like any other.

Naming trap: this op takes BODY field baseListId; bulk import (prospect/post_bulk) takes QUERY param listId. They are NOT interchangeable.

Body

field	type	req	constraints	description
email	string	✓	≤256 chars	Must be a valid email address
baseListId	integer	–	≥1	List to assign the prospect to; omit → the account's Unassigned list
sendingStatus	string	–	see schemas/prospect	Campaign participation state
sendingActive	boolean	–	default true	Whether eligible for campaign sending
firstName	string	–	≤512 chars
lastName	string	–	≤512 chars
company	string	–	≤512 chars
industry	string	–	≤512 chars
city	string	–	≤512 chars
website	string	–	≤512 chars
phone	string	–	≤512 chars
country	string	–	≤512 chars
domain	string	–	≤180 chars
companySocial	string	–	≤512 chars
companySize	string	–	≤32 chars
jobPosition	string	–	≤512 chars
location	string	–	≤512 chars
personalSocial	string	–	≤512 chars
customImageUrl	string	–	≤256 chars
screenshotUrl	string	–	≤256 chars
logoUrl	string	–	≤256 chars
state	string	–	≤128 chars
icebreaker	string	–	≤4000 chars
custom1–custom20	string	–	≤2000 chars each	Free-text custom fields
notes	string	–		Internal notes

Response

201 — prospect object: see schemas/prospect. Deltas: none (full schema).

Errors: 400, 401, 406, 409, 415, 422, 429, 500 — shared schema: schemas/errors. 409 = duplicate email.

Invoke

Call create with name: "prospect/post".