GET | /Categories/{BrandName}/{DeviceName} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
BrandName | path | string | No | |
DeviceName | path | Device | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No | |
Id | form | int | No | |
Name | form | string | No | |
NameStripped | form | string | No | |
RangeName | form | string | No | |
RangeNameStripped | form | string | 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.
POST /json/reply/Categories HTTP/1.1
Host: digital-prod-umbracosharedapi-appservice.azurewebsites.net
Content-Type: application/json
Content-Length: length
{"brandName":"String","deviceName":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"}},"id":0,"name":"String","nameStripped":"String","rangeName":"String","rangeNameStripped":"String"}