| POST | /QueuePush |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ItemsList | body | List<QueuePushItem> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ItemType | form | QueueDataTypes | No | |
| ItemId | form | string | No |
| task | |
| file | |
| completion | |
| movement |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| IsOk | form | bool | No | |
| ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /QueuePush HTTP/1.1
Host: s10.tdfkm.ru
Accept: application/json
Content-Type: application/json
Content-Length: length
{"itemsList":[{"itemType":"task","itemId":"String"}]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"isOk":false,"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}