Deregistration Endpoint
Warning: You are viewing an old version of the DRS docs. To access the new APIs, see Dash Replenishment Overview.
Deregistration is used to disassociate a device from a customer’s Amazon account. This call will invalidate any LWA access tokens, refresh tokens, and authorization codes associated with the device.
Path
Version 2.0
/registration
Version 1.0
/deviceModels/{DEVICE_MODELID}/devices/{DEVICE_IDENTIFIER}/registration
HTTP Method
DELETE
Header Parameters
Version 2.0
Authorization: Bearer (ACCESS_TOKEN)
x-amzn-accept-type: com.amazon.dash.replenishment.DrsDeregisterResult@1.0
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeregisterInput@2.0
Version 1.0
Authorization: Bearer (ACCESS_TOKEN)
x-amzn-accept-type: com.amazon.dash.replenishment.DrsDeregisterResult@1.0
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeregisterInput@1.0
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 Deregister Endpoint:
Version 2.0
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeregisterInput@2.0
x-amzn-accept-type: com.amazon.dash.replenishment.DrsDeregisterResult@1.0
Version 1.0
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeregisterInput@1.0
x-amzn-accept-type: com.amazon.dash.replenishment.DrsDeregisterResult@1.0
Response Example
HTTP/1.1 200 OK
x-amzn-type-version: com.amazon.dash.replenishment.DrsDeregisterResult@1.0
Error Responses
| Error | Description |
|---|---|
| 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