Web API service response

[AkshayaR]

Hi Team,

We have been trying to send a POST request to REST API service. The response is received as expected while trying to send the request in postman/ARC as well as through Utility - HTTP VBO. But while trying to configure the same through Web Service API under System tab, the response status code is updated as 200 but the response content is received as a series of non printable ascii characters.

We need your inputs on what we are missing here.

Thanks,
Akshaya

------------------------------
Akshaya R
------------------------------

[AkshayaR]

Hi Eric,

As mentioned above, I did try after setting the sysparm_display_value=true. It still didn't work out.
This is how I appended this parameter value to the base url.

https://[Tenant URL]/newSR/<appname>/f94979231b69b894c273848dcc4bcb49/da4b14c31b7bb0d0c273848dcc4bcb55/12345&sysparm_display_value=true

Could you please let me know if we are missing out anything here?

Thanks,
Akshaya

------------------------------
Akshaya R
------------------------------

[ewilson]

@Akshaya R,

When adding query params to a URL, the first param is preceded by a "?" and then additional params are delineated by "&".​ So your example above should look like:

https://[Tenant URL]/newSR/<appname>/f94979231b69b894c273848dcc4bcb49/da4b14c31b7bb0d0c273848dcc4bcb55/12345?sysparm_display_value=true 

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

[AkshayaR]

Hi Eric,

Replacing '&' with '?' didn't help. Receiving the same response content like before.

Thanks,
Akshaya

------------------------------
Akshaya R
------------------------------

[ewilson]

Hello @Akshaya R,

This is definitely a peculiar situation. The only other thing I can think of, without seeing the actual definition of the Web API service entry, is to use Fiddler or ​Wireshark to capture the HTTP Request/Response created from Postman and the same Request/Response created while using the Web API service and then compare the two to see if there is some obvious difference in the headers, layout of the request, etc.

Outside of that, my recommendation is to move forward with the HTTP VBO for this integration. You can also open a ticket with Blue Prism support as it appears you may have identified a bug in the Web API service feature.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

[AkshayaR]

For now we are using HTTP VBO which works fine.

And probably we will also raise a support ticket to know more so as to identify the root cause which might help us in understanding better about Web API services.

Thanks much Eric for providing your valuable insights.

Regards,
Akshaya

------------------------------
Akshaya R
------------------------------