To ensure the best experience using Swapcard—especially for features like live video, Roundtables, and messaging—you may need to adjust your network settings. This is especially important if you're accessing Swapcard from a restricted network, such as a corporate firewall.
Which domains should be whitelisted?
These domains must be accessible for the app and media features to work correctly:
*.swapcard.com(Main platform access)*.tokbox.com(Used for video calls and Roundtables)*.opentok.com(Also related to video services)*.mux.com(Video content delivery)
✅ Tip: Domain-based whitelisting is strongly recommended over IP whitelisting to reduce future maintenance.
Which IP addresses should be whitelisted?
These IPs may be needed for environments with strict firewall rules:
Swapcard infrastructure outbound IPs:
13.37.93.76
13.37.88.21
35.181.27.117
54.246.158.150
52.51.3.111
34.255.150.197
Email server IPs:
161.38.206.33
141.193.33.237
161.38.205.104
185.250.238.18
What CDN IP ranges need to be allowed?
Swapcard uses third-party CDN services for content delivery. You may need to allow the following IP ranges:
Which ports should be open for Swapcard to work?
For full functionality, these ports must be open:
Required
TCP port 443: Must be open for HTTPS and secure real-time services
⚠️ Ensure non-web traffic (e.g., UDP/TCP signaling) can also pass through this port
UDP port 3478: Recommended for STUN traffic used in video calls
Optional but recommended
UDP ports 1025–65535: Recommended for optimal media performance, reducing reliance on TURN servers
Blocking any of the above may prevent Swapcard’s video, messaging, or real-time features from working correctly. By ensuring these network rules are in place, your users can enjoy seamless interaction across all devices and session types.
Read more