Authenticate fails for Orchestrator API

Use the same credentials as here but fails… Any suggestions?
https://account.uipath.com/login

Hi @Artem_Ibragimov

Have you created another account for account.uipath.com
Try to create another account it will work

Thanks
Ashwin S

@AshwinS2 I’m sorry what?

Why would I create another account?
The link you gave me is incorrect

hi @Artem_Ibragimov
Check this account link
https://platform.uipath.com/portal_/unhandlederror?client_id=&connection=&lang=en-US%2Cen%3Bq%3D0.9&error=invalid_request&error_description=missing%20client%20parameter&tracking=a46307d5e0eafafaf917

Click on login and pass ur account name

Thanks
Ashwin S

Again wrong url

If I click Login, I can login, but API still fails!

You need to pass your tenant name in the request along with your username and password:

{
  "tenancyName": "string",
  "usernameOrEmailAddress": "string",
  "password": "string"
}

For more details about such API requests, please check your tenant’s Swagger page:
https://platform.uipath.com/<acount_name>/<service_name>/swagger/
You can find you Account Name and Service Name by logging into https://platform.uipath.com.

2 Likes

Hi @Artem_Ibragimov

Actually, for Cloud API it is not as easy. The Authenticate endpoint will not work anymore. See here how to authenticate instead:
https://orchestrator.uipath.com/v2019/reference#consuming-cloud-api

And see here for a robot I made that does all the steps for you (together with extra workflows for a sample API call):

Thank you @loginerror this works.
Just FYI, current API of UIPath is a mess. hard to navigate, a lot of outdated articles. Really frustrating.

Though happy to see that you’re moving to oAuth

Does anybody even use UiPath ? Really guys? How come a documentation has hard coded client_id and no information where I can find client_id associated with my account?

HORRIBLE!

I’m literally sitting and doing reverse engineering, looking at the data that your websites sends and stores on my computer… and trying to match it with API.

We were considering contacting your sales team to purchase enterprise version, but after working with your API I have huge doubts…

Just make someone from outside use your make an API request to your servers and see how it goes. How much time he spends. Or try it by yourself to follow your documentation.

THE WORST API THAT I’VE SEEN IN MY LIFE! Damn 568 million! 7b valuation. Seriously?

Hi @Artem_Ibragimov

I realize it is a bit tricky to get started with the Cloud Platform API. The current guide is a temporary workaround given our migration to Auth0 (which removed the possibility to simply authenticate with basic authentication).

All the steps in this guide are unfortunately necessary. As far as concrete values in the guide, the variable ones are always between brackets []. This means that client_id should simply be taken as is and doesn’t need to be personalized.

However, if you do not feel like going through the entire guide, simply fire up the process attached in the below post that will do it for you:

Also, please keep in mind that all of this concerns only the Public Preview of our Cloud offering.
The on-premise installation of Orchestrator Enterprise still uses the standard basic authentication API, in which you simply call this endpoint and get a bearer token in return:

You can see the difference in documentation for both scenarios here:
image

EDIT
Last remark - after you go through all the steps and get your refresh_token, it is permanent. This means that afterwards you can make 1 api call to refresh your access_token without the need to go over all the steps again :slight_smile:

Thanks! Seems working now

1 Like