Developer Console
Gracias por tu visita. Esta página solo está disponible en inglés.

SubscriptionInfo Endpoint

SubscriptionInfo allows device makers to access the subscription status for specific slots assigned to registered devices.

Path

/subscriptionInfo

HTTP Method

GET

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 headers are supported by the GetSubscriptionInfo Endpoint:

Header Parameters

Version 2.0

Authorization: Bearer (ACCESS_TOKEN)
x-amzn-accept-type: com.amazon.dash.replenishment.DrsSubscriptionInfoResult@2.0
x-amzn-type-version: com.amazon.dash.replenishment.DrsSubscriptionInfoInput@1.0

Version 1.0

Authorization: Bearer (ACCESS_TOKEN)
x-amzn-accept-type: com.amazon.dash.replenishment.DrsSubscriptionInfoResult@1.0
x-amzn-type-version: com.amazon.dash.replenishment.DrsSubscriptionInfoInput@1.0

Response Example

Version 2.0

HTTP/1.1 200 OK
x-amzn-type-version: com.amazon.dash.replenishment.DrsSubscriptionInfoResult@2.0
{
 "slotsSubscriptionStatus": {
   "slot1": {
     "productInfoList": [{
       "asin": "string",
       "quantity": 1,
       "unit": "count"
     }],
     "subscribed": true
   }
 }
}

Version 1.0

HTTP/1.1 200 OK
x-amzn-type-version: com.amazon.dash.replenishment.DrsSubscriptionInfoResult@1.0
{
   "slotsSubscriptionStatus": {
     "slot1": true,
     "slot2": false
   }
}

Error Responses

Error Responses 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