Erase Recipient
Erase everything held about one recipient, addressed by your id for them, whether or not a contact currently exists.
DELETE /v1/contacts/{id} covers the ordinary case, but it can only reach what a live contact points at. A trigger records the recipient by the external_id you sent, and resolution to a contact happens later, in the background — so a typo, an integration that addresses people by email while your contacts are keyed by CRM id, a trigger fired before the contact was created, or a contact deleted before this endpoint existed all leave trigger payloads that no contact delete can reach. Those payloads are the rawest data we hold: your variables, plus the external id itself, which is frequently an email address.
Use this to answer an erasure request when you are not certain a contact exists. It is idempotent, safe to call repeatedly, and returns what it touched so you can evidence the request. If a contact does exist it is deleted too, making this a strict superset of the contact delete.
Request
- Base URL: https://api.elaan.io (the document declares no server; this is the origin it was published from)
- URL: https://api.elaan.io/v1/erasures
- Auth: none declared
Headers
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.