Delete several native contacts
Deletes up to 100 contacts, each one the way a single delete works: its bookings are cancelled first, and it is refused whole if one of them will not cancel.
Partial on purpose. One contact who is on a call must not keep the other forty-nine, so a refusal is collected against the contact that caused it and the run carries on. You are handed deleted, failed and remaining, each naming contacts, because “some of them failed” is not something anyone can act on.
remaining is the ids the run never reached: the work is sequential, because firing a hundred cancellations at a linked calendar at once turns a clean refusal into a rate limit, and it stops at a time budget rather than running past the point where you stopped waiting. Send remaining again to carry on; at least one contact is always attempted, so asking again always makes progress.
A contact that had already gone counts as deleted, not failed. It is what a second click, or another operator, looks like from here.
Cookie-auth callers must send the x-csrf-token header.
Required API key scope: contacts:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Query Parameters
The sub-account. It is the only thing that identifies the tenant on these routes, and it is re-checked against your access on every call. A sub-account that keeps its contacts in a CRM answers 400.
Body
The contacts to delete.
