CommandReflectionDigital Documentation
CommandReflectionDigital
Draft documentation version
Documentation is partial and not validated !
Description
Version | V1 |
---|---|
Require User context | |
Authorization | |
Errors |
Request
Route
Parameters
Parameter | Required | Sample | Description |
---|---|---|---|
Command | Digital command as ReflectionCommandDigital | ||
ReflectionID | 6 | ID of ReflectionBase to command | |
WAC | WAC123456789012 | Code of BusinessAccount | |
ExecutionDate | 2014-09-15T13:59:20.0000000Z | Execution planned date. If empty, command is executed on next LTU call | |
Tracking | Main | Ack and execution command tracking level as TrackingEnum |
Remarks
- To override Content-type in your clients HTTP Accept Header, append the
.json
suffix or?format=json
- To embed the response in a jsonp callback, append
?callback=myCallback
Post Data sample
POST /json/reply/CommandReflectionDigital HTTP/1.1
Host: localhost
Content-Type: application/json
Content-Length: length
{"wType":"CommandReflectionDigital","command":{"wType":"ReflectionCommandDigital","value":false},"reflectionID":0,"executionDate":"0001-01-01T00:00:00.0000000Z","tracking":"None","wac":"String"}
cURL command sample
curl -k -H "Authorization: Bearer [YOUR_ACCESS_TOKEN]" -H "Content-Type:application/json" -X POST -d @filename.json https://api.wit-datacenter.com/WAC123456789012/Reflection/6/CommandDigital
Remark
@filename.json
contain your request parameters serialized in JSON as described in Post Data sample bottom
Response
Returned Entity
Command as ReflectionDataAnalogicJSON Sample
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"wType":"ReflectionDataDigital","value":false,"valueDate":"0001-01-01T00:00:00.0000000Z","creationDate":"0001-01-01T00:00:00.0000000Z","sendDate":"0001-01-01T00:00:00.0000000Z","executionDate":"0001-01-01T00:00:00.0000000Z","phase":"Received","state":0,"id":0,"picture":"00000000000000000000000000000000","name":"String"}