Managing Users Changes in March 2019

2019-01-23 14:26:39
79093
0
Blog picture

Please check the logic of your application with our HTTP API:

  1. From the beginning of March, users will be created within one application, and not within the company's account as it was before.
  2. 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

  1. The application_id and application_name parameters of all API functions will no longer accept arrays.
  2. 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).

 

Sign Up for a free Voximplant developer account or talk to our experts

Add your comment

Name*
Email*
Message

Your comment has been added and will be published after moderation.

Recommended posts

Voximplant Kit vs Talkdesk: Comparing contact centers for the small and medium enterprise

Voximplant Kit vs Talkdesk: Comparing contact centers for the small and medium enterprise

Any contact center manager considering a new cloud communications solution needs to do their “due diligence” before choosing a provider, including those in small to medium enterprises. The stakes are high for SMEs because your needs are unique and there are significant differences in the available providers. Your decision not only affects your organization’s budget, but also its business processes, customer experiences, and agent work environment.

What is a No-code Contact Center?

What is a No-code Contact Center?

If you’re involved in evaluating cloud contact center services, you’ve likely recognized two distinct categories and a big difference in the amount of technical expertise required to implement them. You’re attracted to the ease of use offered by contact center as service (CCaaS) offerings, but their fixed functionality doesn’t fit your business needs. In contrast, a cloud contact center built on a communications platform as a service (CPaaS) offering provides unlimited flexibility, but requires expensive software development resources to build a complete solution.