Delete shared contacts by name

DELETE

/domains/{domain}/contacts

Last modified:2026-09-28 19:29:25

OperationId:DeleteDomainContactsByName

Deletes every contact in the domain's shared address book that matches a first and last name, and optionally a tag. To delete one contact, use DELETE /domains/{domain}/contacts/{contact_id} instead.

Needs domain tier or above: Office Manager can delete its own domain's shared contacts, Reseller those of domains in its territory, and Super User any domain's. Scopes that can only read shared contacts, including Site Manager and Call Center Supervisor, get 403.

name-first-name and name-last-name are required and match exactly; tags narrows the match to contacts whose stored tags contain its text. Send them in the query string or the JSON body. Every contact that matches is deleted, so check the matches with the list first. When none match, nothing is deleted and the call still returns 202. Only this address book is searched. Unlike the delete by ID, this call leaves the contacts' avatars and video contact copies in place.

202 means the deletes were accepted and are applied shortly after.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Query Params

Responses

🟢202Accepted

application/json

The deletes were accepted, one per matching contact, and are applied shortly after. Also returned when no contact matches.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/domains/example.com/contacts?name-first-name=Front&name-last-name=Desk&tags=cg-Vendors' \
--header 'Authorization: Bearer <token>'

Response Example

202 - Accepted

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-09-28 19:29:25

Count shared contacts

List shared contacts