01-05-2024 10:19 AM - edited 01-05-2024 10:21 AM
When setting up the API request in the Five9 Connector, it's crucial to bear in mind that the parameters are case-sensitive. They must align with the specified naming conventions both in the Connector and within your Invoca Marketing Data Field API names. Precision in matching these conventions is key to seamless configuration.
Endpoint:
https://invoca.net/api/2018-02-01/transactions.url_encoded_form
Required Fields:
calling_phone_number
call_start_time (ensure call start time matches approved format which is a 17 digit number - yyyymmddhhmmssSSS)
oauth_token (Generate this token in Invoca:
https://community.invoca.com/t5/invoca-apis/how-to-pull-a-new-oauth-token-to-authorize-third-party-a...
), do not add the @ symbols around the token or the user will be prompted to enter their Invoca credentials in the Five9 platform.
transaction_id (this is needed for 1:1 matching in Invoca)
agent_full_name
agent_id
disposition
campaign_name
skill_name
call_id
user_name
type
Additionally, it is advisable to follow best practices by using distinct API tokens for the PreSense API and the Connector. Sharing the same API token for both could potentially result in API Request issues. Maintaining separate tokens ensures smoother functionality and mitigates the risk of complications.