Delete Contact

Deletion Behavior

How contact lookup and deletion work

  • Pass the contact UUID or the workspace identity value to resolve the contact.
  • Email identity lookups are normalized before matching, so surrounding whitespace and letter casing do not affect the lookup.
  • A successful request permanently deletes the contact and returns an empty response body.
  • Associated comments, message events, delivery routes, messages, campaign executions, and segment membership records are deleted with the contact.
  • The resolved contact must belong to the API key's workspace.
DELETE
/v1/contacts/:contact

Permanently delete a contact by UUID or identity value

Path parameters

contactstring Required

Contact UUID or the current workspace identity value

Delete by UUID
curl -X DELETE https://api.leadpush.io/v1/contacts/:contact \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {token}"
Delete by Identity
curl -X DELETE https://api.leadpush.io/v1/contacts/person@example.com \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {token}"

Success and Errors

Expected outcomes for delete requests

  • Successful requests return an empty success response body.
  • The endpoint returns 404 if the contact path parameter does not resolve to a contact in the workspace.
  • The endpoint returns 403 if the resolved contact does not belong to the API key's workspace or the token does not have access to it.