Skip to main content

Program news

We hope everyone is well. We want to take this time to share with you some eBay Developers Program updates from the recent quarter (October - December 2025).

Five new Buy API use case guides published

Five new Buy API use case guides added to the new Guides page. These new Buy API guides include the following.

In case you are unfamiliar with the new Guides page, it is organized in a way that better aligns with business use cases of yours by leveraging eBay APIs. There is a Sell tab and a Buy tab that you can toggle between, and each dives deep into building selling or buying applications. Note that there are several common guides relevant to both contexts, so you’ll see those guides under both tabs.

Country of Origin aspect update

Country of Origin is now critical for tariff calculation and managing listing visibility for US-based buyers. As of November 1, all listings with items shipping to the US from outside the US are expected to have the Country of Origin aspect. For new and active listings that don’t have this aspect, eBay will add this aspect to US import eligible listings where reliable country of origin information is available.

The Country of Origin provided by the seller will be prioritized and will overwrite what eBay provided as a Country of Origin.

Keep in mind the following:

  • Aspect names are localized for each eBay marketplace, so make sure to use the getItemAspectsForCategory or fetchItemAspects methods to get the equivalent Country of Origin aspect for the listing marketplace.
  • The Country of Origin aspect replaced the Country/Region of Manufacture aspect back in October.
  • The name of the original Country of Origin aspect, used for categories like fashion and jewelry, has been changed to Materials Sourced From. This aspect is optional, but should be included if applicable.

New EPREL aspect for EEK labels

A new EPREL Registration Number aspect is now available for products that feature Energy Efficiency (EEK) labels. If a valid EPREL (European Product Registry for Energy Labelling) registration number is provided, EEK information such as the Energy Efficiency Label and product data sheet will be automatically picked up and displayed on the listing.

EU Regulatory requirements expect sellers to provide Energy Efficiency labels for product groups such as appliances, smart phones, tablets, and tyres if those sellers are operating within and/or shipping to EU countries and Northern Ireland. The getRegulatoryPolicies method of the Metadata API can be used to see which eBay leaf categories support Energy Efficiency labels. Leaf categories in that API response that support Energy Efficiency labels will show a value of ENERGY_EFFICIENCY in the supportedAttributes.name field. Developers can also use the getItemAspectsForCategory method or the fetchItemAspects method and Taxonomy SDK to see which leaf categories support EEK labels.

The EPREL Registration Number for a product can be found by scanning the QR code on the product’s Energy Efficiency label, or a search can be performed on the EPREL database directly using the product’s GTIN value.

Note that using the EPREL Registration Number aspect is an alternative to using the EnergyEfficiencyLabel container of the Trading API or the energyEfficiencyLabel container of the Inventory API. If both are provided, either of those containers take precedence over the EPREL Registration Number aspect.

eBay for Charity expanded to CA and DE

The eBay for Charity program has expanded to the Germany and Canada (English and French versions) marketplaces. See the following pages for detailed information on eBay for Charity:

With expansion of this program, the Charity container of the Trading API and the charity container of the Inventory API can now be used on the Germany and Canada marketplaces to enable charitable listings.

eBay Plus changes

In order to make a listing on the Germany or Australia marketplaces eBay Plus eligible, the seller no longer needs to include the eBayPlus field of the Trading API or the eBayPlusIfEligible field of the Inventory API. If this field is included, it is ignored and dropped. eBay determines which listings qualify for eBay Plus based on whether the buyer has an active eBay Plus subscription and whether the listing meets the program's requirements. See the eBay AU help topic or eBay Germany eBay Plus page for listing requirements.

Sellers on those two eBay marketplaces also no longer have an eBay Plus preference to manage in their eBay account.

API License Agreement updated

A new clause was added concerning Covered Persons and Transfers of Personal Data. See Section 3.g.4 in the Data Processing Addendum section of the API License Agreement.

API updates

The following updates have been made to our APIs this quarter.

AI-enabled Inventory Mapping API released

The GraphQL Inventory Mapping API is now available to all developers. This API helps sellers create high-quality eBay listings with AI-powered recommendations generated from their existing product data. This API allows sellers and third-party partners to use existing product data to create eBay listing previews, which are then used to create listings through eBay's listing APIs.

See the Create listing previews section of the Listing creation guide for details on using the Inventory Mapping API to create eBay listing previews. You can also test out the API through the new GraphQL Explorer tool.

Be sure to read the recent Explore the Inventory Mapping API blog post.

New Feedback API

A new Feedback API was released this quarter. This new REST API is a more robust and modern alternative to the GetFeedback, GetItemsAwaitingFeedback, LeaveFeedback, and RespondToFeedback calls of the Trading API.

See the Using the Feedback API section of the Sell Communications Guide for more information on this new API.

New Message API

A new Message API was released this quarter. This new REST API is a more robust and modern alternative to the AddMemberMessageAAQToPartner, AddMemberMessageRTQ, AddMemberMessagesAAQToBidder, DeleteMyMessages, GetMemberMessages, GetMyMessages, and ReviseMyMessages calls of the Trading API.

See the Managing communications using the Message API section of the Sell Communications Guide for more information on this new API.

New shipping metadata methods

Five new shipping metadata methods were added to the Metadata API. All of these methods can be used as alternatives to the GeteBayDetails call of the Trading API.

Nine new topics added to Notification API

The following nine new topics can now be subscribed to through the Notification API:

  • ORDER_CONFIRMATION: A subscription for this topic initiates a notification being sent to a seller when a buyer completes the checkout process for an auction or fixed-price item.
  • OFFER_ACTIVITY: A subscription for this topic initiates offer-related notifications being sent to a buyer or seller when listing offer activity occurs. The four notifications that may be sent are as follows:
    • BUYER_OFFER (sent to sellers only)
    • BUYER_COUNTER_OFFER (sent to sellers only)
    • SELLER_OFFER (sent to buyers only)
    • SELLER_COUNTER_OFFER (sent to buyers only)
  • AUCTION_ACTIVITY: A subscription for this topic initiates auction activity related notifications being sent to bidders and sellers. The four notifications that may be sent are as follows:
    • BID_PLACED (sent to buyers only)
    • BID_RECEIVED (sent to sellers only)
    • OUTBID (sent to buyers only)
    • AUCTION_WON (sent to buyers only)
  • ITEM_MARKED_SHIPPED: A subscription for this topic initiates notifications being sent to a seller who marks an item as shipped.
  • FEEDBACK_RECEIVED: A subscription for this topic initiates notifications being sent to a user when they have received feedback from an order partner.
  • FEEDBACK_LEFT: A subscription for this topic initiates notifications being sent to a user when they have left feedback for an order partner.
  • FEEDBACK_STAR_CHANGED: A subscription for this topic initiates notifications being sent to a user when their feedback star rating has changed.
  • BUYER_QUESTION: A subscription for this topic initiates notifications being sent to a seller when a buyer asks a question about an active listing.
  • NEW_MESSAGE: A subscription for this topic initiates notifications being sent to a user when they receive a new message from eBay or another eBay user.

New compatibility support for Catalog API

A new compatibilityCount field was added to the response of the getProduct method of the Catalog API. This field is conditionally returned for a Parts & Accessories product to indicate how many motor vehicles the product is compatible with.

New methods available in Buy Marketing API

The following two methods were added to the Buy Marketing API:

  • getMostWatchedItems: This method retrieves the listings with the highest watch counts for a specific leaf category. The user can control the number of listings retrieved up to a maximum of 50. This method is an alternative to the getMostWatchedItems call of the Merchandising API.
  • getSimilarItems: This method retrieves items that are similar to the item in the request. The user can control the number of listings retrieved up to a maximum of 50. There are also options to filter by item end date or buying format, and a user can also exclude one or category IDs. This method is an alternative to the getSimilarItems call of the Merchandising API.

The Buy Marketing API is a restricted API that requires a specific scope.

New bulk sales tax method added

The bulkCreateOrReplaceSalesTax method was added to the Account API v1. This method allows a seller to add or modify multiple sales tax rate settings for multiple US territories and/or Canadian provinces. This new method complements the existing createOrReplaceSalesTax method and brings the sales_tax methods of the Account API v1 up to parity with the SetTaxTable call of the Trading API, which can also be used to add or modify multiple sales tax rate settings for multiple US territories and/or Canadian provinces.

New warning added to Browse search method

A new warning (ID 12519) added to the search method of the Browse API to account for a behavior when both itemLocationRegion and deliveryCountry are used as filter values in the same request. If incompatible itemLocationRegion and deliveryCountry values are provided, this warning will be triggered and the marketplace’s default location behavior will be used.

2-day seller offers no longer supported in US, UK

The duration of seller-initiated offers on the US and UK marketplaces can no longer be set to 2 days, but only to 4 days. Developers using the sendOfferToInterestedBuyers of the Negotiation API should be aware of how this change affects the behavior of the offerDuration container of that method. It is preferable that the offerDuration container is omitted in the request, as eBay will automatically default to the only supported duration for the US and UK marketplaces, which is 4 days. If the offerDuration container is used, the offerDuration.value value must be set to ‘4’ for the US and UK marketplaces and set to ‘2’ for all other eBay marketplaces that support this feature.

New Leads API available

A new Leads API was released this quarter. This new REST API is a modern alternative to the GetAdFormatLeads call of the Trading API. The getAllClassifiedLeads method searches through all of the seller’s active classified ad listings and retrieves sales leads by date range and/or by status. The getClassifiedLeadsByItemId method works similarly, but the search only considers one specified classified ad listing.

eBay deprecation and decommission updates

This section is just a summary of the deprecation and decommission activity. Be sure to visit https://developer.ebay.com/develop/get-started/api-deprecation-status page for full details.

Decommissioned APIs

No APIs were decommissioned in Q4.

Deprecated APIs

The following APIs were marked as deprecated in Q4:

Scheduled for decommission in Q1 2026

The following table summarizes the operations that will be decommissioned. See the https://developer.ebay.com/develop/get-started/api-deprecation-status page for the full list of Post-Order API methods being decommissioned.


Operations Operations
16 Post-Order API Return methods January 20, 2026
3 Return and 1 Inquiry Post-Order API methods February 2, 2026
GetVeROReportStatus, GetVeROReasonCodeDetails, and VeROReportItems February 2, 2026
3 Case Management, 1 Return, and 1 Cancellation Post-Order API methods March 2, 2026
4 Inquiry Post-Order API methods March 16, 2026
GetCategories March 31, 2026

We hope everyone had a great fourth quarter and start to the holiday season! We are looking forward to working with the community in 2026!