Before using this endpoint, complete the Getting Started guide to obtain your API key. You do not need to send a company ID or role ID. AgencyHandy assigns the lead to the workspace client role automatically.
Prerequisites
- ✅ API key generated from Workspace Config → API Key
Create new leads
Endpoint
Headers
Request body
The request body is a JSON array — you can create one or more leads in a single call.The lead type. Allowed values:
individual, leadCompanyMember.The lead’s email address. It must be valid and should be unique within your workspace.
The lead’s pipeline status. Allowed values:
New, Contacted, Qualified, Working, Proposal Sent, Negotiation.Optional password for the lead. If provided, it must contain at least 8 characters, one uppercase letter, one lowercase letter, one number, and one special character.
The lead’s first name. Optional.
The lead’s last name. Optional.
The lead’s phone number. Optional. Defaults to an empty string if omitted.
The lead’s country. Optional.
The lead’s city. Optional.
The lead’s state or region. Optional.
The lead’s ZIP or postal code. Optional.
The lead’s address. Optional.
Optional array of category or label IDs. Each ID must exist in the workspace.
The lead’s company name. Optional.
Whether to send an invitation email. Optional. Defaults to
true.How you acquired this lead. Optional. Example values:
website, referral, social.The estimated value of the lead. Optional.
The lead’s website. Optional.
Optional assigned agent ID.
Optional date for when the lead was last contacted.
Optional array of file IDs attached to the lead.
Optional profile image URL or file reference.
Optional custom field responses for lead custom fields.
Optional currency code for a closed-won deal amount.
Optional closed-won deal amount. Can be
null or an empty string.Optional date of the lead’s last engagement.
Optional last engagement type. Allowed values:
Email, Phone, One-to-One, Online Meeting.Optional date of the first outreach.
Optional disqualification reason. Can be
null or an empty string.Optional email activity count. Can be
null or an empty string.Optional date of the last activity.
Optional meeting count. Can be
null or an empty string.Optional message thread count. Can be
null or an empty string.Optional outreach activity count. Can be
null or an empty string.Full payload example
Onlytype, email, and status are required. Every other field shown here is optional.
Example request
cURL
Success response
Indicates whether the request was processed successfully.
Leads that were created successfully.
The unique ID of the newly created lead. Store this if you need to reference the lead in subsequent API calls.
The full name of the lead (firstName + lastName).
The pipeline status of the lead as stored.
Leads that were not created. Each item includes the submitted
email, a reason, and sometimes the existing lead object.
