Orchestrator API - OrganizationUnitId and other problems


since switching to OAuth2 (confidential application) we’re facing several issues which we haven’t had before.

One of them is the header X-UIPATH-OrganizationUnitId.

Apparently this header is needed for most (if not all) requests, but this is documented nowhere. I only found out about this when searching for the errorCode 1101.

Additionally, when using this header to get processes (/Releases) we’ll only get the processes of specific folders depending on the header we’re using.
In the past it was possible to the all the processes.

Is there any way to get all processes/releases of all folders with a single request?

Another problem that others have stated as well, is that you cannot give API permissions only to certain folders. Before OAuth you used a specific user and could set the permissions to whatever you needed. This isn’t possible anymore either.

I’d like to add that we’re using application scopes, not user scopes. Because I think some of the problems are exclusive to application scopes.

Had a conversation about this with the UiPath support. Answer:

The parameter [X-UiPath-OrganizationUnitId] must be used for external applications.
This is a mandatory parameter in latest versions, you can find official documentation here .
I am afraid that you will not be able to use an API in order to Get all processes of all folders.

My workaround will be to first use the GET /Folders request to get all folders and then call GET /Releases for every folder.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.