Whitelisting LivePerson services

If you have IP restrictions in place, you’ll need to do some whitelisting so that Conversation Builder can make calls to your brand’s systems and vice versa. The specifics on what to whitelist vary depending on whether your implementation is hosted in the LivePerson Cloud or Amazon Web Services (AWS) environment:

  • LivePerson Cloud: This is your environment if you access Conversation Builder from within LiveEngage, i.e., your browser is pointing to the “liveperson.net” domain.
  • AWS: This is your environment if you access Conversation Builder directly, i.e., your browser is pointing to the “livepersonai.com” domain.

LivePerson Cloud

If your implementation is hosted in LivePerson Cloud, you can find all details on whitelisting here in the Knowledge Center.

AWS

If your implementation is hosted in AWS, in general, use Amazon’s list of IP ranges to guide your whitelisting. Be aware that the list is updated periodically by Amazon, so check back periodically as well.

More specifically, refer to Amazon’s ip-ranges JSON file that you can access from the AWS IP Address Ranges page (see the “Download” section). The sections below describe the IP ranges of interest.

Brand system calls to Conversation Builder
To use this… Whitelist this in the ip-ranges file… Notes
Conversation Builder's web portal All IPs for the CLOUDFRONT service and the EC2 service Whitelisting the domain is recommended over whitelisting the IPs.
Web View integration API All IPs for the EC2 service  
Conversation Builder calls to brand systems
To use this… Whitelist this in the ip-ranges file…
Agent connectors to LiveEngage All IPs for the EC2 service
API integrations All IPs for the EC2 service
Custom integrations (if any developed specifically for your brand) All IPs for the EC2 service

Whitelisting rich media

Images and other media

You must whitelist the domains in all URLs for images, videos, and audio files used in interactions. Contact LivePerson Support to assist with this.

If you've enabled the Shorten URLs setting in a bot's Bot Settings to shorten lengthy web links, the shortened domain that's applied to all URLs must also be whitelisted. The shortened domain varies by region, and the domain for your region appears below the setting. An example is below.

For Facebook, the owner of the Facebook page must whitelist the domains (shortened or otherwise) in all web link URLs, including button links, within the Facebook page settings.