| PUT | /POS/Operations/Book/tasks |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| OpDate | body | DateTime | No | |
| BranchID | body | int? | No | |
| Partial | body | bool? | No | |
| IgnoreBooked | body | bool? | No | |
| IgnoreOpenBatches | body | bool? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| 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.
PUT /POS/Operations/Book/tasks HTTP/1.1
Host: 10.10.0.107
Accept: application/json
Content-Type: application/json
Content-Length: length
{"OpDate":"\/Date(-62135596800000-0000)\/","BranchID":0,"Partial":false,"IgnoreBooked":false,"IgnoreOpenBatches":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}