Required PureCloud domains

From Genesys Documentation
Revision as of 13:35, January 17, 2020 by WikiSysop (talk | contribs)
Jump to: navigation, search

In order for agents to view journey context data from Genesys Predictive Engagement, specific PureCloud domains must be available.

Required domains for all implementations

As a cloud-based product, Genesys Predictive Engagement needs access to various websites in order to work. When you implement Genesys Predictive Engagement, be sure your network configuration allows access to the following domains:

  1. All of the PureCloud domains listed in the Domains and IP Addresses section of this article
  2. https://dhqbrvplips7x.cloudfront.net/
  3. The region-specific PureCloud domains listed in the following sections:

Notes about the required Genesys Predictive Engagement domains

Domain Used for
https://api.mypurecloud API resources
https://apps.mypurecloud Non-cached static assets
https://journey-websockets.mypurecloud Real-time events
https://dhqbrvplips7x.cloudfront.net/ Cached static assets
https://journey-websockets.mypurecloud Altocloud-specific domain content
https://login.mypurecloud/ Logging in users

Americas (US East)

  • https://api.mypurecloud.com
  • https://apps.mypurecloud.com
  • https://journey-websockets.mypurecloud.com

Americas (US West)

  • https://api.usw2.pure.cloud
  • https://apps.usw2.pure.cloud
  • https://journey-websockets.usw2.pure.cloud

EMEA (Dublin)

  • https://api.mypurecloud.ie
  • https://apps.mypurecloud.ie
  • https://journey-websockets.mypurecloud.ie

EMEA (Frankfurt)

  • https://api.mypurecloud.de
  • https://apps.mypurecloud.de
  • https://journey-websockets.mypurecloud.de

Asia Pacific (Sydney)

  • https://api.mypurecloud.com.au/
  • https://apps.mypurecloud.com.au/
  • https://journey-websockets.mypurecloud.com.au/

Asia Pacific (Tokyo)

  • https://api.mypurecloud.jp/
  • https://apps.mypurecloud.jp/
  • https://journey-websockets.mypurecloud.jp/
Retrieved from "https://all.docs.genesys.com/ATC/RequiredPCDomains (2024-07-27 23:27:58)"
Comments or questions about this documentation? Contact us for support!