Update Contact

Lookup Behavior

How the `contact` path parameter is resolved

  • Pass the contact UUID to update a contact directly by its identifier.
  • Pass the workspace identity value to update the matching contact by email, phone, or your configured custom identity field.
  • Email identity lookups are normalized before matching, so surrounding whitespace and letter casing do not affect the result.
  • The resolved contact must belong to the workspace in the path.
POST
/v1/workspaces/:workspace/contacts/:contact

Update an existing contact by UUID or identity value

Path parameters

workspacestring Required

ID of your workspace

contactstring Required

Contact UUID or the current workspace identity value

Request body

attributesobject Required
Update by UUID
curl -X POST https://api.leadpush.io/v1/workspaces/:workspace/contacts/:contact \
-H "Content-Type: application/json" \
-H "Authorization: Bearer {token}" \
-d '{ 
  "attributes": { 
    "first_name": "Jane",
    "last_name": "Smith", 
    "company": "New Company Inc",
    "job_title": "Senior Developer" 
  } 
}'
Update by Identity
curl -X POST https://api.leadpush.io/v1/workspaces/:workspace/contacts/person@example.com \
-H "Content-Type: application/json" \
-H "Authorization: Bearer {token}" \
-d '{
  "attributes": {
    "first_name": "Jane"
  }
}'
Example Response
{
"uuid": "<contact_uuid>",
"subscribed": false,
"attributes": {
  "email": "jane.smith@example.com",
  "phone": "+1234567890",
  "first_name": "Jane",
  "last_name": "Smith",
  "company": "New Company Inc",
  "job_title": "Senior Developer"
},
"created_at": "2021-01-01T00:00:00.000Z",
"updated_at": "2021-01-02T12:30:00.000Z"
}