Skip to main content
PATCH
Update lead
Update fields on an existing lead. Only provided fields will be updated; all others remain unchanged. Updatable fields:
  • full_name, email, phone, company, status, timezone, notes
At least one field is required — an empty body returns 400 VALIDATION_ERROR.

Path Parameters

id
string
required

Lead ID (UUID)

Example:

"550e8400-e29b-41d4-a716-446655440000"

Body

application/json
company
string

Company name

Example:

"Acme Corp"

email
string<email>

Email address

Example:

"john@example.com"

full_name
string

Full name of the lead

Example:

"John Doe"

notes
object[] | null

Internal notes attached to the lead. See the LeadNotes schema for the array shape (each note has content + created_at + optional user_id). Replaces the existing notes array. Pass null or omit to skip.

phone
string

Phone number in E.164 format (validated): + followed by country code and digits, no spaces or hyphens.

Pattern: ^\+[1-9]\d{1,14}$
Example:

"+14155552671"

status
string

Lead status. Before the lead books, its form answers set its status. After it books, its calls set it. You can still write a status here, and it is saved as sent, but Aura's status sync later puts back the status its calls give. The sync checks up to 100 of an organization's leads each hour, so in a large organization this can take days. To change it for good, change the call's outcome. A won call beats a disqualifying form: while the lead's current call is won, the sync never puts back disqualified.

Example:

"qualified"

timezone
string

Lead's timezone. Must be an IANA zone (e.g. Europe/Berlin); the common aliases EST, CET, PST8PDT and US/Pacific are accepted, and surrounding whitespace is trimmed. Anything else is DISCARDED rather than rejected: the request still succeeds and every other field is applied. On create the timezone is left empty; on update the lead's existing timezone is left UNCHANGED, never cleared. If an unusable timezone is the only field supplied to an update, the request is rejected, because nothing would have been applied. Rejecting outright at the boundary is planned once telemetry shows nobody depends on the current leniency (AUR-2090).

Example:

"America/New_York"

Response

Successfully updated lead

data
object
required
success
enum<boolean>
required
Available options:
true