https://business.me-mate.net/api/betav3/tagmanage/tag/deleteContactsTagWise/deleteAll | Messenger Mate

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)

1 {
2   "api_key": "string",  
3   "tags": ["number"]
4 }

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

1 {
2   "api_key": "{{api_key}}",
3   "tags": [
4     274,
5     275
6   ]
7 }

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:

1 {"status":true,"msg":"Deleted tag-wise contacts (chunked)","deleted_contacts":0,"deleted_relations":18}

Error Cases

Exact error payloads may vary, but common cases include:

400 Bad Request: Missing/invalid api_key or invalid tags payload.
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 =

## 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) ``` json { "api_key": "string", "tags": ["number"] } ``` ### 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 ``` json { "api_key": "{{api_key}}", "tags": [ 274, 275 ] } ``` --- ## 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: ``` json {"status":true,"msg":"Deleted tag-wise contacts (chunked)","deleted_contacts":0,"deleted_relations":18} ``` --- ## Error Cases Exact error payloads may vary, but common cases include: - **400 Bad Request**: Missing/invalid `api_key` or invalid `tags` payload. - **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 =`

Request

This endpoint expects a string.

Response

msgstring

statusboolean

deleted_contactsinteger

deleted_relationsinteger

Request Body

Schema (JSON)

1 {
2   "api_key": "string",  
3   "tags": ["number"]
4 }

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

1 {
2   "api_key": "{{api_key}}",
3   "tags": [
4     274,
5     275
6   ]
7 }

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).

Error Cases

Exact error payloads may vary, but common cases include:

400 Bad Request: Missing/invalid api_key or invalid tags payload.

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.

$	curl -X POST https://business.me-mate.net/api/betav3/tagmanage/tag/deleteContactsTagWise/deleteAll \
>	-H "X-Requested-With: XMLHttpRequest" \
>	-H "Content-Type: application/json" \
>	-d "{
>	\"api_key\": \"{{api_key}}\", // required
>	\"tags\": [
>	274,
>	275
>	] // required
>	}"

1	{
2	"msg": "Deleted tag-wise contacts (chunked)",
3	"status": true,
4	"deleted_contacts": 2,
5	"deleted_relations": 18
6	}