You’ll need to Authorize via the API to retrieve an access token, or Update the access token for the user. Looking at the your message, the bot didn’t even execute the API, because it wasn’t authorized or shared the access token in the REST API command



see:https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/control-room-api/cloud-control-room-apis.html

v1 Authentication API: https://docs.automationanywhere.com/bundle/enterprise-v2019/page/auth-api-supported.html#tag/auth
v1 Authentication API: https://docs.automationanywhere.com/bundle/enterprise-v2019/page/auth-api-supported-v2.html

Hi!

How did you solve it?

For anyone looking at this post currently, you must now use the /v2/authenticate API call. The above-mentioned /v1/authenticate has been deprecated. 

When you start off with this API call, you will receive a JSON message with a “token” key. That value must be saved as it is needed for subsequent API calls. That token is passed into these API calls in the header key “X-Authorization”. 

If you receive a “code” in the JSON message, that means something went wrong including the UM1117 error. Check your JSON message sent in the body to make sure it matches the expected info (e.g., for the authentication call {“username”:”abc”,”password”:”def”}).