Getting 401 - Anauthorized errro while sending request to Orchestrator using odata/Jobs/UiPath.Server.Configuration.OData.StartJobs endpoint

Hello,

I am encountering a 401 - Unauthorized error while sending a request to the following Orchestrator endpoint:

Endpoint: odata/Jobs/UiPath.Server.Configuration.OData.StartJobs

This API was working fine until the previous day, but it suddenly stopped functioning. Has anyone else experienced this issue? Is there any changes in API functionality?

Please guide me on how to resolve it.

Regards,
Keyur

A 401 from …/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs usually means the request isn’t hitting Orchestrator with the right token, URL, or folder header.

  1. Check your URL – It should look like:
    https://cloud.uipath.com/{org}/{tenant}/orchestrator_/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs
    Replace {org} and {tenant} with what you see in your Automation Cloud URL. Keep “orchestrator_” in place.

  2. Use a valid access token with the right scopes – Make sure it’s an access_token (not an ID token) and includes OR.Jobs (Write), OR.Folders (Read), and OR.Processes (Read). Tokens expire in about an hour, so generate a fresh one if unsure.

  3. Send the folder info – Add one of these headers so Orchestrator knows which folder to use:
    X-UiPath-OrganizationUnitId:
    or
    X-UiPath-FolderPath: <Folder/Path>

  4. Required headers
    Authorization: Bearer <your_access_token>
    X-UiPath-OrganizationUnitId: <folder_id> (or X-UiPath-FolderPath)
    Content-Type: application/json

  5. ReleaseKey must match a process in that folder – Get it first:
    GET https://cloud.uipath.com/{org}/{tenant}/orchestrator_/odata/Releases?$filter=Name eq ‘YourProcessName’&$select=Key
    Use the returned Key in your StartJobs body.

Example request (Modern folders) – Fill in your values for ACCESS_TOKEN, FOLDER_ID, and RELEASE_KEY, then POST to the URL above with a JSON body like:
{ “startInfo”: { “ReleaseKey”: “YOUR_RELEASE_KEY”, “Strategy”: “ModernJobsCount”, “JobsCount”: 1, “RuntimeType”: “Unattended”, “InputArguments”: “{}” } }

Most common 401 causes:

  • Wrong org/tenant in URL
  • Folder header missing or incorrect
  • Token is expired, wrong type, or missing scopes
  • Using on-prem Orchestrator without adding X-UiPath-TenantName:

Fix those, and the request should go through without a 401.

@botautomation,

Will need more details to understand this. From where you are sending this API request. How you are authenticating?

Thanks for your quick response.

The integration was working fine until yesterday, and I haven’t made any changes to the token generation, release key, or StartJobs endpoint configuration.

I am still able to generate the token successfully. However, when I try to use the new token to fetch the Release Key, I receive a 401 - Unauthorized error.
Additionally, I am unable to access the API key (client id and secret key) from the Admin panel — it seems to be missing or unavailable.

Regards,
Keyur

I’m experiencing the same problem. If anyone can help, that would be much appreciated.

@botautomation @swridings

You mean you are not able to see the registered app under admin->external applications anymore?

Can you please confirm if you are using UiPath community version as i can see another user also reporting of the same issue which started yesterday.

Hi @botautomation

@swridings was able to resolve this error by creating PAT. You can also consider trying the same.

If not, please consider doing external application setup and using client id and secret from same to generate access token for further api calls.

@botautomation

Please try the steps as below for fetching token, it should work for you as it has worked for 2 other users who reported the same issue.

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