Delete a contact
Delete a contact, and keep everything they took part in.
Nothing the contact was part of is destroyed. Relationships, life events and files outlive them, because those describe things that happened rather than the row itself.
The reminders about this person go quiet and say why, rather than disappearing. Private links onto their page stop opening.
The contact representing you cannot be deleted, and asking answers 422. Relationships and life events are written from that contact's point of view, so a vault that lost it would be talking about nobody.
The deletion is soft, so nothing is destroyed, but no endpoint here brings a contact back today. Treat it as final.
Path parameters
Sent as JSON. Anything not listed here is ignored.
The vault the contact lives in, named either by the readable name it reports as slug or by its id. Both answer.
The contact, named either by the readable name it reports as slug or by its id. Both answer. A readable name is rebuilt whenever the record is renamed, and the previous one stops answering, so a client that stores a reference stores the id. A name a record has released is never given to another. The contact has to be in the vault the path names: a contact of yours addressed through the wrong vault answers 404, the same as one that never existed. A contact absorbed by a merge answers 404 here, and the merge endpoints say what became of them.
Returns
Nothing at all. A contact belonging to somebody else answers 404, and so does one you have already deleted, so calling this twice does not report a second deletion.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
No content.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.