Trading API

Trading API Release Notes

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:

Q1 2017
Version Release Date
1009 2017-Mar-31
1007 2017-Mar-17
1005 2017-Mar-03
1003 2017-Feb-17
1001 2017-Feb-03
999 Skipped
997 2017-Jan-20
995 2017-Jan-06
Q4 2016
Version Release Date
993 No schema or doc changes
991 2016-Oct-21
989 2016-Oct-07
Q3 2016
Version Release Date
987 No schema or doc changes
985 No schema or doc changes
983 2016-Aug-26
981 2016-Aug-12
979 2016-Jul-29
977 2016-Jul-15
975 2016-Jul-01
Q2 2016
Version Release Date
973 Not Released
971 2016-Jun-03
969 Not Released
967 2016-May-06
965 2016-Apr-22
963 2016-Apr-08

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.

Version 1007

Index of Changed Calls - 1007

Schema Changes - 1007

Announcements - 1007

New Features - 1007

Changed Functionality - 1007

Documentation Changes and Errata - 1007

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 1007

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.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 1007

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.

Announcements - 1007

Change Requests

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.

New Features - 1007

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.

Changed Functionality - 1007

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.

Documentation Changes and Errata - 1007

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.

Minor Edits to Some Call/Type Documentation

General documentation cleanup was performed for several calls and types.

Version 1005

Index of Changed Calls - 1005

Schema Changes - 1005

Announcements - 1005

New Features - 1005

Changed Functionality - 1005

Documentation Changes and Errata - 1005

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 1005

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.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 1005

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.

Announcements - 1005

Change Requests

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.

Max Length of Category Names Increasing

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:

New Features - 1005

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.

Changed Functionality - 1005

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.

Documentation Changes and Errata - 1005

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.

Cleanup of Some Types

General documentation cleanup was performed for several types.

Version 1003

Index of Changed Calls - 1003

Schema Changes - 1003

Announcements - 1003

New Features - 1003

Changed Functionality - 1003

Documentation Changes and Errata - 1003

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 1003

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.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 1003

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.

Announcements - 1003

Change Requests

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.

New Features - 1003

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.

Changed Functionality - 1003

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.

Documentation Changes and Errata - 1003

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.

Cleanup of Some Types

General documentation cleanup was performed for several types.

Version 1001

Index of Changed Calls - 1001

Schema Changes - 1001

Announcements - 1001

New Features - 1001

Changed Functionality - 1001

Documentation Changes and Errata - 1001

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 1001

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.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 1001

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.

Announcements - 1001

Change Requests

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.

Product Identifiers Update

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.

New Features - 1001

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.

Changed Functionality - 1001

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.

Documentation Changes and Errata - 1001

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.

Cleanup of Some Types

General documentation cleanup was performed for several types.

Version 997

Index of Changed Calls - 997

Schema Changes - 997

Announcements - 997

New Features - 997

Changed Functionality - 997

Documentation Changes and Errata - 997

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 997

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 997

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

Announcements - 997

Change Requests

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.

Coming Soon: New Way to Specify Product Identifiers in Listing Calls

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.

Fields Deprecated from Several Complex Types

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.

New Features - 997

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.

PNG Now a Supported Picture Format in UploadSiteHostedPictures

A PNG enumeration value was added to PictureFormatCodeType to support PNG format pictures in the UploadSiteHostedPictures call.

Changed Functionality - 997

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.

Valid Product Identifiers are now Required in Item Specifics

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:

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.

Documentation Changes and Errata - 997

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.

Version 995

Index of Changed Calls - 995

Schema Changes - 995

Announcements - 995

New Features - 995

Changed Functionality - 995

Documentation Changes and Errata - 995

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 995

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 995

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

Announcements - 995

Change Requests

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.

New Features - 995

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.

New Estimated Delivery Fields Returned in Order Management Calls

The following three fields are now conditionally returned through the ShippingPackageInfo container in GetOrders, GetItemTransactions, GetSellerTransactions, and GetOrderTransactions:

Changed Functionality - 995

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.

Documentation Changes and Errata - 995

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.

Version 991

Index of Changed Calls - 991

Schema Changes - 991

Announcements - 991

New Features - 991

Changed Functionality - 991

Documentation Changes and Errata - 991

For a current list of known issues, see Site Status Updates and the Knowledge Base.

New Calls

No new calls in this release.

Index of Changed Calls - 991

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.

Schema Changes - 991

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.

NamePart of SchemaType of Change
NotificationEventTypeCodeType.OrderInquiryOpenedEnumNew
NotificationEventTypeCodeType.OrderInquiryReminderForEscalationEnumNew
NotificationEventTypeCodeType.OrderInquiryProvideShipmentInformationEnumNew
NotificationEventTypeCodeType.OrderInquiryClosedEnumNew
NotificationEventTypeCodeType.OrderInquiryEscalatedToCaseEnumNew

Announcements - 991

Change Requests

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.

New Features - 991

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.

New Seller Notifications Enabled for Order Inquiries

Five new seller-oriented notifications have been added to alert sellers about updates to Item Not Received inquiries. These five notifications include the following:

See NotificationEventTypeCodeType for more information about these new notification event types.

Changed Functionality - 991

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.

Documentation Changes and Errata - 991

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.

Version 989

Index of Changed Calls - 989

Schema Changes - 989

Announcements - 989

New Features - 989

Changed Functionality - 989

Documentation Changes and Errata - 989

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 989

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 989

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.

NamePart of SchemaType of Change
GroupValidationRulesType Complex type New
ProductIdentifiersType Complex type New
RecommendationsType.ProductIdentifiers Element New

Announcements - 989

Change Requests

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 the Product Identifier Mandate Postponed

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.

New Features - 989

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.

Supported/Required Product Identifier Types Returned in GetCategorySpecifics

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.

Changed Functionality - 989

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.

Documentation Changes and Errata - 989

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.

Version 983

Index of Changed Calls - 983

Schema Changes - 983

Announcements - 983

New Features - 983

Changed Functionality - 983

Documentation Changes and Errata - 983

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 983

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.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 983

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.

Announcements - 983

Change Requests

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.

New Features - 983

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.

Changed Functionality - 983

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.

Documentation Changes and Errata - 983

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.

Version 981

Index of Changed Calls - 981

Schema Changes - 981

Announcements - 981

New Features - 981

Changed Functionality - 981

Documentation Changes and Errata - 981

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 981

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 981

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.

Announcements - 981

Change Requests

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.

GuaranteedShipping Field to Start Being Returned in Order Management Calls

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.

New Features - 981

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.

CancelStatus Field Now Returned in GetMyeBayBuying When Applicable

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.

Changed Functionality - 981

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.

Documentation Changes and Errata - 981

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.

Corrected the Available Sort Values for GetItemsAwaitingFeedback

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:

And QuestionCount was actually removed from the document, as this enumeration value is not supported by the Sort field.

Best Offer Auto Accept/Reject Values Lost When StartPrice is Revised

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.

Version 979

Index of Changed Calls - 979

Schema Changes - 979

Announcements - 979

New Features - 979

Changed Functionality - 979

Documentation Changes and Errata - 979

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 979

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 979

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.

NamePart of SchemaType of Change
FeedbackDetailType.FeedbackRatingStar Element New

Announcements - 979

Change Requests

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.

New Features - 979

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.

Feedback Rating Star Now Returned in GetFeedback Call

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.

Changed Functionality - 979

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.

Other Updates to GetFeedback Call

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:

Documentation Changes and Errata - 979

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.

Restriction of Order Management Calls Clarified

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.

RuName Field Description Clarified

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.

Restriction on Revising BestOfferEnabled Value

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.

Version 977

Index of Changed Calls - 977

Schema Changes - 977

Announcements - 977

New Features - 977

Changed Functionality - 977

Documentation Changes and Errata - 977

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 977

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 977

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.

Announcements - 977

Change Requests

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.

New Features - 977

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.

Changed Functionality - 977

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.

Doc Cleanup and Maintenance

General cleanup of API Call Reference documentation was performed for Version 977.

Documentation Changes and Errata - 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.

Version 975

Index of Changed Calls - 975

Schema Changes - 975

Announcements - 975

New Features - 975

Changed Functionality - 975

Documentation Changes and Errata - 975

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 975

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 975

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.

Announcements - 975

Change Requests

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.

New Features - 975

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.

Changed Functionality - 975

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

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.

Documentation Changes and Errata - 975

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.

GetItem and GetSellingManagerTemplates Call Reference Documentation Updated

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:

ReceivedTopRatedDiscount Field Description Updated

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.

DetailedMessage Field Description Updated

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.

Version 971

Index of Changed Calls - 971

Schema Changes - 971

Announcements - 971

New Features - 971

Changed Functionality - 971

Documentation Changes and Errata - 971

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 971

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.

New Calls

No new calls in this release.

Changed Calls

No changed calls in this release.

Schema Changes - 971

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.

Announcements - 971

Change Requests

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.

New Features - 971

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 - 971.

None for this release.

Changed Functionality - 971

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.

Documentation Changes and Errata - 971

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 971 and Changed Functionality - 971.

Updates to BuyerTaxIdentifier Field

Minor updates were made to the field description for the BuyerTaxIdentifier field that is returned in order management calls.

Call Samples Updated

Numerous samples in numerous calls were updated.

Version 967

Index of Changed Calls - 967

Schema Changes - 967

Announcements - 967

New Features - 967

Changed Functionality - 967

Documentation Changes and Errata - 967

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 967

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 967

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.

NamePart of SchemaType of Change
EpidSupportedDefinitionType Complex type New
KTypeSupportedDefinitionType Complex type New
CategoryFeatureType.EpidSupported Element New
CategoryFeatureType.KTypeSupported Element New
FeatureDefinitionsType.EpidSupported Element New
FeatureDefinitionsType.KTypeSupported Element New
SiteDefaultsType.EpidSupported Element New
SiteDefaultsType.KTypeSupported Element New
FeatureIDCodeType.EpidSupported Enum New
FeatureIDCodeType.KTypeSupported Enum New

Announcements - 967

Change Requests

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.

New Features - 967

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 - 967.

New Parts Compatibility Fields Added to GetCategoryFeatures

New EpidSupported and KTypeSupported fields added to GetCategoryFeatures call to indicate which sites and categories support the ability to supply an eBay Product ID (ePID) or an K Type vehicle number to identify a motor vehicle in an Add/Revise/Relist call that is compatible with a part or accessory.

K type vehicle numbers can only be used to identify cars and trucks on the Germany site, and ePIDs can only be used to identify motorcycles and scooters on the Germany and UK sites.

Changed Functionality - 967

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.

Documentation Changes and Errata - 967

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 967 and Changed Functionality - 967.

None for this release.

Version 965

Index of Changed Calls - 965

Schema Changes - 965

Announcements - 965

New Features - 965

Changed Functionality - 965

Documentation Changes and Errata - 965

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 965

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.

New Calls

No new calls in this release.

Changed Calls

No changed calls

Schema Changes - 965

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.

NamePart of SchemaType of Change
ProductListingDetailsType.ProductID Element Removed

Announcements - 965

Change Requests

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.

New Features - 965

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 - 965.

None for this release.

Changed Functionality - 965

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.

ProductListingDetails.ProductID Field Being Deprecated

Sellers should no longer use the ProductListingDetails.ProductID field to identify an eBay catalog product in an add/revise/relist call. Instead, the seller should only pass in the eBay Product ID (ePID) through the ProductListingDetails.ProductReferenceID field.

Documentation Changes and Errata - 965

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 965 and Changed Functionality - 965.

None for this release.

Version 963

Index of Changed Calls - 963

Schema Changes - 963

Announcements - 963

New Features - 963

Changed Functionality - 963

Documentation Changes and Errata - 963

For a current list of known issues, see Site Status Updates and the Knowledge Base.

Index of Changed Calls - 963

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.

New Calls

No new calls in this release.

Changed Calls

Schema Changes - 963

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.

Announcements - 963

Change Requests

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.

2016 Spring Seller Updates

The 2016 Spring Seller Update has been released. Below is a summary of the announced new features and changes:

Coming Soon: Business Policies Opt-In/Opt-Out Will Be Enforced

Starting soon, a seller's choice to opt into or out of Business Policies will determine which API fields can be used when creating/revising/relisting their listings.

Using Business Policies
To list items using Business Policies, the seller will have defined at least one of each of the following Business Policies types:

You can create and manage these profiles in My eBay, or by using the Business Policies Management API. If you are opted in to Business Policies, you will only reference the profile IDs of these business policies in the Item.SellerProfiles container in an Add/Revise/Relist call, and the payment, return policy, and shipping-related fields in those referenced business policies will be used to create or revise the listing instead of the "legacy" payment, return policy, and shipping fields in the Trading API. If you pass in Business Policies profile IDs and the legacy fields, the legacy fields will be ignored and dropped. See the Mapping Business Policies Management API Fields to Trading API Fields table in the Business Policies Users Guide for a complete list of the legacy Trading API fields and their equivalent Business Policies fields that should be used instead.

Opt-In Enforcement Details
Previously, sellers who were opted into Business Policies could create listings using either the Business Policies API fields or the equivalent legacy Trading API fields, or even a combination of the two. This will no longer be allowed.

Any seller who is opted into Business Policies will not be able to use the legacy fields at all, for Payment, Returns or Shipping in any new listing. If legacy fields are passed into the request, they will be ignored and dropped and the seller may get a warning message to that effect.

One exception to this requirement: when an opted-in seller has an existing listing. If the listing uses only legacy fields, the seller can relist or revise the item using legacy fields, until the listing expires/ends, or is withdrawn by the seller. However, if the listing uses a combination of legacy fields and business policies, the seller will be prevented from continuing the listing, and will receive an error message indicating that they must cancel the listing and recreate it with business policies only.

Opt-Out Enforcement Details
If a seller is opted out of (or have not opted into) Business Policies, that seller cannot reference any business policies to create, relist, or revise any listing.

Actions to Take
Act now to ensure that your selling application gracefully anticipates the upcoming change, so sellers will not be inconvenienced as they conduct their business on eBay:

  1. Inform your sellers of their obligations when opted into or out of Business Policies.
  2. Ensure that opted-in sellers have at least one Payment profile, one Return profile, and one Shipping profile defined for their account.
  3. Modify or replace sellers' current listings as necessary to comply with their opt-in or opt-out status.
  4. Sellers can only opt-in and opt-out of Business Policies through My eBay (My eBay > Account > Manage your business polices)
  5. Sellers can see their opt-in/opt-out status, and also view all Business Policies defined for their account in My eBay or by using the GetUserPreferences call. If using the GetUserPreferences call, the seller should include the ShowSellerProfilePreferences boolean field in the request and set to true.

New Features - 963

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 - 963.

Changed Functionality - 963

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.

Documentation Changes and Errata - 963

This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 963 and Changed Functionality - 963.

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.