DeviceStatus Endpoint
Warning: You are viewing an old version of the DRS docs. To access the new APIs, see Dash Replenishment Overview.
Devices must call DRS on a daily cadence to report activity.
- Path
- HTTP Method
- Header Parameters
- Versioning
- Request Body Parameters
- Response Example
- Error Responses
Path
/deviceStatus
HTTP Method
POST
Header Parameters
x-amzn-accept-type: com.amazon.dash.replenishment.DrsDeviceStatusResult@1.0
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeviceStatusInput@1.0
Authorization: Bearer (ACCESS_TOKEN)
Versioning
Versioning is used to incrementally update API functionality without directly impacting customers. x-amzn-type-version and x-amzn-accept-type headers must be sent with each call. The following are supported by the DeviceStatus Endpoint:
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeviceStatusInput@1.0
x-amzn-accept-type: com.amazon.dash.replenishment.DrsDeviceStatusResult@1.0
Request Body Parameters
The following data must be passed in the request body:
| Parameter | Description | Type |
|---|---|---|
mostRecentlyActiveDate |
The date and time of the most recent device activity in ISO 8601 format. | String |
Sample Request Body
{
"mostRecentlyActiveDate" : "2015-12-21T10:00:00Z"
}
Response Example
HTTP/1.1 200 OK
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeviceStatusResult@1.0
Error Responses
| Errors | Descriptions |
|---|---|
| HTTP/1.1 500 Internal Server Error | Indicates that an error occurred internally to the server. |
| HTTP/1.1 400 Bad Request | Client error: an error occurred due to data passed in by the client (e.g. bad token). Amazon will make a best effort to provide feedback on the nature of the failure in the response body. |
Last updated: Aug 07, 2018