WEB Rest POST API 16.3

RE: WEB Rest POST API 16.3

Peter Lewis — Wed, 17 Jun 2020 22:01:14 GMT

Oh sorry my mistake - I forgot that you can't use a!httpQuery() for a POST (you must use a process model in this case). The best way to do this is to set up your http query in a process to run first. Then, save the results into a process variable and pass the variable as an input to your form. Here's an example of how I'd suggest setting it up (ignore the deprecated node - yours should display correctly in 16.3):

You must use activity chaining to query the data first using this node. Then, save the output of the HTTP Query into a process variable that you can reference in your interface. Note: you might need to use a function like a!fromJson() if your response body is JSON.

RE: WEB Rest POST API 16.3

antoniom0002 — Wed, 17 Jun 2020 20:38:03 GMT

Hi Peter,

first of all, really thanks for you suggestion.
I tried in this way but I don't understand how to use it into the process model in order to store the response of the API.

I tried also the following:

a!httpQuery(
url: "URL",
method: "HEAD",
headers:{
a!httpHeader(
name: "Content-Type",
value: "application/json"
)
}
)

but unfortunately it seems that we cannot use POST with this httpQuery function.

Can I ask you if you have a snippet or some example that can clarify better how to configure it and save the response into the process model?

RE: WEB Rest POST API 16.3

Peter Lewis — Wed, 17 Jun 2020 20:18:49 GMT

The alternative available in 16.3 is the HTTP Query function / smart service. This function doesn't have nearly as many features as the Integration design object (which was introduced in 17.2), but it should still work for basic POST requests where you retrieve data.