Delete a contact
curl --request DELETE \
--url https://app.usertick.com/api/public/v1/contacts/{contactId} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.usertick.com/api/public/v1/contacts/{contactId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.usertick.com/api/public/v1/contacts/{contactId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text)Delete a contact
Deletes a contact and its list memberships, as Delete in Usertick does. Its address is blanked in the send history, whose counts stay, and the organization’s unsubscribe for the address stays. Its responses stay and lose their link to the contact, so POST /responses/erase can no longer find the ones only that link pointed to: to erase a person, use POST /contacts//erase instead. Recorded in the audit log as made through the credential.
Scopes: contacts:write.
DELETE
/
contacts
/
{contactId}
Delete a contact
curl --request DELETE \
--url https://app.usertick.com/api/public/v1/contacts/{contactId} \
--header 'Authorization: Bearer <token>'const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.usertick.com/api/public/v1/contacts/{contactId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.usertick.com/api/public/v1/contacts/{contactId}"
headers = {"Authorization": "Bearer <token>"}
response = requests.delete(url, headers=headers)
print(response.text)Last modified on November 8, 2026