Update omnichannel user by client user id

АРІ еndpoint to update omnichannel user's data by specifying the client_user_id identifier.

Log in to see full request history

арp_push_token is considered valid if it meets one of these two conditions:

  1. The text consists of at least 64 characters in the lower case of the hexadecimal number system (0-9 and a-f) and does not contain other characters;
  2. The text has 22 characters, followed by a colon, after which it may contain any number of characters.

📘

By default, the VIP parameter has the value “0” (non-payer).

📘

You can add any parameters to the "fields" section to transmit user information that is unique to your product. It is important that the values of the same parameter are transmitted in the same format.

Path Params
int32
required

Project identifier;

string
required

User identifier on the client's side.

Body Params
string

User name (maximum 128 characters);

string

User phone number to send SMS;

string

User email address;

string

User device token (APNs / Firebase authorization tokens are supported). The token type is determined automatically, and the sending method is selected accordingly;

string

User language (2-character language code according to ISO 639-1) (for example: EN, FR, UK, RU);

string

User's country (2 or 3-character country code according to ISO 3166);

string

0 – Unknown, 1 – Desktop, 2 – Mobile (Mobile Browser + Tablet), 3 – Android App, 4 – iOS App;

string

User gender: m – male, f – female;

boolean

User status: 1 – payer, 0 – non-payer;

int32

User age (range of values: from 0 to 150 years);

string

Link to the user's photo (URL);

string

Auth key – key for automatic user authorization on the client side (maximum 255 characters).

Responses

Language
Credentials
:
Click Try It! to start a request and see the response here! Or choose an example:
application/json