topic RE: API in Product Forum

API

aseelodeh — Sun, 02 Jan 2022 14:54:00 GMT

HI,

I've created an account service ( but there is no API interact permission option ) and set the credentials.
however, im getting this error from bp when running the actions

------------------------------
aseel odeh
------------------------------

RE: API

lookman — Mon, 03 Jan 2022 17:27:00 GMT

Hi Aseel.

In the service you created, what authentication type did you specify? From the screen shot, it looks to me that you have selected OAuth2.0:

jack

------------------------------
Jack Look
Sr Product Consultant
Blue Prism
------------------------------

RE: API

aseelodeh — Tue, 04 Jan 2022 07:08:00 GMT

hi dear,

yes it's OAuth2.0 client credentials

------------------------------
aseel odeh
------------------------------

RE: API

joefarr — Tue, 04 Jan 2022 08:29:00 GMT

Hi Aseel

Which version of Hub/Interact are you using? The Interact Remote API Service account was only added in 4.4. If you're using 4.3 or earlier, you can find your secret key in a file which, by default, is located here:

C:\Program Files (x86)\Blue Prism\Interact Remote API secret key.txt

This part of the online help is the relevant section.

Hope this helps!

------------------------------
Joe Farr
Product Consultant
Blue Prism Limited
------------------------------

RE: API

cvmac — Mon, 21 Feb 2022 11:23:00 GMT

Hi @aseelodeh - I am receiving same error message for you for BOX APIs, have you had any luck progressing this?

------------------------------
Chloe MacIntosh
Automation Developer
Zurich Insurance
Europe/London
------------------------------

RE: API

joefarr — Mon, 21 Feb 2022 11:40:00 GMT

Hi Aseel and Chloe

This error shows when there is a problem with the credentials set up for the API.

In Hub, there is a known issue where the secret key needs to be created without a "+" in it. If your secret key has a "+", you can regenerate the key until it doesn't have the symbol.

I'm not sure if this is the same issue with BOX, Chloe, but it looks like the API is not able to get the authentication token prior to making the API call.

Hope this helps

------------------------------
Joe Farr
Product Consultant
Blue Prism Limited
------------------------------