Skip to main content
Network Requirements
Saurabh Bajaj avatar
Written by Saurabh Bajaj
Updated over a week ago

Swiftlane Networking Requirements

API Endpoints

Customers should allow complete outbound connections from access point devices, on port 80 and 443. This would ensure the highest level of reliability for the system.

However, here are some specific endpoints called from the Swiftlane system. Please note that this is a changing set of requirements and may affect future performance of the device. Highly recommended that allow all outgoing 80/443 traffic from the Swiftlane devices.

admin.swiftlane.com/*
โ€‹[swiftpass.ue.r.appspot.com/](https://swiftpass.ue.r.appspot.com/)*

Swiftlane Email IP Addresses to be Whitelisted

  • 149.72.134.227

  • 149.72.121.190

  • 149.72.202.229

  • 149.72.222.121

  • 149.72.237.105

  • 167.89.112.241

  • 198.21.4.83

  • 149.72.169.55

  • 149.72.134.227

Swiftlane Door Controller Panel Firewall Config

  • Enable bidirectional connections for port 80 and 443

  • Enable bidirectional mqtt.googleapis.com:8883 (for communication between API and door controller hardware)

  • Enable bidirectional cloudiot.googleapis.com:443 (for communication between API and door controller hardware)

SwiftReader Firewall Configuration

Enable Bidirectional communication on ports 80 and 443

port 5223 17.0.0.0/8 outbound: Apple Push Notification service (APNs) for Apple devices.

IP range `17.0.0.0/8`` is an IP range block assigned to Apple Inc so this merely represents that apple push notification servers would connect to the port 5223 on the reader devices for push notifications.

Email Domain Authentication (User enrollment flow)

Make sure that the Swiftlane.com email domain is whitelisted as a trusted domain on the spam filters, in case you have very strong email spam rules, or if you see swiftlane.com emails going to spam. Swiftlane already uses DMARC, and sender authentication to ensure high deliverability of our emails.

Intercom Calling

Swiftlane intercom uses webrtc based video and audio intercom, which requires specific endpoints and paths to be enabled.

WebRTC Signaling Server

Websocket: wss://global.vss.twilio.com/signaling

This opens a web socket connection for WebRTC signaling.

Video events Websocket

Websocket: wss://sdkgw.us1.twilio.com

Websocket: wss://sdkgw.us1.twilio.com/v1/VideoEvents

Did this answer your question?