Orchestrator API definition (Swagger) or documentation wrong

Help Orchestrator
,
1

The documentation of the orchestrator cloud api (Consuming Cloud API) has the following example of creating an authentication token:

POST https://account.uipath.com/oauth/token
{
“grant_type”: “refresh_token”,
“client_id”: “[Client Id]”,
“refresh_token”: “[User Key]”
}

Which is quite different from the swagger example:

POST ​/api​/auth​/oauth​/token
{
“grant_type”: “None”,
“client_id”: “string”,
“client_secret”: “string”,
“scope”: “string”
}

While the first example is working fine, I don’t know what to do with the second one, as I couldn’t figure out what the “scope” parameter was.

Generally was it for me not possible to use any of the swagger definitions. Are they up to date?

2 Likes
2

Hello @T0Bi!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

3

Anyone from Uipath staff can help with this? I already saw a couple of topics discussing the Orchestrator API and indeed, there’s a lot of confusion between the old basic Auth and the new one implemented for Automation Cloud.
This is also affecting the documentation which is clearly different in the Docs and in Swagger (https://cloud.uipath.com/[logical name]/[tenant name]/swagger/index.html

I would really appreciate some feedback here.

1 Like
4

Hi @Gil_Silva
Check this documentation, it helped me a lot.

Regards

5

Hi @Benjamin_Vazquez,
Thank you for your answer.
Yes, I checked and indeed is helpful, basically I can do everything through Postman, authenticate and any other API calls.
My problem is how to configure this authentication as OAuth2.0, since I’m trying to create a Custom Connector in Power Automate to communicate with UiPath.
(there’s a nice connector in the UiP marketplace - Microsoft Flow Connector - RPA Component | UiPath Marketplace - but it doesn’t tackle the auth configuration)

image
image667×763 12.6 KB

If you have some insights on that, I would really appreciate.
I can create individual API calls to authenticate, get the refresh token and then use it for every other call, but I want to have this authentication encapsulated in the connector.

6

I’m trying to do exactly the same and I have been not able to authenticate :frowning: