Create /leads
Create a lead. Required: company or name (at least one). Optional: company/contact details, address, types, categories, assignees, responsible_role_id (round-robin assign to the next active staff of that role), status, source, and organization. Returns record with the detail projection. If the email, phone or company code already exists, no new lead is created: a repeated-request task is added to the existing lead and the response is 200 with duplicate: true, message and the existing lead as record (or duplicate_of with its type and uuid when the match is not a lead you can read).
Body
Newsletter subscription consent. Accepts 1/0 or true/false. To disable on update send 0 (a JSON false is treated as "not provided").
Last contact date (Y-m-d or Y-m-d H:i:s). Send today's date to mark the lead as contacted today.
Staff role UUID or numeric ID (tblroles.roleid), as listed by GET /roles. On create, assigns the next active staff member of this role in round-robin order. Merged with responsible when both are sent.
anyanyResponse
Duplicate: a matching record already exists, nothing was created.
Sent instead of record when the match is not a record of this module you can read.
Fields enabled for this documentation instance (projection enabled: feature, option, subdomain, closures) plus account-level form field visibility. Role- and user-level field overrides are not applied here, so an API key whose staff user has such overrides may receive fewer fields. A disabled field is omitted from the response object entirely; a present key with a null value means the record simply has no value.
More in Leads
PATCHUpdate /leads/{uuid}DELDelete /leads/{uuid}Still need help? Ask the team