curl --request POST \
--url https://app.usertick.com/api/public/v1/contacts/{contactId}/erase \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.usertick.com/api/public/v1/contacts/{contactId}/erase', 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}/erase"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)Erase a contact
GDPR erasure of a contact and every response of the person, in the background. First the responses POST /responses/erase finds from the contact’s address, its external id and its links, with their files, erased everywhere; then the contact and its list memberships are deleted, its address is blanked in the send history and masked in the activity log, where the name is removed. The organization’s unsubscribe for the address stays, so no email reaches the person again if they are added later. Under a legal hold the job waits, queued, until the hold is released. An app or an AI assistant whose member’s role reaches only selected surveys can’t start it (403 AUTHZ-007-001); its member needs the permissions to manage surveys and contacts. While an erasure of the contact runs, the same job answers. 202 with the job (type contacts.erase, subject the contact id); follow it with GET /jobs/, which needs responses:delete.
Scopes: responses:delete, contacts:write.
curl --request POST \
--url https://app.usertick.com/api/public/v1/contacts/{contactId}/erase \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.usertick.com/api/public/v1/contacts/{contactId}/erase', 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}/erase"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)Authorizations
Headers
Any 1 to 255 printable ASCII characters, without a space at either end. The answer to the first request with a key is kept for 24 hours per credential: the same request again gets it back (Idempotent-Replayed: true), another request with the key is 409 PUB-002-002, and while the first still runs 409 PUB-002-003. A server error is not kept, and a request that never answered frees its key after 2 minutes: a retry with the key then runs again.
255Response
The job.