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 (July - September 2025).

Five new guides available in the new guides experience

The following two new guides were added to the new Guides landing page at https://developer.ebay.com/develop/guides-v2:

  • Listing Creation Guide: This API use case guide covers creating individual single-SKU and multiple-SKU listings, creating listings in bulk, and generating listings based on existing eBay Catalog products.
  • Listing Management Guide: This API use case guide covers how to revise, relist, retrieve, and end eBay active listings.

The following three guides are not new, but have been reformatted into the new guides experience. If you have bookmarked the previous versions of these guides, we recommend that you update your bookmarks:

  • Using eBay REST Guide: This guide provides high-level information on getting started with and using eBay REST APIs.
  • Authorization Guide: This guide covers all you need to know about generating and using OAuth tokens when making API calls.
  • Digital Signatures Guide: This guide covers the full process involved in creating and adding digital signatures in the HTTP payloads for affected API calls. Digital signatures are only required for developers making API calls on behalf of EU/UK sellers.

Data handling change

eBay's API integrations will be modified to address data handling requirements for certain users. This change affects third-party developers operating in one of the following jurisdictions: China (and its territories), Russia, North Korea, Cuba, Iran, and Venezuela. Public eBay API fields that use/return public eBay usernames will be replaced with immutable user IDs, and financial data will be protected for certain users. More details on this change and the full list of affected public API fields can be found in our Data Handling Compliance document.

Creating compliant P&A listings in US

Starting in July, eBay implemented a “Free and Easy” returns policy where Parts & Accessories listings on the US marketplace, meeting certain criteria, must offer free returns to buyers with a return period of 30 or 60 days. See the Boost buyer trust with new P&A returns policy page on Seller Center for more information, the full list of criteria, and a full set of FAQs.

Add and Revise APIs are already returning warnings for non-compliant listings, and these warnings will be converted to blocking errors starting around October 7. Please work with your sellers to make sure their US Parts & Accessories listings are compliant with this policy. See the Support for easy returns in Parts and Accessories integration guide topic for specific information on creating compliant return policies through the Trading API or through the Fulfillment Policy object of the Account v1 API.

To help offset costs, eBay will be offering sellers eBay return shipping labels at a discount of 50 percent.

COO/Region of Manufacturer aspect changes

eBay sellers shipping to the US should provide information about where their items were manufactured on their listings to enable a transparent shipping experience that aligns with US tariff requirements. Below are two important things developers and sellers need to be aware of:

  • As of September 12th, the Country of Origin aspect within categories like fashion or jewelry has been changed to Materials Sourced From.
  • Coming in October, the Country/Region of Manufacture aspect (applicable to the majority of eBay categories) will be changed to Country of Origin, and that aspect name should be used instead of Country/Region of Manufacture for all listings on all eBay marketplaces that ship to the US.

It is recommended that developers use or continue to use the getItemAspectsForCategory method or the fetchItemAspects method and Taxonomy SDK to monitor the switchover from the Country/Region of Manufacturer to the Country of Origin aspect name for affected categories.

Short-duration call limits for all Media API POST calls

All POST methods in the Media API have a short-duration call limit of 50 requests per five seconds. An error will occur if this short-duration call limit is exceeded. This is not a new behavior, but this rate limit was just called out in documentation this quarter to help prevent triggering any errors related to this rate limit being exceeded. This note was added to all POST method reference docs and was also added to the API Call Limits page.

Catalog product edits allowed for category ID 173651

As part of the Emissions control defeat devices policy, products in the Tuning devices and software feature category (category ID 173651) must reference an eBay catalog product. Until now, sellers were not allowed any edits to any of the catalog product details, but they can now make revisions to the title and/or description if they desire. They can still not make any changes to a product's item specifics. See the Tuning devices and software integration guide topic for more API-specific information.

Fashion Pre-owned item conditions expanded

The three 'Pre-owned' item conditions were launched globally to an additional 159 leaf categories, including women's handbags, accessories, jewelry, and shoes.

As a reminder, here are the three Condition IDs (used in Trading API) and Condition Enums (used in Inventory API) to use for the 'Pre-owned' item conditions:

Condition Name Condition ID value Condition Enum value
Pre-owned - Excellent 2990 PRE_OWNED_EXCELLENT
Pre-owned - Good 3000 USED_EXCELLENT
Pre-owned - Fair 3010 PRE_OWNED_FAIR

The item condition metadata in the getItemConditionPolicies method of the Metadata API has been updated for the newly supported leaf categories.

Refurbished Program rolls out to more categories

The eBay Refurbished Program has continued to grow in Q3, with over 500 leaf categories added to the program in 2025, bringing the total number of leaf categories to over 2200. In the eBay Refurbished Program, there are four different refurbished item conditions, including Certified Refurbished (ID 2000), Excellent - Refurbished (ID 2010), Very Good - Refurbished (ID 2020), and Good - Refurbished (ID 2030). Sellers must go through an application and vetting process before using any one of the four refurbished item conditions.

The eBay Refurbished Program applies to leaf categories across the following verticals: Home & Garden, Business & Industrial, Electronics, Fashion, Motors, Jewelry & Watches, Lifestyles, and Collectibles. For all leaf categories that support the eBay Refurbished Program, the item condition of Seller Refurbished (ID 2500) can no longer be used, and sellers must change the condition to Used (ID 3000) or use one of the newer refurbished conditions if they apply and qualify for using that item condition.

More information on the eBay Refurbished Program can be found on the eBay Refurbished Program Seller Center page, including links to the applications and a link to a downloadable spreadsheet that has the 500+ leaf categories that have become part of the program just in 2025. The getItemConditionPolicies method of the Metadata API can be used to retrieve all leaf categories that are supported by the eBay Refurbished Program.

New automated feedback feature for sellers

The feedback score and positive feedback percentage are very important metrics for sellers. Most transactions go smoothly, with sellers providing great service, but not every buyer will acknowledge great service by providing feedback. As of September 3, 2025, sellers will automatically receive feedback for successful sales transactions that meet these criteria:

  • You shipped the order with tracking and it arrived within the expected delivery range
  • The buyer hasn't reported any issues
  • The buyer hasn't left feedback

Typically, a seller will receive automated positive feedback from eBay seven days after the sales transaction if the buyer has yet to leave feedback. If the buyer does leave positive feedback after the automated feedback is already there, the buyer's feedback comment will replace eBay's feedback comment. For each sales transaction, the buyer will not know that eBay has left automated feedback for the seller, so they will not be disincentivized to leave feedback.

API updates

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

Support for Multiwarehouse functionality in order APIs

For sellers who have multiple warehouses and have implemented eBay's multi-warehouse functionality, the order management methods of the Fulfillment API and the Trading API now return the warehouse location closest to the buyer's location.

Regardless of which listing API that you use, you will need to create a FULFILLMENT_CENTER location (with full address) using the createInventoryLocation method of the Inventory API, and then you will use the createOrReplaceSkuLocationMapping method to map multiple FULFILLMENT_CENTER locations to listings. Note that the createOrReplaceSkuLocationMapping method maps FULFILLMENT_CENTER locations at the SKU level, so the createOrReplaceSkuLocationMapping method will need to be used multiple times for multiple-SKU listings. Whether you use the Inventory API or the Trading API, see the Q4 2024 Newsletter for more information on the process of associating multiple warehouses to listings.

For listings that are set-up with multi-warehouse functionality, the address to the FULFILLMENT_CENTER location closest to the buyer will be returned in the itemLocation container in getOrder and getOrders methods of the Fulfillment API, and in the Item.Location field of GetOrders, GetSellerTransactions, and GetItemTransactions calls of the Trading API.

eBay Guaranteed Fit support in Fulfillment API

As part of the eBay Guaranteed Fit program for eBay US Motors P&A listings, the buyer"'s vehicle aspects will be returned in the compatibilityProperties array of getOrder and getOrders methods in the Fulfillment API. In order to take advantage of the eBay Guaranteed Fit program, buyers are expected to provide the year, make, model, and trim of their vehicle, and these aspects will be returned in the order details just so that the seller can verify that the vehicle is compatible with the part or accessory.

Motors/Caramel checkout details returned in order APIs

For motor vehicles that are purchased on eBay US Motors using eBay's Secure Purchase program, the details of this purchase are returned through the new MotorPurchase container of GetOrders and GetItemTransactions of the Trading API. With Secure Purchase, buyers can securely pay the full balance of the motor vehicle, easily obtain financing and/or insurance, and even have eBay take care of DMV-related tasks such as paying taxing and vehicle title. See the Secure Purchase topic for detailed information, including numerous FAQs.

Support for CAFR and BEFR in Feed and Metadata APIs 

The French language versions of the eBay Canada (https://www.cafr.ebay.ca/) and eBay Belgium (https://www.befr.ebay.be/) sites are now supported by all methods of the Sell Feed API and the Metadata API. Whether you are using the Sell Feed API to list/revise items on one of these eBay marketplaces or using the Metadata API to retrieve listing metadata from one of these eBay marketplaces, you must set the following HTTP headers as follows:

  • eBay Canada (French): Include the X-EBAY-C-MARKETPLACE-ID header and set its value to EBAY_CA, and include the Accept-Language header and set its value to fr-CA.
  • eBay Belgium (French): Include the X-EBAY-C-MARKETPLACE-ID header and set its value to EBAY_BE, and include the Accept-Language header and set its value to fr-BE.

New document type supported in Media API

The document resource of the Media API now supports ACCESSIBILITY_INFORMATION as a documentType value in the createDocument and createDocumentFromUrl methods. The ACCESSIBILITY_INFORMATION document type is described as a document providing "details on the accessibility features of a product, ensuring it can be used by individuals with disabilities or special needs".

Promoted Listing campaign report updates

The following updates were made to Promoted Listing reports in the Sell Marketing API this quarter:

  • For all campaign reportType values, when the dimensionKey value is set to seller_keyword_id, the following annotationKeys values become available:
    • keyword_bid
    • keyword_status
  • For all campaign reportType values, when the dimensionKey value is set to campaign_id, the following annotationKeys values become available:
    • campaign_status
    • daily_budget (CPC campaigns only)
    • daily_budget_status (CPC campaigns only)
  • For all campaign reportType values, when the dimensionKey value is set to listing_id, listing_status is a newly-supported annotationKeys value.
  • When the reportType value is set to CAMPAIGN_PERFORMANCE_REPORT, and the dimensionKey value is set to campaign_id, the following annotationKeys values become available:
    • listing_strategy
    • budget_strategy
  • When the reportType value is set to TRANSACTION_REPORT, the sales_type dimensionKey value is now available for both the CPC and CPS funding models.

New reference docs for Inventory Mapping API

The new reference doc experience is now fully live for the new GraphQL Inventory Mapping API. Please note that this API is still restricted to select partners at the moment. For the developers already using this API, please note that the new reference docs have replaced the Inventory Mapping Playbook, and that playbook has been archived.

Charity details added to Browse API Item methods

The charityTerms container can now be returned for the getItem, getItembyLegacyId, and getItemsByItemGroup methods. For this new container to be returned, the listing must be a charitable listing, and one of the fieldgroups values must be set to CHARITY_DETAILS. The charitable information in the new charityTerms container includes the charityOrgId, name, donationPercentage, website, and imageUrl for charity logo image.

Two new topics added to Notification API

The following two new topics were added to the Notification API:

  • BUYER_REQUESTED_PURCHASE_QUOTE: This topic can be subscribed to if a seller wishes to receive notifications when a buyer requests the total price for the order before paying for the order. A seller will typically send this buyer an invoice when the order total is requested.
  • LISTING_PREVIEW_CREATION_TASK_STATUS: This topic can be subscribed to if a seller is having listing previews generated for them through the Inventory Mapping API, and is sent whenever a listing previews task has completed.
    Note: This notification topic can only be used by developers who have access to the restricted Inventory Mapping API.

eBay Delivery International Shipping API enhanced

The eBay Delivery International Shipping API has been enhanced with a new bundle resource with four new methods. Sellers can use these methods to create a bundle for multiple packages in an order, retrieve a bundle, cancel a bundle, or retrieve a bundle label.The ConsignTypeEnum type was also updated with four new enumeration values.

Note: This API is restricted to select developers supporting Greater-China based eBay sellers with shipping and fulfillment.

SellerAccept enum value added as new Best Offer status

A new SellerAccept enum value was added to the BestOfferStatusCodeType of the Trading API. In the GetBestOffers response, this new enumeration value will be returned to indicate that the seller has accepted the buyer's offer but buyer payment has not occurred yet. The status will change to Accepted once the buyer completes payment.

eBay deprecation and decommission updates

The following APIs were decommissioned in Q3:

Additionally, support for the ASPECTS_ADOPTION compliance type in the Compliance API and support for the ExtensionInDays field in the UploadSiteHostedPictures call in the Trading API has ended.

The following APIs were marked as deprecated in Q3:

Due to extremely low or non-existent use, the following Platform Notification event types have been decommissioned and users will no longer be able to subscribe to these events: AccountSuspended, BuyerNoShow, AccountSummary,, EBNOrderCanceled, EBNOrderPickedUp, EmailAddressChanged, PasswordChanged, PasswordHintChanged, and PaymentDetailChanged.

We hope everyone had a great third quarter, and we are looking forward to working with the community for the rest of 2025!