Get Contact

Lookup Behavior

How the `contact` path parameter is resolved

  • Pass the contact UUID to fetch a contact directly by its identifier.
  • Pass the workspace identity value to fetch 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 API key's workspace.
GET
/v1/contacts/:contact

Retrieve a single contact by UUID or identity value

Path parameters

contactstring Required

Contact UUID or the current workspace identity value

Request
Lookup by UUID
curl "https://api.leadpush.io/v1/contacts/:contact" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {token}"
Lookup by Identity
curl "https://api.leadpush.io/v1/contacts/person@example.com" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {token}"
Response Example
{
  "data": {
    "uuid": "<contact_uuid>",
    "subscribed": true,
    "attributes": {
      "email": "person@example.com",
      "phone": "+1234567890",
      "first_name": "John",
      "last_name": "Doe"
    },
    "provider": "gmail",
    "updated_at": "2021-01-01T00:00:00.000Z",
    "created_at": "2021-01-01T00:00:00.000Z"
  }
}