Whether you are enforcing strict Firewall policies, connecting with API, or securing your voice flow, understanding SnapCall's IP address whitelisting scenarios is essential.
Here is a roundup of the IP address details from across our platform.
REST API
The REST API's IP addresses are highly dynamic across a vast range, so it's not practical to whitelist based on IP addresses. Instead, we recommend you allow all outbound HTTPS and WSS traffic to any *.snapcall.io subdomain.
SnapCall Client & SDKs
The original SnapCall web client and also SDKs allow you to connect directly to SnapCall from a web browser or a custom mobile application.
Here are the network requirements for SnapCall web client and SDK connections:
IP | Server-side port used | Protocol |
63.34.87.151 | 443/80 | TCP |
63.34.87.151 | 80 | UDP |
52.211.244.22 | 443/80 | TCP |
52.211.244.22 | 80 | UDP |
Bandwidth Requirements
Product | media | Platform | Codec | Bandwidth required* dynamically adjustable |
SnapCall web client | audio | desktop/responsive | OPUS | 10-40 kbits/sec |
SnapCall SDKs | audio | mobile | OPUS | 10-40 kbits/sec |
SnapCall web client | video | desktop/responsive | VP8 | 600-800 kbits/sec |
SnapCall SDKs | video | mobile | VP8 | 600-800 kbits/sec |
* The Bandwidth value shown is required for both directions