Orchestrator API - Adding Queue Items is not working

Hello Folks,

I am trying to invoke the Orchestrator API to send a simple queue message to them.

And when I perform it, I am getting the HTTP Status Code (200) and apparently it is okay. But that event message is not arriving.

I am using Postman to Authenticate (https://orchestrator/api/account/authenticate) and AddQueueItem (https://orchestrator/odata/Queues/UIPathODataSvc.AddQueueItem), below is my payload sample:

Authorization:Bearer [result of authentication]
X-UIPATH-TenantName: Default
X-UIPATH-OrganizationUnitId: Default
“itemData”: {
“Name”: “TestQueue”,
“Priority”: “High”,
“SpecificContent”: {
“First”: “Some String Value Here”,
“First@odata.type”: “#String”,
“Second”: 516,
“Fourth”: “Did I skip the Third value?”,
“AnotherKey”: true

The result in post man body’s tab is:

<base href="/" />

<title>UiPath Orchestrator </title>
<link rel="shortcut icon" href="favicon.ico" />

<link rel='stylesheet' type='text/css' href='/dist/assets/preloader.css?v=2019.4.4.0' />
<link rel='stylesheet' type='text/css' href='/dist/css/noto/noto-font-jp-zh-woff.css?v=2019.4.4.0' />
<link rel='stylesheet' type='text/css' href='/dist/css/noto/noto-font-jp-zh.css?v=2019.4.4.0' />
<link rel='stylesheet' type='text/css' href='/dist/css/material-design-icons/material-icons.css?v=2019.4.4.0' />
<link rel='stylesheet' type='text/css' href='/dist/styles.css?v=2019.4.4.0' />
<link rel='stylesheet' type='text/css' href='/dist/default.theme.css?v=2019.4.4.0' />
<script src='/dist/js/mixpanel-init.js?v=2019.4.4.0' type='text/javascript'></script>
<script src='/dist/assets/js/preload.js?v=2019.4.4.0' type='text/javascript'></script>
<script src='/dist/runtime.js?v=2019.4.4.0' type='text/javascript'></script>
<script src='/dist/scripts.js?v=2019.4.4.0' type='text/javascript'></script>
<script src='/dist/main.js?v=2019.4.4.0' type='text/javascript'></script>

My UiPath version is 2019.4.4

Thanks in advance,



Not sure what would be happening here. Although the images are a little small in resolution to make out the content (verification), it would appear everything is correct.

Your pasted text is using curved quotes instead of straight quotes so JSON parsers probably won’t like that, but I chalk that up to what you used to copy/paste the text.

  "itemData": {
    "Name": "TestQueue",
	"Priority": "High",
	"SpecificContent": {
	  "First": "Some String Value Here",
	  "First@odata.type": "#String",
	  "Second": 516,
	  "Fourth": "Did I skip the Third value?",
	  "AnotherKey": true


Tested with both 2018.3.1 and 2019.10.18 and a JSON response is returned. If I set the Content-Type to any other than application/json, it will throw “An error has occured.” but still a JSON response.

I did a quick search in the forums and there have been similar reports, but none of which had a solution or defined the underlining cause. Most seemed to switch the application they using i.e. Postman to SoapUI or vice versa.

I would presume that a setting in your Postman, proxy, orchestrator/IIS, or similar might be interfering?

1 Like

Hello, thank you so much for you assistance I have tried in SOAPUI and it was working properly.

In the Postman, I was able to get the items added into the queue after adding all the default settings of it.


Now it is working fine.


1 Like

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