Changelog for the Buy with Prime API v2024-04-01
May 13, 2024
This changelog lists the updates associated with Buy with Prime API v2024-04-01.
Backwards-incompatible changes
v2024-04-01 of the Buy with Prime API has the following backwards-incompatible updates from the v2024-01-01 version. These updates require code changes on your end if you decide to migrate to this version.
Catalog interface
The "mapping product" concept was replaced by the "product" concept. This resulted in the following changes:
- The
mappingProduct
query was renamed toproduct
. There is now also aproducts
query to retrieve multiple products from the Buy with Prime catalog in one API call. - The
MappingProduct
object was renamed toProduct
, and the following fields were renamed:productExternalId
was renamed toexternalId
.productSku
was renamed tosku
.productMsku
was renamed toamazonSku
.isPrimeIntended
was renamed toofferPrime
.url
was renamed toproductDetailPageUrl
.
- The
MskuProductIdentifier
object was renamed toAmazonSkuProductIdentifier
. - The
Issue
object was removed. Use theSignal
object instead. - The
buyableQuantity
field of theInventoryItem
object was renamed tofulfillableQuantity
. - For the
createUploadLink
mutation:- The
fileExtension
field in the input was renamed tofileType
. - The
createUploadLink
mutation now returns aCreateUploadLinkResponse
object that contains the upload link as a field, instead of returning the upload link itself.
- The
Delivery Preview interface
- In the input to the
deliveryPreview
query, theitems
field was renamed toproducts
, which resulted in the following additional changes:- The
DeliveryItemInput
object was renamed toDeliveryProductInput
, and thequantity
field was renamed toamount
. - The
DeliveryItem
object was renamed toDeliveryProduct
. - The
itemMessaging
field of theDeliveryPolicy
object was renamed toproductMessaging
. - The exceptions are now
ProductAmountUnavailable
,ProductNotPrimeEnabled
, andProductOutOfStock
.
- The
- The
DeliveryOffer
object no longer has acharge
field.
Order interface
- The
createOrder
andupdateOrder
mutations now return the entire order. - In the
CreateOrderInput
object, theorderTotal
field was replaced by thetotalPrice
field. - In the
LineItem
object, thepurchasedItem
field was renamed toproduct
. - The
CanceledOrderLineItem
object was removed. - The
association
field of theDeliveryInformation
object was removed. To access order line items associated with the delivery information, use thedeliveryInformationDetailsFor
field of theDeliveryInformationDetails
object. - The following events were renamed:
ITEM_CANCELLED
was renamed toDELIVERY_CANCELLED
.ITEM_DELIVERED
was renamed toDELIVERY_COMPLETED
.ITEM_IN_TRANSIT
was renamed toDELIVERY_IN_TRANSIT
.
Return interface
- The
generateReversalOffers
query was renamed toreversalOffers
. - The
ReversalOfferGroup
object was renamed toReversalItemOffers
. - In the
ReversalOffers
object, thereversalOfferGroups
field was replaced byreversalOfferCollection
. - In the
ReturnFor
object, theorderLineItems
field now contains a list ofOrderLineItemAmount
objects instead ofReturnOrderLineItem
objects. - The returned
ReversalOffers
now provide locale information rather than just en-US strings without locale information.
Refund interface
- In the
RefundFor
object, theorderLineItems
field now contains a list ofOrderLineItemAmount
objects instead ofRefundedOrderLineItem
objects.
Privacy interface
- The
createPrivacyRequest
mutation was replaced bystartPersonalDataRetrievalTask
andstartPersonalDataDeletionTask
. - The
privacyRequest
query was replaced bypersonalDataRetrievalTask
andpersonalDataDeletionTask
. - The
cancelPrivacyRequest
mutation was renamed tocancelPersonalDataDeletionTask
.
Event interface
- Event interface mutations and queries were removed. To subscribe to events, work with your Buy with Prime solutions architect.
Backwards-compatible changes
v2024-04-01 of the Buy with Prime API has the following backwards-compatible updates from the v2024-01-01 version.
Catalog interface
- There are three new mutations:
- The
FeaturedImageInput
object now contains analttext
string field that you can use to specify the image alt text, which is not currently supported by the CSV. - In the catalog feed processing result CSV file, there are now "Error Type(s)" and "Error Code(s)" columns. Update your CSV-parsing logic to handle the two new fields and their machine-friendly values.
Return interface
- There is now a
resolutionTypes
tag to indicate return eligibility in the API response to explicitly indicate returnability with resolution type value'RETURN'
. You no longer need to rely on a string match with the reversal offer summary view.
Privacy interface
Updated 6 days ago