Test

<back to all web services

StoreLogs

StoreLogs Parameters:
NameParameterData TypeRequiredDescription
LoggersqueryList<Logger>No
Logger Parameters:
NameParameterData TypeRequiredDescription
IdformlongNo
DevicesformList<Device>No
Device Parameters:
NameParameterData TypeRequiredDescription
IdformlongNo
TypeformstringNo
TimeStampformlongNo
ChannelsformList<Channel>No
Channel Parameters:
NameParameterData TypeRequiredDescription
NameformstringNo
ValueformstringNo
StoreLogsResponse Parameters:
NameParameterData TypeRequiredDescription
ExistingLogsformList<Logger>No
ResponseStatusformResponseStatusNo

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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/StoreLogs HTTP/1.1 
Host: test.servicestack.net 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"loggers":[{"id":0,"devices":[{"id":0,"type":"String","timeStamp":0,"channels":[{"name":"String","value":"String"}]}]}]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"existingLogs":[{"id":0,"devices":[{"id":0,"type":"String","timeStamp":0,"channels":[{"name":"String","value":"String"}]}]}],"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}