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 - 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.
Documentation Changes and Errata - 983
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 - 983.
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 - 983 and Changed Functionality - 983.
None for this release.
Documentation Changes and Errata - 981
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.
A GuaranteedShipping boolean field was added to the WSDL, but this field will not be returned in order management calls (GetOrders, GetSellerTransactions, etc.) until the feature becomes available to sellers in October.
Once the feature becomes available, and turned on in the API, this field will be returned as true if the seller chose to use eBay's Guaranteed Shipping feature at listing time. With eBay's Guaranteed Shipping, the seller will never pay more for shipping than what is charged to the buyer. The Guaranteed Shipping price will be based on the shipping service option and on the dimensions and weight of the shipping package. Initially, eBay's Guaranteed Shipping feature can not be selected with the Add/Revise/Relist API calls, but must be set up through the Web flow.
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 - 981.
None for this release.
A Status.CancelStatus field will now be returned in the WonList and DeletedFromWonList container in the GetMyeBayBuying response for order line items that have a pending, active, or completed cancellation request.
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 - 981 and Changed Functionality - 981.
None for this release.
The ItemSortTypeCodeType values available for use in an GetItemsAwaitingFeedback request were not completely accurate. The field description for the Sort field was missing the following enumeration values:
FeedbackLeftDescendingFeedbackReceivedUserID
And QuestionCount was actually removed from the document, as this enumeration value is not supported by the Sort field.
The documentation for StartPrice (in ItemType), and BestOfferAutoAcceptPrice and MinimumBestOfferPrice (in ListingDetailsType) was modified to let users know that the Best Offer Auto Accept (BestOfferAutoAcceptPrice field) and Best Offer Auto Reject (MinimumBestOfferPrice field) threshold values will be lost when a listing is revised with a new StartPrice value. The seller would have to make an additional Revise call if they wanted to reintroduce the Best Offer thresholds in the listing. This behavior is not applicable to auction listings.
Documentation Changes and Errata - 979
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 |
|---|---|---|
FeedbackDetailType.FeedbackRatingStar |
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 - 979.
A new FeedbackRatingStar field is now returned in the GetFeedback response. The enumeration value returned in this field indicates Feedback score range of the user that has left Feedback.
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.
Beginning with Version 979, for Feedback entries that were left for the buyer by the seller, some of the FeedbackDetail container fields that are returned in the GetFeedback call will no longer be returned to users who were not involved in the transaction as either the buyer or seller. These fields include the following:
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 979 and Changed Functionality - 979.
It was called out in the Call Reference documentation for GetOrders, GetOrderTransactions, GetSellerTransactions, and GetItemTransactions calls that only orders less than 90 days old may be retrieved with these calls.
The RuName field description was clarified in the GetSessionID Call Reference documentation. The RuName is an eBay Registered URL that is added and associated with an eBay developer's Sandbox and Production key sets.
The BestOfferEnabled field description was updated to make it clear that its boolean value cannot be changed (enabled or disabled) with a ReviseItem or ReviseFixedPriceItem call once the fixed-price listing has any sales (Best Offer or standard purchase), or if the listing has a Best Offer or counter offer that is currently pending.
Documentation Changes and Errata - 977
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.
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 - 977.
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.
General cleanup of API Call Reference documentation was performed for Version 977.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 977 and Changed Functionality - 977.
None for this release.
Documentation Changes and Errata - 975
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.
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 - 975.
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.
UK scooter parts now supports compatibilities, where compatibilities can be added by Application using name/value pairs (like UKM_Make, UKM_Model, etc), or by using the ePID number for the parts. See Manually specifying parts compatibility for details.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 975 and Changed Functionality - 975.
Previously, the call reference documentation for the GetItem and GetSellingManagerTemplates calls were not displaying product identifier-related fields (under the ProductListingDetails container), even though these fields are returned in these calls, when applicable. The following fields are now being displayed in these two calls under the ProductListingDetails container:
The description for the ReceivedTopRatedDiscount field (returned in GetAccount call) was updated to state that the field is only returned after eBay bills the seller for the Final Value Fee for the eligible order line item.
The description for the DetailedMessage field (returned in VeROReportItems call) was updated to state that there is a 1000-character restriction on this text field when the items are being reported with the <code>Others</code> reason code.
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.