Correct URI for Orchestrator 2008.4 on-premise API calls after authorisation


I am using Orchestrator 2008.4 on-premise
I am able to get my bearer token using a POST to with the right headers en body.

Now, that I have the bearer-token, I am trying to make a call that just works…

do I have to use
or is it
or is it

please help!

Hi , welcome to the Uipath community forum
Once you get the authentication token , you need to post it to the same URL

Thanks for yor response but I can’t get it working.

To login I do a POST to
In de HTTP-Header I have “Content-type: application/json”
The body of the POST is:
“tenancyName” : Default",
“usernameOrEmailAddress” : USERNAME",
“password” : XXXXXX"

My response is

I did a POST again to
In the HTTP-Header I have
“Content-type: application/json”,
“X-UIPATH-TenantName: Default”,
“Authorization: Bearer [RESULT FROM FIRST REQUEST]”

You did not tell me what to put in the body, so my body is empty…

And my result is {“message”:“loginModel must not be null”,“errorCode”:0,“resourceIds”:null}

What should happen then? Do I get another token?

I got the community edition Cloud API version running, and I am able to start a Job there…
But on On-Premise it is different and documentation is confusing and not clear to me…

I still need help.
Some more information on the URL, header and body for next step would help!

results in:

{“message”:“You are not authorized!”,“errorCode”:0,“result”:null,“targetUrl”:null,“success”:false,“error”:{“code”:0,“message”:“You are not authorized!”,“details”:“You are not allowed to perform this operation.”,“validationErrors”:null},“unAuthorizedRequest”:false,“__abp”:true}

I think my account needs some rights to be set…


pass the authorization code in headers

Hello Dennis,
IN this video I show how to start the process on Orchestrator on-prem:

Cristian Negulescu

1 Like

Hello. That what is happening when i do the same things as you in video. Is there any options i need to apply - may be enable API use in orch, or something else i dont know?

Hello Aleksandr,
I don’t know what to say. Did you send the content type Json
my Postman has these defaults settings:

Cristian Negulescu

1 Like

try to open the swagger like this
The Orchestrator API Swagger definition can be accessed as follows, depending on your deployment type:

  • on-premise - add the following suffix: /swagger/index.html to your Orchestrator URL. For example,
    and test your commands
    API References
1 Like

Yes. Content type was OK.
This is what i get with swagger due VPN connected:

1 Like