The table below lists the API capabilities that are deprecated and scheduled for decommission.
| API | Method(s)/Field(s) | Deprecation Date | Decommission Date | Notes |
|---|---|---|---|---|
| Compliance API | 2023/09/07 | 2024/01/30 |
The suppressViolation method has been deprecated and is no longer supported on any eBay marketplace.
This method will be decommissioned on January 30th, 2024. |
|
| Trading API |
The following fields in GetMyeBaySelling:
|
2023/08/23 |
2024/02/06 |
These fields have been deprecated for the GetMyeBaySelling call and are scheduled for decommissioning. |
| Trading API |
The TicketListingDetails and the QuantityInfo containers, and their associated fields in the following calls:
* TicketListingDetails only
|
2023/08/23 | 2024/02/26 | These containers and their associated fields have been deprecated for the Add/Revise/Relist/Verify and GetItem family of calls. They are not usable and ignored if sent, and are scheduled for decommissioning. |
| Trading API |
UpdateReturnPolicy and UpdateSellerInfo fields in the ReviseItem call. OriginatingPostalCode field in the following calls: |
2023/08/23 | 2024/02/26 |
These fields have been deprecated for the listed calls. They are not usable and ignored if sent, and are scheduled for decommissioning.
For the OriginatingPostalCode field, specify the postal code of the item's location in the request field. For example, in the AddItem call specify the item's location using the Item.PostalCode field.
|
| Trading API |
2023/05/12 |
2024/04/02 |
The GetSellerDashboard call of the Trading API will be decommisioned on April 2, 2024. The alternative for this API is Seller Standards Profile methods of the Seller Analytics API. |
|
| Trading API |
The following calls have multiple fields being deprecated: |
2023/05/03 |
2024/01/31 |
Numerous fields in the response payloads of the GetOrders, GetItemTransactions, GetSellerTransactions, and GetMyeBaySelling calls are being deprecated. See the Deprecated Trading Order Management Fields document for the complete list of deprecated fields and reasons for deprecation. |
| Return Management API |
2023/02/03 |
TBD |
All methods of the Return Management API are scheduled to be decommisioned. The official decommission date will be announced once determined. This API is now out of synch with return management flows on eBay. Current users of the Return Management API and all users interested is programmatically managing return requests should make plans to migrate to the Post-Order API. |
|
| Trading API |
2023/01/31 |
2024/01/31 |
The GetOrderTransactions call will be decommissioned on January 31, 2024. No further updates are planned for this API during the deprecation period. Developers have the option of migrating to the GetOrders call in the Trading API, or the getOrders method of the Fulfillment API. Please note that the Fulfillment API only returns paid orders, so if your use case calls for retrieving both paid and unpaid orders, we recommend migrating to the GetOrders call in the Trading API. |
|
| Business Policies Management API | All | 2021/03/23 | TBD | The Business Policies Management API is deprecated and is scheduled for decommission in 2022. We recommend that you migrate to the fulfillment_policy, payment_policy, and return_policy resources of the Account API to set up and manage all of your fulfillment, payment, and return business policies. |
| Finding API | findCompletedItems | 2020/10/15/ | TBD | The findCompletedItems call is deprecated as of October 15, 2020, and access is restricted. An alternative to the findCompletedItems call is the Marketplace Insights API, but please note that this API is restricted and requires eBay Business approval for access. Please contact the Developer Technical Support team if you are interested in getting access to the Marketplace Insights API. |