Users are your customer's employees registered in your service — such as sales managers or support agents who handle deals and customer inquiries in the CRM.

The methods below help you synchronize your service's users with Wazzup and configure their access permissions to chats.

Methods

• GET /v2/users — retrieve a list of users.
• GET /v2/users/{user_id} — retrieve a user by ID.
• POST /v2/users — adding users.
• PATCH /v2/users — updating users.
• DELETE /v2/users — deleting users.
• PATCH /v2/settings — configure user roles per channel and control number visibility in the iframe.
• GET /v2/settings — retrieve role settings.

Adding Users

The request body should contain an array of user objects (max 100 users per request). Users are matched by their id: if a user does not yet exist in Wazzup, they will be added; if they already exist, their information will be updated.

Request Example:

curl -L 'https://tech.wazzup24.com/v2/users' -H 'Authorization: Bearer <client_access_token>' -H 'Content-Type: application/json' -d '{
"users": [
{
"id": "1",
"name": "Test",
"phone": "37199999999"
}
]
}'

Response example:

{
"data": {
"processed": 1
},
"meta": {
"timestamp": 1759495852
}
}

Result: The user (or list of users) has been added.

Common Errors When Adding Users

Retrieving a List of Users

Request Example:

curl -L 'https://tech.wazzup24.com/v2/users?offset=0&limit=50' -H 'Authorization: Bearer <client_access_token>'

Response example:

{
"data": [
{
"id": "1",
"name": "Test",
"phone": "37199999999"
}
],
"meta": {
"timestamp": 1759496425
}
}

Result: Returns a list of all previously created users.

Retrieving a User by ID

Path Parameters
user_id — CRM user ID

Request Example:

curl -L 'https://tech.wazzup24.com/v2/users/1' -H 'Authorization: Bearer <client_access_token>'

Response example:

{
"data": [
{
"id": "1",
"name": "Test",
"phone": "37199999999"
}
],
"meta": {
"timestamp": 1759496425
}
}

Result: Returns the user with id: 1, if they exist.

Updating Users

Example:

curl -L -X PATCH 'https://tech.wazzup24.com/v2/users' -H 'Authorization: Bearer <client_access_token>' -H 'Content-Type: application/json' -d '{
"users": [
{
"id": "1",
"name": "Tester",
"phone": "37199999999"
}
]
}'

Response example:

{
"data": {
"processed": 1
},
"meta": {
"timestamp": 1759495852
}
}

Result: If the user exists, their information has been updated.

Deleting Users

Request Example:

curl -L -X DELETE 'https://tech.wazzup24.com/v2/users'
-H 'Authorization: Bearer <client_access_token>'
-H 'Content-Type: application/json'
-d '{
"user_ids": [
"1"
]
}'

Response example:

{
"data": null,
"meta": {
"timestamp": 1759393502
}
}

Result: User id: 1 has been deleted.

Configuring Users

Use this method to configure user access to chats and optionally hide contact phone numbers within their chat interfaces.

Configuring Roles

A role defines user permissions: which chats they can view and whether they can send messages.

Assign one of the following roles to each user:

• "Manager", seller — can only message contacts they are assigned to in the CRM. Does not see other users' conversations.
• "Supervisor", manager — can see all conversations and message any contact.
• "Quality Control", auditor — can view all conversations but cannot send messages.

Enable the "Receives new clients" setting (allow_get_new_clients) for users who should receive messages from new contacts — those not yet assigned to anyone in the CRM.

Enable the push_input_output_message_events_for_managers setting if users with the Supervisor role should receive notifications from all chats. This is commonly used in online stores and support departments where customers reach out with simple questions and it doesn't matter who replies — the first available agent responds.

When this setting is disabled, users with the Supervisor role receive notifications only for chats they are personally responsible for. In the Wazzup iframe:

• Chats they are responsible for show red unanswered badges;
• Chats belonging to other managers do not trigger notifications and display gray unanswered badges.

Hiding Phone Numbers

This setting helps protect your customer base.

When enabled, phone numbers are hidden in the Wazzup iframe and mobile apps. Authorized employees will only see the first and last digits — for example: +371 55 *** *34.

PATCH /v2/settings
├── user_roles[] *
│ ├── channel_id *
│ ├── user_id *
│ ├── role *
│ └── allow_get_new_clients *
├── hide_phone_numbers_for_user_ids[]
└── push_input_output_message_events_for_managers *

user_roles (object)

Request Example:

{
"user_roles": [
{
"channel_id": "5d1c7dd8-bbfd-42d8-830d-3163b57e760",
"user_id": "user_1",
"role": "manager",
"allow_get_new_clients": true
}
],
"hide_phone_numbers_for_user_ids": [
"user_1"
],
"push_input_output_message_events_for_managers": true
}

Successful Response Example:

{
"user_roles": [
{
"channel_id": "5d1c7dd8-bbfd-42d8-830d-3163b57e760",
"user_id": "user_1",
"role": "manager",
"allow_get_new_clients": true
}
],
"hide_phone_numbers_for_user_ids": [
"user_1"
],
"push_input_output_message_events_for_managers": true
}

Retrieve Role Settings

Response Example

{
"user_roles": [
{
"channel_id": "5d1c7dd8-bbfd-42d8-830d-3163b57e760",
"user_id": "user_1",
"role": "manager",
"allow_get_new_clients": true
}
],
"hide_phone_numbers_for_user_ids": [
"user_1"
],
"push_input_output_message_events_for_managers": true
}