| GET | /api/v1/deviceconsumptions/{Guid} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BearerToken | query | string | Yes | |
| Guid | path | Guid | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| DeviceConsumption | form | DeviceConsumption | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Guid | form | Guid | No | |
| DeviceReading | form | double? | No | |
| DeviceReadingDate | form | DateTime? | No | |
| DeviceReadingKind | form | DeviceReadingKind | No | Allowable Values
|
| ChangeDate | form | DateTime? | No | |
| Note | form | string | No | |
| AmpouleColour | form | string | No | |
| DeviceGuid | form | string | No |
| ZA | |
| HA | |
| MO | |
| EB | |
| AB |
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.
GET /api/v1/deviceconsumptions/{Guid} HTTP/1.1
Host: calotec-portal-servdesk.eras-online.de
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"deviceConsumption":{"guid":"00000000000000000000000000000000","deviceReading":0,"deviceReadingDate":"0001-01-01T00:00:00.0000000Z","deviceReadingKind":"ZA","changeDate":"0001-01-01T00:00:00.0000000Z","note":"String","ampouleColour":"String","deviceGuid":"String"},"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}