Purpose
Delete all contacts associated with one or more tag IDs (tag-wise deletion). This is a destructive operation and cannot be undone.
Endpoint
-
Method:
POST -
URL:
https://business.me-mate.net/api/betav3/tagmanage/tag/deleteContactsTagWise/deleteAll
Required Headers
X-Requested-With: XMLHttpRequest
If your workspace/collection also requires
Content-Type: application/json, ensure it is set when sending JSON bodies.
Authentication
This endpoint authenticates using an API key passed in the request body.
- Uses Postman variable:
{{api_key}}
Recommended: store api_key in a Postman Environment (rather than Globals) and select that environment before sending requests.
Request Body
Schema (JSON)
Field Definitions
-
api_key(string, required): Your API key. In Postman, set this as{{api_key}}. -
tags(array of numbers, required): List of tag IDs to delete contacts for.
Example
Important Notes
-
Tag IDs must be valid numeric IDs that exist in your account.
-
This operation is destructive: it deletes tag-wise contact associations (and may delete contacts depending on backend behavior). Use with caution.
-
The response may report how many contacts/relations were affected (for example,
deleted_contacts,deleted_relations).
Success Response (200 OK)
Example response body:
Error Cases
Exact error payloads may vary, but common cases include:
-
400 Bad Request: Missing/invalid
api_keyor invalidtagspayload. -
401 Unauthorized / 403 Forbidden: API key invalid, expired, or lacks permission.
-
404 Not Found: Endpoint or resource not available.
-
429 Too Many Requests: Rate limit exceeded.
-
5xx Server Errors: Server-side failure while processing deletion.
Required Postman Variables
api_key(required): API key used in the request body.
Tip: Create/select an Environment and set:
api_key =
