Some of our developers asked if there was a way to restrict access to VoxImplant HTTP API and only allow it for certain IP addresses or networks when api_key is being used. Today we updated the service and this setting is now available for all VoxImplant developers. It can be set in HTTP API Access part of the control panel.
Sign Up for a free Voximplant developer account or talk to our experts
Growing a business involves lots of moving parts, but no matter how large your customer base gets, customer experience (CX) should hold a top spot among your business responsibilities as your company grows.
Adding peer-to-peer communications to an application is relatively straight-forward. Developers can leverage WebRTC APIs or a CPaaS service to quickly add real time voice and video to their web or mobile app. But, what if you want to hold a meeting with more than two people? How can you leverage powerful WebRTC APIs to build a multi party conferencing application?
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.