https://business.me-mate.net/partners/broadcast/editMultiContact | Messenger Mate

curl -X POST https://business.me-mate.net/partners/broadcast/editMultiContact \
     -H "X-Requested-With: XMLHttpRequest" \
     -H "Content-Type: application/json" \
     -d "{
  \"contacts\": [
    {
      \"tag\": \"113050\",   // contact list id
      \"old_number\": \"97190xxxxx\", // old contact number
      \"number\": \"998877xxxx\",   // new contact number
      \"name\": \"name Updated\"     //  contact user name
    },
    {
      \"tag\": \"113050\",
      \"old_number\": \"987654xxxxx\",
      \"number\": \"99999xxxx\",
      \"name\": \"Sales Updated\"
    }
  ]
}"

{
  "msg": "Contacts updated!",
  "failed": [
    {
      "key": "value"
    }
  ],
  "status": true,
  "summary": {
    "failed": 0,
    "updated": 0,
    "not_found": 2,
    "requested": 2,
    "duplicates": 0
  },
  "updated": [
    {
      "key": "value"
    }
  ],
  "not_found": [
    {
      "tag": "113050",
      "error": "Contact not found",
      "old_number": "971905xxxx"
    },
    {
      "tag": "113050",
      "error": "Contact not found",
      "old_number": "987654xxxx"
    }
  ],
  "duplicates": [
    {
      "key": "value"
    }
  ]
}

Purpose

Edit/update multiple contacts in a single contact list (tag) in one call. Each item in contacts identifies an existing contact by old_number and provides the new number and name to update.

Endpoint

POST https://business.me-mate.net/partners/broadcast/editMultiContact

Authentication

This endpoint requires an authenticated partner session.

In this workspace, an auth token is referenced via the variable {{access token}}.

Configure auth at the request/collection level as required by your backend (for example, a session cookie or an Authorization header). This request currently only includes the header documented below.

Headers

Header	Required	Value	Notes
`X-Requested-With`	Yes	`XMLHttpRequest`	Indicates an AJAX/XHR request.

Request body (JSON)

Top-level body schema:

Field	Type	Required	Description
`contacts`	`array`	Yes	List of contact updates to apply.

Each `contacts[]` item:

Field	Type	Required	Description
`tag`	`string`	Yes	Contact list / tag identifier to update within (e.g., `"113050"`). All updates are applied within this list.
`old_number`	`string`	Yes	Existing/previous contact number to locate the contact record.
`number`	`string`	Yes	New contact number to set.
`name`	`string`	Yes	New/updated contact name.

`Example payload`

1 {
2   "contacts": [
3     {
4       "tag": "113050",
5       "old_number": "97190xxxxx",
6       "number": "998877xxxx",
7       "name": "name Updated"
8     },
9     {
10       "tag": "113050",
11       "old_number": "987654xxxxx",
12       "number": "99999xxxx",
13       "name": "Sales Updated"
14     }
15   ]
16 }

`Validation & edge cases`

Number format:** Ensure old_numberandnumber use the expected format for your account/region (digits-only vs. E.164, country code, etc.
Existence:** If old_numberdoes not exist under the providedtag, that item may fail or be ignored depending on server behavio
Duplicates/conflicts:** If numberalready exists in the sametag (or violates uniqueness rules), the server may reject that updat
Partial success:** When submitting multiple items, confirm whether the API applies updates atomically or allows partial updates (some succeed, some fail). Handle accordingl
Empty list:** contacts should be non-empt

`Typical responses`

(Exact response body may vary by deployment.)

200 OK**: Updates accepted/applied successfull
400 Bad Request**: Invalid JSON/body schema, missing required fields, or failed validatio
401 Unauthorized / 403 Forbidden**: Missing/invalid auth context (token/cookie) or insufficient permission
404 Not Found**: Tag/list not found (or related resource missing
500 Internal Server Error**: Unexpected server-side erro

### Purpose Edit/update multiple contacts in a single contact list (tag) in one call. Each item in `contacts` identifies an existing contact by `old_number` and provides the new `number` and `name` to update. ### Endpoint `POST https://business.me-mate.net/partners/broadcast/editMultiContact` ### Authentication This endpoint requires an authenticated partner session. In this workspace, an auth token is referenced via the variable `{{access token}}`. > Configure auth at the request/collection level as required by your backend (for example, a session cookie or an Authorization header). This request currently only includes the header documented below. ### Headers | Header | Required | Value | Notes | | --- | --- | --- | --- | | `X-Requested-With` | Yes | `XMLHttpRequest` | Indicates an AJAX/XHR request. | ### Request body (JSON) Top-level body schema: | Field | Type | Required | Description | | --- | --- | --- | --- | | `contacts` | `array` | Yes | List of contact updates to apply. | ``Each `contacts[]` item:`` | Field | Type | Required | Description | | --- | --- | --- | --- | | `tag` | `string` | Yes | Contact list / tag identifier to update within (e.g., `"113050"`). All updates are applied within this list. | | `old_number` | `string` | Yes | Existing/previous contact number to locate the contact record. | | `number` | `string` | Yes | New contact number to set. | | `name` | `string` | Yes | New/updated contact name. | ### `Example payload` ``` json { "contacts": [ { "tag": "113050", "old_number": "97190xxxxx", "number": "998877xxxx", "name": "name Updated" }, { "tag": "113050", "old_number": "987654xxxxx", "number": "99999xxxx", "name": "Sales Updated" } ] } ``` ### `Validation & edge cases` - **`Number format:** Ensure `old_number` and `number` use the expected format for your account/region (digits-only vs. E.164, country code, etc.`** - **`Existence:** If `old_number` does not exist under the provided `tag`, that item may fail or be ignored depending on server behavio`** - **`Duplicates/conflicts:** If `number` already exists in the same `tag` (or violates uniqueness rules), the server may reject that updat`** - **`Partial success:** When submitting multiple items, confirm whether the API applies updates atomically or allows partial updates (some succeed, some fail). Handle accordingl`** - **`Empty list:** `contacts` should be non-empt`** ### `Typical responses` `(Exact response body may vary by deployment.)` - **`200 OK**: Updates accepted/applied successfull`** - **`400 Bad Request**: Invalid JSON/body schema, missing required fields, or failed validatio`** - **`401 Unauthorized / 403 Forbidden**: Missing/invalid auth context (token/cookie) or insufficient permission`** - **`404 Not Found**: Tag/list not found (or related resource missing`** - **`500 Internal Server Error**: Unexpected server-side erro`**

Request

This endpoint expects a string.

Response

msgstring

failedlist of any

statusboolean

summaryobject

updatedlist of any

not_foundlist of objects

duplicateslist of any

Header

Required

Value

Notes

X-Requested-With

Yes

XMLHttpRequest

Indicates an AJAX/XHR request.

Field

Type

Required

Description

contacts

array

Yes

List of contact updates to apply.

Field

Type

Required

Description

tag

string

Yes

Contact list / tag identifier to update within (e.g., "113050"). All updates are applied within this list.

old_number

string

Yes

Existing/previous contact number to locate the contact record.

number

string

Yes

New contact number to set.

name

string

Yes

New/updated contact name.

{
  "contacts": [
    {
      "tag": "113050",
      "old_number": "97190xxxxx",
      "number": "998877xxxx",
      "name": "name Updated"
    },
    {
      "tag": "113050",
      "old_number": "987654xxxxx",
      "number": "99999xxxx",
      "name": "Sales Updated"
    }
  ]
}

1	{
2	"contacts": [
3	{
4	"tag": "113050",
5	"old_number": "97190xxxxx",
6	"number": "998877xxxx",
7	"name": "name Updated"
8	},
9	{
10	"tag": "113050",
11	"old_number": "987654xxxxx",
12	"number": "99999xxxx",
13	"name": "Sales Updated"
14	}
15	]
16	}