Trading API
The latest version of the Trading API has rolled out to all the API machines and is now available! Be sure to check out all the new features and known issues.
If you are getting started with the API, the following locations have information about joining the eBay Developers Program, creating test users, and other steps to getting your application certified to go live against the eBay production servers:
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
These release notes go back four quarters. For older release notes, see the Release Notes archive.
The lowest supported version is 941.
To learn how versioning works in the Trading API, see eBay's Schema Versioning Strategy.
Documentation Changes and Errata - 1031
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
See the 2017 Fall Seller Update for information about upcoming selling changes, including the eBay Guaranteed Delivery feature, integration of Markdown Manager into Seller Hub, new Q&A feature on product pages, information on eBay policy updates, and updates to Returns.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1031.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
With Trading WSDL Version 1031, the InsuranceDetailsType has been removed. This type was used by the InsuranceDetails and InternationalInsuranceDetails containers in Add/Revise/Relist/Verify calls for sellers to offer shipping insurance to buyers on any eBay site. This feature is no longer applicable/supported on any eBay sites.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1031 and Changed Functionality - 1031.
Although the SellerProfiles container has always been returned by 'Get' calls like GetItem since Business Policies have been supported by the Trading API, this container was missing in the Call Reference pages for the 'Get' calls. This container now appears in the Call Reference pages for the following calls:
In the ShippingTimeMax and ShippingTimeMin fields of ShippingServiceDetails, ShippingServiceOptionsType, and MultiLegShipmentType, it was clarified that the shipping times are based on business days only. For ShippingServiceDetails (returned in the GeteBayDetails call), it was also stated that the seller should look at the ShippingTimeMax value for a shipping service when setting up a listing for eBay Guaranteed Delivery. With eBay Guaranteed Delivery, becoming available in October 2017, the seller's handling time and the shipping time must be four days or less.
Documentation Changes and Errata - 1029
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
Starting on September 1, 2017, sellers will no longer be able to list and buyers will no longer be able to buy on Half.com. Beginnning on this date, Half.com will redirect to eBay.com. Returns and refunds for Half.com listings will continue to be processed until October 31, 2017. Half.com users will still have access to their My Account Page until November 30, 2017. For more information on this change, please see the Half.com Closing FAQ page.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1029.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
Gift Services and the Gift Icon (in listings) are no longer supported on any eBay Marketplace sites. This means that the Item.GiftServices and Item.GiftIcon fields should no longer be used in Add/Revise/Relist/Verify calls.
The following listing enhancements are no longer supported on any eBay Marketplace sites. This means that the enumeration values associated with this listing enhancements should no longer be passed in through the Item.ListingEnhancement field. Here are the deprecated listing enhancements along with their associated enumeration values:
BasicUpgradePackBundle)Border)Featured)Highlight)ProPackBundle)ProPackPlusBundle)This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1029 and Changed Functionality - 1029.
None for this release.
Documentation Changes and Errata - 1027
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
Beginning on August 31, 2017, API support for Half.com listings is being fully deprecated. For a full list of API calls, types, fields, and enumeration values affected by this change, see the Documentation Changes and Errata section.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1027.
Beginning with Version 1027, sellers on the US, UK, and DE sites can offer the Best Offer feature in auction listings. The seller can offer Buy It Now or Best Offer in an auction listing, but not both features.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1027 and Changed Functionality - 1027.
Beginning on August 31, 2017, API support for Half.com listings is being fully deprecated. This section will discuss the full list of API calls, types, fields, and enumeration values affected by this change.
The following Trading API calls are exclusively for Half.com listings, and these calls will no longer function beyond August 31:
The following Trading API types are exclusively for Half.com listings, and these types will no longer be applicable beyond August 31:
The following Trading API fields and enumeration values are exclusively for Half.com listings, and these fields/values will no longer be applicable beyond August 31:
Half enumeration value of ListingTypeCodeTypeShipped enumeration value of OrderStatusCodeTypeHalf enumeration value of TransactionPlatformCodeTypeCreditCardVerifyHalfOptIn and UnconfirmedHalfOptIn enumeration values of UserStatusCodeTypeDocumentation Changes and Errata - 1025
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
MembershipDetailsType |
Type | New |
MembershipDetailType |
Type | New |
UserType.Membership |
Element | New |
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
Beginning with Version 1027, sellers on the US, UK, and DE sites will be able to offer the Best Offer feature in auction listings. Once this new capability rolls out, the seller can offer Buy It Now or Best Offer in an auction listing, but not both.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1025.
If a seller is enrolled in one or more membership programs, such as eBay Plus, a Membership container will be returned in the GetUser call. This Membership container will provide details about the seller's membership, including the applicable eBay site and the membership expiration date.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1025 and Changed Functionality - 1025.
All applicable Best Offer calls, fields, and feature guide documentation was updated to reflect the fact that Best Offers will soon be available for auction listings on the US, UK, and DE sites.
Documentation Changes and Errata - 1019
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
RateTableDetailsType.DomesticRateTableId |
Element | New |
RateTableDetailsType.InternationalRateTableId |
Element | New |
TransactionType.GuaranteedDelivery |
Element | New |
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
The following changes, announced in the Spring and Summer Seller Update, are going into effect soon:
For more information on any of these changes, you can visit the 2017 Spring and Summer Updates.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1019.
eBay is rolling out new domestic and international shipping rate tables to My eBay Shipping Preferences and to the Seller Hub page. Each seller will be able to create a maximum of 20 domestic and/or international shipping rate tables. These shipping rate tables can be applied to a listing by using the new DomesticRateTableId and InternationalRateTableId fields that were added to the ShippingDetails.RateTableDetails container. Sellers will still be able use the old domestic and international shipping rate tables, but they cannot combine old and new tables. They have to use one or the other. These shipping rate tables are being rolled out to US and Australia sellers this month, and rolled out to UK and Germany sellers next month.
A GuaranteedDelivery boolean field was added to TransactionType, and will be returned in the GetOrders, GetOrderTransactions, GetItemTransactions, and GetSellerTransactions calls to indicate whether or not the seller is committed to eBay Guaranteed Delivery. With eBay Guaranteed Delivery, the seller is committing to getting the order to the buyer within three business days. To enable this possibility, the seller must offer 0 or 1-day handling and a one-day or expedited shipping service. This feature will first become available to US sellers in late summer 2017.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
The maximum length of a single eBay category name has increased from 30 to 50 characters. This constraint change is applicable to the eBay category names that are returned in the CategoryName field that is returned in the GetCategories, GetContextualKeywords, GetSellingManagerTemplates, and GetSuggestedCategories calls.
Numerous confidential/sensitive data fields have been hidden to any party other than buyer or seller in the responses of the order management calls (GetOrders, GetOrderTransactions, GetItemTransactions, and GetSellerTransactions). If a third party caller is using a Trading WSDL older than 1019, these confidential/sensitive data fields will not even be returned. If a third party caller is using a Trading WSDL 1019 or above, these confidential/sensitive data fields will be returned but will contain dummy/masked data. Below is the list of data fields that this change affects:
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1019 and Changed Functionality - 1019.
None for this release.
Documentation Changes and Errata - 1017
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1017.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1017 and Changed Functionality - 1017.
General documentation cleanup was performed for several calls and types.
Documentation Changes and Errata - 1015
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1015.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1015 and Changed Functionality - 1015.
General documentation cleanup was performed for several calls and types.
Documentation Changes and Errata - 1013
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1013.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1013 and Changed Functionality - 1013.
General documentation cleanup was performed for several calls and types.
Documentation Changes and Errata - 1011
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1011.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1011 and Changed Functionality - 1011.
General documentation cleanup was performed for several calls and types.
Documentation Changes and Errata - 1009
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1009.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1009 and Changed Functionality - 1009.
General documentation cleanup was performed for several calls and types.
Documentation Changes and Errata - 1007
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1007.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1007 and Changed Functionality - 1007.
General documentation cleanup was performed for several calls and types.
Documentation Changes and Errata - 1005
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
The maximum length of an eBay category name (returned in CategoryName field of numerous Trading API calls will be increasing from 30 characters to 50 characters. This change is expected to go into effect on train 1019, scheduled for release in the middle of June 2017. This change will affect the following calls:
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1005.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1005 and Changed Functionality - 1005.
General documentation cleanup was performed for several types.
Documentation Changes and Errata - 1003
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1003.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1003 and Changed Functionality - 1003.
General documentation cleanup was performed for several types.
Documentation Changes and Errata - 1001
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
No schema changes in this release.
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
Although new schema has recently been added the Add/Revise/Relist/Verify calls and the GetCategorySpecifics call to support a new method of specifying/using product identifiers, this schema will not be available for use in the Sandbox or Production Environments until later in 2017. Expected wire-on dates are expected to be announced as we get close to the second half of 2017. See the Required Product Identifiers Mandate (Current Phase) topic for more information on how product identifiers are currently used/specified in the Trading API, and see the Required Product Identifiers Mandate (Future Phase) topic for more information on how product identifiers will be used/specified in the Trading API beginning later in 2017.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 1001.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 1001 and Changed Functionality - 1001.
None for this release.
General documentation cleanup was performed for several types.
Documentation Changes and Errata - 997
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
CalculatedShippingRateType.PackageDepth |
Element | Removed |
CalculatedShippingRateType.PackageLength |
Element | Removed |
CalculatedShippingRateType.PackageWidth |
Element | Removed |
CalculatedShippingRateType.ShippingPackage |
Element | Removed |
CalculatedShippingRateType.WeightMajor |
Element | Removed |
CalculatedShippingRateType.WeightMinor |
Element | Removed |
ItemType.ListingCheckoutRedirectPreference |
Element | Removed |
ItemType.PostCheckoutExperienceEnabled |
Element | Removed |
ItemType.SkypeContactOption |
Element | Removed |
ItemType.SkypeEnabled |
Element | Removed |
ItemType.SkypeID |
Element | Removed |
ItemType.ThirdPartyCheckout |
Element | Removed |
ItemType.ThirdPartyCheckoutIntegration |
Element | Removed |
ItemType.UseRecommendedProduct |
Element | Removed |
ListingCheckoutRedirectPreferenceType |
Type | Deprecated |
PictureDetailsType.GalleryURL |
Element | Removed |
PictureFormatCodeType.PNG |
Enum | New |
ProductListingDetailsType.NameValueList |
Element | New |
ReturnPolicyType.EAN |
Element | Removed |
ShippingDetailsType.InsuranceFee |
Element | Removed |
ShippingDetailsType.InsuranceOption |
Element | Removed |
VariationProductListingDetailsType.NameValueList |
Element | New |
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
The NameValueList container was added to the ProductListingDetails and VariationProductListingDetails container in Add/Revise/Relist/Verify calls. Although the NameValueList container was added, it will not be available for use in the Sandbox environment until late in the second quarter, and not available in the Production environment until after June.
Ultimately, specifying product identifiers through the NameValueList container will replace the process of specifying product identifiers through the BrandMPN container, or through the EAN, ISBN, or UPC fields. For more information on how product idenfiers are specified now, see the Required Product Identifiers Mandate (Current Phase) topic. For more information on how product idenfiers will be specified in the future, see the Required Product Identifiers Mandate (Future Phase) topic.
Several complex types were cleaned up for 997. The changes are summarized in the table below.
| Type | Field(s) | Deprecation Reason |
|---|---|---|
CalculatedShippingRateType |
PackageDepth, PackageLength, PackageWidth, ShippingPackage, WeightMajor, WeightMinor | Package type, Package dimensions, and package weight should be specified in the ShippingPackageDetails container instead. |
ItemType |
ListingCheckoutRedirectPreference, PostCheckoutExperienceEnabled, SkypeContactOption, SkypeEnabled, SkypeID, ThirdPartyCheckout, ThirdPartyCheckoutIntegration, UseRecommendedProduct | Third-party checkout, Post-Checkout Experience, and member communication through Skype have all been deprecated, and the UseRecommendedProduct is also no longer applicable. |
PictureDetailsType |
GalleryURL | This field is only used internally. |
ReturnPolicyType |
EAN | An EAN should be specified through the ProductListingDetails or VariationProductListingDetails (multiple-variation listings only) containers instead. |
ShippingDetailsType |
InsuranceFee, InsuranceOption | If applicable, the shipping insurance option and fee should be specified in the ShippingDetails.InsuranceDetails or ShippingDetails.InternationalInsuranceDetails containers instead. |
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 997.
None for this release.
A PNG enumeration value was added to PictureFormatCodeType to support PNG format pictures in the UploadSiteHostedPictures call.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
Sellers are encouraged to provide product identifying information for all listings. If you're using the ItemSpecifics container to provide product identifiers for a catalog-enabled category, you must comply with new validation requirements for the ItemSpecifics.Name and ItemSpecifics.Value fields.
Valid types of product identifiers in the Name field are:
BrandMPNEAN (European Article Number)ISBN (International Standard Book Number)JAN (Japanese Article Number — used only in Japan)UPC (Universal Product Code)For any of these Names, the Value field must comply with the new guidelines to avoid an error condition. See Product Identification Using Item Specifics for the detailed guidelines.
Valid product identifiers help sellers populate their listings with product information from the eBay catalog; they help your sellers' listings appear in search engine results (such as Google or Bing) so buyers can find what they're looking for; and they also help to include features in the listing such as product reviews. Without valid product identifiers, your sellers will lose out on these enhancements and the sales they generate.
For more information about product identifiers, see Listing for Advanced Sellers.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 997 and Changed Functionality - 997.
None for this release.
Documentation Changes and Errata - 995
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
ShippingPackageInfoType.HandleByTime |
Element | New |
ShippingPackageInfoType.MaxNativeEstimatedDeliveryTime |
Element | New |
ShippingPackageInfoType.MinNativeEstimatedDeliveryTime |
Element | New |
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 995.
The following three fields are now conditionally returned through the ShippingPackageInfo container in GetOrders, GetItemTransactions, GetSellerTransactions, and GetOrderTransactions:
HandleByTimeMaxNativeEstimatedDeliveryTimeMinNativeEstimatedDeliveryTimeThis section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 995 and Changed Functionality - 995.
None for this release.
Documentation Changes and Errata - 991
For a current list of known issues, see Site Status Updates and the Knowledge Base.
No new calls in this release.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
Enumeration note: You need to use this release version or higher to retrieve new code list valuesthat were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
NotificationEventTypeCodeType.OrderInquiryOpened | Enum | New |
NotificationEventTypeCodeType.OrderInquiryReminderForEscalation | Enum | New |
NotificationEventTypeCodeType.OrderInquiryProvideShipmentInformation | Enum | New |
NotificationEventTypeCodeType.OrderInquiryClosed | Enum | New |
NotificationEventTypeCodeType.OrderInquiryEscalatedToCase | Enum | New |
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
This section describes new features that have been added as of this release. New features can involve new calls, newcapabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 991.
Five new seller-oriented notifications have been added to alert sellers about updates to Item Not Received inquiries. These five notifications include the following:
OrderInquiryOpenedOrderInquiryReminderForEscalationOrderInquiryProvideShipmentInformationOrderInquiryClosedOrderInquiryEscalatedToCaseSee NotificationEventTypeCodeType for more information about these new notification event types.
This section describes logical or functional changes that have been made to existing functionality, including newcode list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that arenot already mentioned in New Features - 991 and Changed Functionality - 991.
None for this release.
Documentation Changes and Errata - 989
For a current list of known issues, see Site Status Updates and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Enumeration note: You need to use this release version or higher to retrieve new code list values that were added in this release. See Code Lists.
| Name | Part of Schema | Type of Change |
|---|---|---|
GroupValidationRulesType |
Complex type | New |
ProductIdentifiersType |
Complex type | New |
RecommendationsType.ProductIdentifiers |
Element | New |
See the API Site Status for announcements regarding recently resolved or current system wide issues. Visit the Developer Support page for support options and information on filing bugs.
The next phase of Product Identifier Mandate has been postponed until July 2017. The new schema to support the upcoming mandate has already been added to the GetCategoryFeatures call, but the functionality will only be supported in the Sandbox environment. Similarly, new schema will be added to the Add/Revise/Relist with version 997, but the functionality will only be supported in the Sandbox environment.
This section describes new features that have been added as of this release. New features can involve new calls, new capabilities, and/or new fields added to existing calls.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 989.
None for this release.
If Product Identifiers are applicable for the eBay category, a new ProductIdentifiers container will be returned for each category ID that is passed into the GetCategorySpecifics request. The ProductIdentifiers container will consist of one or more Product Identifier types that can be, or possibly required to be used when listing a product. These Product Identifier types will be common Global Trade Item Number (GTIN) types such as UPC, ISBN, and EAN. As of 989, this container will only be returned in the Sandbox environment. This container has not been wired on in Production.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 989 and Changed Functionality - 989.
None for this release.
Copyright © 2005–2017 eBay, Inc. All rights reserved. This documentation and the API may only be used in accordance with the eBay Developers Program and API License Agreement.