Stop calling several native contacts
Stops the calls for up to 100 contacts at once, each one the way the single endpoint does: the switch goes on the contact and its pending Queue rows are parked, so nothing is left scheduled against a contact nobody may call.
It only ever stops. There is no bulk resume, and sending anything else in the body will not make one. Clearing the block asks whether the PERSON asked not to be called, which the single endpoint refuses to answer without acknowledgeRequest; answering it a hundred times in one request is how somebody who asked us to stop gets called again. Reopen leads one at a time.
This records the decision as OURS, never as the contact’s own request, because a selection in a list is not somebody asking.
Partial on purpose. A contact that has since been deleted is named in failed and the rest still go, because “some of them failed” is not something anyone can act on. Re-marking a contact who is already stopped is not a failure.
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 stop calling, and why.
