Erase a contact
using System.Net.Http.Headers;var client = new HttpClient();var request = new HttpRequestMessage{ Method = HttpMethod.Delete, RequestUri = new Uri("https://dashboard.azimea.com/api/v1/contacts/example"), Headers = { { "Authorization", "Bearer <token>" }, },};using (var response = await client.SendAsync(request)){ response.EnsureSuccessStatusCode(); var body = await response.Content.ReadAsStringAsync(); Console.WriteLine(body);}const url = 'https://dashboard.azimea.com/api/v1/contacts/example';const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://dashboard.azimea.com/api/v1/contacts/example \ --header 'Authorization: Bearer <token>'Erases a person at their request (GDPR right to erasure), the same way the dashboard does: their name, address, attributes, tags and consent history are removed, a single anonymous row remains so a later import does not bring them back, and the other parts of Azimea erase theirs (timeline, flow runs, messages, orders, reports). It cannot be undone. reference is the contact’s Azimea id, ext:<your id> or email:<address>; the last two find only contacts your system or an import created, a store’s customers are found by their Azimea id. A contact already erased is not found again (404): nothing is left to erase. Needs the contacts:erase permission, which no other permission includes.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”The erased contact’s id
object
object
object
object
object
object
object
Example
{ "isSuccess": true, "value": { "id": "01a10900-0000-7000-8000-000000000101" }, "status": 0, "errors": [], "fieldErrors": null}Missing or invalid API key
The key lacks the contacts:erase permission