Skip to main content
PATCH
Cambiar el responsable del lead
El ID viene de GET /team (el campo id de cada miembro). Debe ser un miembro activo de tu cuenta; de lo contrario la solicitud se rechaza con 400. Envía null para dejar el lead sin responsable.

Autorizaciones

X-API-Key
string
header
requerido

API key for authentication. Keys are prefixed with nxr_live_.

Parámetros de ruta

id
string<uuid>
requerido

Lead ID

Cuerpo

application/json

Any lead field can be updated. Metadata is shallow-merged with existing values (other keys preserved). All other fields are replaced directly.

first_name
string

Lead's first name

Ejemplo:

"Carlos"

last_name
string | null

Lead's last name

Ejemplo:

"Rodriguez"

email
string<email> | null

Lead's email address

Ejemplo:

"carlos@example.com"

phone
string | null

Lead's phone number

Ejemplo:

"+56987654321"

company
string | null

Lead's company name

Ejemplo:

"Stark Industries"

title
string | null

Lead's job title

Ejemplo:

"Manager"

source
string

Lead source

Ejemplo:

"website"

campaign_id
string<uuid> | null

Campaign ID to tag the lead with. Set to null to remove campaign assignment.

Ejemplo:

"123e4567-e89b-12d3-a456-426614174001"

metadata
object

Key-value pairs to merge into the lead's existing metadata. Existing keys not included in this object are preserved. New keys are added. Matching keys are overwritten with the new value.

Ejemplo:
assigned_to
string<uuid> | null

ID of the team member who owns this lead. Must be an active member of your account (GET /team). Set to null to leave the lead unassigned.

Ejemplo:

"123e4567-e89b-12d3-a456-426614174002"

Respuesta

Lead updated successfully

success
boolean
requerido
Ejemplo:

true

lead
object
requerido
Última modificación el 4 de agosto de 2026