Caleb_Dixon | 2017-12-18 23:48:10 UTC | #1
Hi Team,
I'm trying to execute a data action that retrieves a users GUID from CRM based on an inputted registration number.
The request works through postman both on our internal network and an external network.
The error I receive within in PureCloud is { "message": "The request timed out.", "contextId": "aeb36ecf-b6cb-479f-8a53-5bd3d3a1fc29" }
I looked into the amazon IP addresses that are being used and contacted our network contractors who advised that API requests from and to our server should work. He advised to do a netstat command to see if I could see any communication with a PureCloud address. I checked and couldn't find any IP address associated with PureCloud.
I have configure the basic authentication within the integration and use the same authentication as the ones used in postman.
Here is my request below
Input Contract: { "title": "RetrieveContactGUID", "description": "Retrieve callers GUID based on Reg number", "type": "object", "properties": { "regNumber": { "type": "string", "maxLength": 6, "pattern": "^[0-9]{6}$", "description": "The reg number used to query the CRM" } } }
Output Contract: { "title": "RetrieveContactGUID", "description": "Return GUID as output", "type": "object", "required": [ "guid", "status" ], "properties": { "guid": { "type": "string", "description": "The GUID retrieved from CRM" }, "status": { "type": "string", "enum": [ "SUCCESS", "ERROR" ] }, "messageCode": { "type": "string", "maxLength": 15 }, "messageText": { "type": "string", "maxLength": 255 } } }
Request: { "requestUrlTemplate": "https://trbwebapiuat.trb.sa.edu.au:4430/Purecloud/RetrieveContactGUID?regNumber=${input.regNumber}", "requestType": "GET", "headers": { }, "requestTemplate": "${input.rawRequest}" }
Response: { "translationMap": {}, "successTemplate": "${rawResult}" }
I'm not too sure why the request won't communicate with my web service from PureCloud.
Any sort of help or recommendations would be greatly appreciated.
Thanks,
Jason_Mathison | 2017-12-19 14:59:07 UTC | #2
The Data Action Service currently only supports talking to a web service on port 443. Is it possible to make your web service accessible on that port?
Jason_Mathison | 2017-12-21 18:25:25 UTC | #3
Our requirements documentation is being updated to reflect that we only support connecting to web services on port 443. We are also going to look into detecting this situation and failing fast with a decent error message.
system | 2018-01-21 18:25:32 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 2261