Use this action to update standard fields and/or custom property values on a lead in a channel your API key can access.Documentation Index
Fetch the complete documentation index at: https://docs.keenpartner.com/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
The API key’s company must have access to the lead’s channel. Access is granted when your company is part of the channel as creator, partner, referring company, or receiving company.Request
Must be
"update_lead".The lead’s UUID. If you only have the legacy integer ID, use
get_lead_by_legacy_id to resolve it
first.Contact email address.
First name of the contact.
Last name of the contact.
Phone number.
Company name of the lead.
How the lead was sourced (e.g.
"Website", "Referral").Employee at the referring company who submitted the lead.
Free-text notes about the lead.
The business’ ID in the company register or an external identifier from your
own system.
Custom property values to upsert on the lead. Each entry requires a
property_definitions_id and a value. Use get_channels to retrieve the property definitions available on the lead’s channel.properties entry has the following fields:
property_definitions_id(uuid, required): Must reference an active property definition on the same channel as the lead.value(string, number, boolean, or object, required): Stored as text. Numbers and booleans are stringified. Objects and arrays are JSON-serialized.nullandundefinedare not allowed.
At least one standard field or a non-empty
properties array is required.Behavior
- Upsert semantics: If a value already exists for the same lead and property definition, it is updated in place. Otherwise a new value is created.
- Partial updates: Standard fields you don’t include are left unchanged.
- No side effects: This action is a pure data edit. It does not trigger new-lead rewards, status-change rewards, webhooks, notifications, or workflows.
Response
Returns the full updated lead, including its status and all custom property values.Example
Request
Response
Errors
| Status | Error | Cause |
|---|---|---|
400 | "lead_id (uuid) required" | The lead_id field is missing or not a valid UUID. |
400 | "At least one updatable field or non-empty properties array required" | The request contains no allowed standard fields and no properties. |
400 | "Invalid properties" | One or more properties entries reference a definition that doesn’t belong to the lead’s channel, are missing property_definitions_id, or have a null/undefined value. The response includes an invalid array with the offending entries. No changes are persisted when this occurs. |
401 | "Invalid API key" | Missing or invalid X-Api-Key header. |
403 | "Lead not accessible" | The lead exists but is not in a channel your API key’s company can access. |
404 | "Lead not found" | The lead could not be found after the access check. |
500 | "..." | Unexpected server error. |