Some of our clients clients have created integrations with Splash in which Splash is programmed to send information to a specific API endpoint on their servers.
For example: a client may want Splash to send a file via a File Transfer Protocol (FTP) at a regularly scheduled cadence; or maybe Splash needs to ping their servers any time someone RSVPs.
A subset of these clients will have internal security policies that are established to restrict the traffic allowed into the servers. This means only authorized IPs and users can access their servers.
In the FTP example, the client would want to permit Splash access to their API, while also preventing potentially malicious users from detecting the FTP endpoint and attempting to break in.
By putting Splash's IP address on a "white list," Splash is granted the necessary permissions to maintain the integration.