Please check the logic of your application with our HTTP API:
- From the beginning of March, users will be created within one application, and not within the company's account as it was before.
- User names* will become unique within the application. You can use the same username in different applications.
* If you start creating new users before March 1, their names should differ from each other. In March, with the new release, it will be possible to create users with the same name.
What will change in the API
- The application_id and application_name parameters of all API functions will no longer accept arrays.
- If a user is bound to several applications at the time of migration, he will be cloned (added to all applications in which he was bound). At the same time, the «old» ID with statistics will remain in the application to which it was bound last. In case of using a separate balance, it will be transferred according to the same principle: for cloned users, it will be zero balance.
Changes in the specific API functions
AddUser
- Be sure to specify one of the fields: application_id or application_name.
BindUser
- Removed completely.
DelUser
- Required parameters, one combination of:
- user_name (string or array) + application_id;
- user_name (string or array) + application_name;
- user_id (string or array).
SetUserInfo
- Required parameters, one combination of:
- user_name (string or array) + application_id;
- user_name (string or array) + application_name;
- user_id (string or array).
GetUsers
- Required field application_id.
BindUserToQueue
- Newly added required parameters, one combination of:
- user_name (string or array) + application_id;
- user_name (string or array) + application_name;
- user_id (string or array).
BindSkill
- Newly added required parameters, one combination of:
- user_name (string or array) + application_id;
- user_name (string or array) + application_name;
- user_id (string or array).
