External Contact APIs
By integrating these prebuilt API Rules into AppBase, users can easily harness the Genesys Conversation API's full potential. These rules might include predefined request and response formats, authentication mechanisms, error handling procedures, and other essential components that are essential for successful API communication.
Methods in Extensions
Before executing these methods, you should init auth token:
using DCM.GenesysHelper.Services;
string pureCloudUrl = ConfigurationManager.AppSettings.Get("PURECLOUD_URL");
string clientId = ConfigurationManager.AppSettings.Get("PURECLOUD_CLIENTID");
string clientSecretId = ConfigurationManager.AppSettings.Get("PURECLOUD_CLIENTSERCRETID");
int regionHost = DcmConvertHelper.SafeObjectToInt(ConfigurationManager.AppSettings.Get("PURECLOUD_REGIONHOST"));
AuthService authService = new AuthService();
authService.SetAuthToken(pureCloudUrl, clientId, clientSecretId, (PureCloudRegionHosts)regionHost);
How to get debug enabled flag. Debug data will be available in Conversation History (if we have ConversationId) or the system monitor.
string result = request.AsString("GEN_ADVANCED_LOGGING");
bool isDebugEnabled = result == "1";
Method | Definitions |
---|---|
DCM.GenesysHelper.Services.ExternalContactService.Get | Description: Returns exactly one External Contact. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.ExternalContactService.GetAll | Description: Searches all External Contacts. The existing Genesys API can only search across all fields.. Input:
Output:
Example:
C#
|
DCM.GenesysHelper.Services.ExternalContactService.UpdateContact | Description: Updates an existing External Contact. Input:
Output:
Example:
C#
|