Additional API access setting - allowed IP addresses/networks

2015-02-26 21:22:40
87498
0

 

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

Add your comment

Name*
Email*
Message

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

Recommended posts

An Introduction to Selective Forwarding Units

An Introduction to Selective Forwarding Units

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?

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.