| PUT | /TspShiftCalcView |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| shiftid | body | int | No | |
| fuelid | body | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | ShiftCalcViewF | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| shiftcalcview | form | List<ShiftCalcView> | No | |
| turn_id | form | int? | No | |
| st_rem | form | decimal | No | |
| counters_scount | form | decimal | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| turntype_id | form | int | No | |
| turntype | form | string | No | |
| inout | form | int | No | |
| shiftfuelturnD_id | form | int? | No | |
| icount | form | decimal | No | |
| scount | form | decimal | No | |
| rng | form | int | No | |
| editable | form | bool | No | |
| prop | form | string | No | |
| vg | form | decimal | 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 /TspShiftCalcView HTTP/1.1
Host: axfuel.apex.ge
Accept: application/json
Content-Type: application/json
Content-Length: length
{"shiftid":0,"fuelid":0}
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"}},"Result":{"shiftcalcview":[{"turntype_id":0,"turntype":"String","inout":0,"shiftfuelturnD_id":0,"icount":0,"scount":0,"rng":0,"editable":false,"prop":"String","vg":0}],"turn_id":0,"st_rem":0,"counters_scount":0}}