You are here: Sell APIs > Fulfillment API > Release Notes

Fulfillment API release notes

Just getting started with the Fulfillment API? See the following documents for details on using this API:

The API release history

The following table lists the releases for the Fulfillment API:


Release Date

Summary of Release

Version 1.1.0


Minor update

Version 1.0.0

2016-10-19 Initial release of Version 1.0.0

Version 1.1.0

The following sections detail the updates that have been made for this release.

API updates

This API release contains the following updates and changes:

Changed Call

Schema changes

Additional enforcement for order search date range

Two of the available criteria for the Get Orders call's filter parameter are date ranges: creationdate and lastmodifieddate. The call can return several error codes for dates that don't comply with the permitted date ranges for these criteria. A new error code has been added:










Start and end dates can't be in the future

Documentation changes and errata

Orders requiring upfront payment must be paid to be fulfilled

This documentation previously stated that the Fulfillment API covers transactions that have completed the checkout process. The documentation has been updated to clarify that this includes all paid purchases and purchases that do not require upfront payment (e.g., COD), but does not include pending payment purchases that require upfront payment before shipment.

Version 1.0.0

This is the initial release of the Fulfillment API, Version 1.0.0. For a list of the new calls, see the Fulfillment API Reference.

The following sections detail the updates that have been made for this release.

Documentation changes and errata

Creating a shipping fulfillment can occasionally fail

The Create a Shipping Fulfillment call can occasionally return an HTTP 500 error due to an internal server issue. However, in some cases this call may succeed if you issue it once more after receiving this error.

Get Orders call does not return cancellation requests

Currently, for the Get Orders call, the cancelStatus.cancelRequests array is returned but is always empty. To retrieve any active cancellation requests for an order, you must use the Get an Order call.