Dan_Fontaine | 2018-01-16 21:31:02 UTC | #1
For a bridge server connector action, what are the contents of the Request Schema for a GET request with no properties? We are not passing any data as part of the request.
Richard.Schott | 2018-01-17 20:12:20 UTC | #2
Dan, The Web Service Data Dip bridge connector only supports POST as a verb. The web service it connects to would be responsible for converting that POST into a GET command "under the hood", if that's how you'd choose to implement it.
Web Service Data Actions (not on Bridge) are somewhat different. These support GET (and POST, PUT, and PATCH) as verbs. As GETs typically do not have a request body associated with them, you would leave the "Request Template" section of the configuration alone. Here's an example of a GET action request configuration:
{ "requestUrlTemplate": "https://myfancyAPI.net/search/SearchForStuff/${input.FirstThing}?searchTerms=${input.SecondThing}", "requestType": "GET", "headers": { "Authorization": "" }, "requestTemplate": "${input.rawRequest}" }
Notice that the substitution from the input contract occurs all in the URL template, not in the request body.
Hope that helps.
Dan_Fontaine | 2018-01-17 20:47:35 UTC | #3
Now you tell me :grinning: You should let Support know. We've been working on this for months (since November)! Also, we should update the Resource Center or Developer Center with this information as I was never able to find it and neither could Support.
tim.smith | 2018-01-17 20:50:39 UTC | #4
FWIW, the supported contracts are documented here: https://developer.mypurecloud.com/api/webservice-datadip/service-contracts.html
Richard.Schott | 2018-01-17 21:26:50 UTC | #5
And here's the documentation on the the request configuration for data actions: https://help.mypurecloud.com/articles/request-configuration-data-actions/
Dan_Fontaine | 2018-01-17 21:41:30 UTC | #6
Yes, I meant documentation for Bridge Connector Actions.
I was able to get everything to work with the Pure Cloud Web Services Data Action but we couldn't figure out why the same API was failing for a Bridge Connector Action. And, as you explained, we can only use POST for the Connector Action. Thanks!
system | 2018-02-17 21:46:21 UTC | #7
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: 2361