Releases: jlevers/selling-partner-api
Releases · jlevers/selling-partner-api
v4.1.6
##Fixed
getInventorySummaries
resulted in a400 InvalidInput
when passingtrue
for$details
. This is a bug in Amazon's OpenAPI models, but we can fix it on our end by changing$details
from aboolean
to astring
. This implements that fix. (Followup to #75, thanks @allen1706)
Full Changelog: v4.1.5...v4.1.6
v4.1.5
v4.1.4
Fixed
- We were making the assumption that all feed result documents are tab-separated-values files. That isn't true, so in order parse those result documents correctly, the
ReportType::__FEED_RESULT_DOCUMENT
report type has been deprecated in favor of passing aFeedType
constant to theDocument
constructor. ThatFeedType
constant should correspond to the type of the feed whose result document is being downloaded.
Full Changelog: v4.1.3...v4.1.4
v4.1.3
Changed
- Added
CAD
to the Fulfillment Inbound API'sCurrencyCode
enum
Full Changelog: v4.1.2...v4.1.3
v4.1.2
Added
- Optional
GuzzleHttp\Client
object as a 3rd parameter toDocument
, to allow custom client functionality when uploading feed documents (#117)
Changed
- Removed
.travis.yml
and.openapi-generator-ignore
build artifacts from version control
Fixed
Full Changelog: v4.1.1...v4.1.2
v4.1.1
v4.1.0
Added
- The Listing Restrictions API
- New business analytics report types
Changed
- Updated the Listing Items API to support the newly added
get
operation
Fixed
- Re-encode document data with
mb_convert_encoding
instead ofutf8_encode
to avoid errors when document data is already UTF-8 (#85)
v4.0.3
Changed
OldCatalogApi
is now renamed toCatalogItemsV0Api
, to make it Amazon's naming scheme more closely.OldCatalogApi
is deprecated. (#106)- The
CA_MBF
andNO_VOEC
deemed reseller categories are now supported by the Orders API (#111, thanks @abbadon1334)
Fixed
v4.0.2
Changed
- Switch from
\Guzzle\Utils::jsonEncode(...)
to\Guzzle\json_encode(...)
for Guzzle 6 compatibility (#103)
Added
Endpoint::getByMarketplaceId()
, to retrieve endpoint information by Amazon marketplace ID (#102)
Thanks for the contributions @krystalcode!