v1.0.0
https://rubygems.org/gems/amz_sp_api/versions/1.0.0
Removed
- Nothing
Changed
-
See https://developer-docs.amazon.com/sp-api/page/release-notes for official changelog
-
BREAKING CHANGES:
- feeds-api-model 2020-09-04 -> 2021-06-30
- reports-api-model 2020-09-04 -> 2021-06-30
- both of these discard the previous encryption, so no need to encrypt_feed and use AmzSpApi.inflate_document instead of decrypt
- they also replace do away with "payload" method on the responses so instead access their data directly, e.g. get_reports.reports instead of get_reports.payload
- reports processingStatus is no longer available you're supposed to use the notifications api to subscribe to an sqs queue for it instead https://developer-docs.amazon.com/sp-api/docs/reports-api-v2021-06-30-use-case-guide#tutorial-request-and-retrieve-a-report
- I think my reports stopped coming back as utf-8 and started being Cp1252 from this api version change since it's the first time I had to pay attention to the Content-Type header as per the updated README
-
MOST LIKELY BREAKING CHANGES:
- Everything was re-generated with a different swagger version (but confusingly still 3.0.24 although it yielded different results) so a lot of result data structures changed but I'm not sure if any of them are used
- catalog-items-api-model v0 -> 2020-12-01 -> 2022-04-01 #22
-
Bugfixes
- Zlib::DataError (incorrect header check) fix for reports #11
Added
- Many new endpoints from #30 including
- listings-items
- listings-restrictions
- product-type-definitions
- shipment-invoicing
- tokens
- vendor-direct-fulfillment-inventory
- vendor-direct-fulfillment-orders
- vendor-direct-fulfillment-payments
- vendor-direct-fulfillment-shipping
- vendor-direct-fulfillment-transactions
- vendor-invoices
- vendor-orders
- vendor-shipments
- vendor-transaction-status