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?
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.
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.
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>
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.
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.