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 .jsv suffix or ?format=jsv
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: text/jsv
Content-Type: text/jsv
Content-Length: length
{
itemsList:
[
{
itemType: task,
itemId: String
}
]
}
HTTP/1.1 200 OK Content-Type: text/jsv 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 } } }