Orchestrator REST API - Start Job with Input Arguments - Bad Request

Help Orchestrator
, ,
1

Hey there

We are currently using the Orchestrator API to start jobs from an external application. This works reliably. However, we now want to extend it to include input arguments — and that’s where I’m running into issues.

Basically, I recreated the scenario in Studio using the Orchestrator HTTP Request activity. That works smoothly, once I finally figured out the correct syntax.

However, calling it from the external application doesn’t work. No matter how I populate the input arguments, I keep getting a 400 Bad Request error.

Our start info block looks like this (all Arguments are strings):

“startInfo”:
{
“ReleaseKey”: “xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx”,
“Strategy”:“Specific”,
“RobotIds”: [9],
“MachineSessionIds”: [40],
“NoOfRobots”: 0,
“JobsCount”:0,
“InputArguments”:“{“in_assetName”:“App_User”,“in_folderName”:“Management”}”,
“Source”:“Manual”
}

In addition to this syntax, I’ve tried the following variations. All of them result in a Bad Request:

“InputArguments”:“{“in_assetName”:“App_User”,“in_folderName”:“Management”}”,
“InputArguments”:“{in_assetName:“App_User”,in_folderName:“Management”}”,
“InputArguments”:“{in_assetName:App_User,in_folderName:Management}”,

2

@JenJen,

Not sure what external application you are trying to trigger the bot but if you are using Power automate, there is a connector for triggering the jobs UiPath Orchestrator which supports arguments as well.

3 
"InputArguments": ->"<-{"in_assetName":"App_User","in_folderName":"Management"}->"<-,

can you try

"InputArguments": "{\"in_assetName\":\"App_User\",\"in_folderName\":\"Management\"}",

also feel free to do the RnD in swagger before

1 Like
4

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