Merchant Data API

Merchant Data API Release Notes Archive

You can find links to the Merchant Data API documentation in the top navigation bar.

This archive document contains information about releases that go back longer than four quarters ago. For more recent releases, see the current Release Notes.

Are you new to the Large Merchant Services solution?

If so, see Large Merchant Services User Guide -- an introduction to the eBay Large Merchant Services solution.

Are you just getting started with the eBay Developer's Program?

The following links provide useful information for beginners:

Q1 2016
Version Release Date
961 Not Released
959 2016-Mar-11
957 2016-Feb-26
955 2016-Feb-12
953 Not Released
951 2016-Jan-15
Q4 2015
Version Release Date
949 2015-Nov-12
947 2015-Oct-29
945 2015-Oct-15
943 2015-Oct-01
Q3 2015
Version Release Date
941 2015-Sep-18
939 2015-Sep-04
937 Not Released
935 2015-Aug-07
933 2015-Jul-24
931 2015-Jul-10
Q2 2015
Version Release Date
929 2015-Jun-26
927 2015-Jun-12
925 2015-May-29
923 2015-May-15
921 2015-May-01
919 2015-Apr-17
917 2015-Apr-03

These releases go back longer than four quarters ago. For more recent releases, see the current Release Notes.

Version 959

Index of Changed Calls - 959

Schema Changes - 959

Announcements - 959

New Features - 959

Changed Functionality - 959

Documentation Changes and Errata - 959

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

Index of Changed Calls - 959

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 - 959

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 - 959

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 - 959

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

AddItem Family of Calls Support Motorcycle Parts Compatibility in DE and UK

In the AddItem family of calls, the ItemCompatabilityType type has been expanded to accept eBay Product ID (ePID) numbers on the DE and UK eBay sites to specify parts compatibility for motorcycle and scooter parts compatibility. For details and examples, see the Features Guide.

Changed Functionality - 959

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 - 959

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

ShipmentLineItem Container Now Correctly Represented

Previously, the documentation erroneously indicated that Shipment.ShipmentLineItem was conditionally required in the SetShipmentTrackingInfo call request. In fact, the ShipmentLineItem container was and is part of ShipmentTrackingDetails, and the documentation now correctly displays Shipment.ShipmentTrackingDetails.ShipmentLineItem in the request prototype.

Version 957

Index of Changed Calls - 957

Schema Changes - 957

Announcements - 957

New Features - 957

Changed Functionality - 957

Documentation Changes and Errata - 957

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

Index of Changed Calls - 957

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 - 957

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 - 957

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.

Listing Calls to Support Boats and Motorcycle Parts Compatibility in DE and UK

In the AddItem family of calls, the ItemCompatibilityType type will soon be expanded to accept eBay Product ID (ePID) numbers on the DE and UK eBay sites to specify parts compatibility for motorcycles (in DE, scooter parts compatibility is also supported). For details and examples, see the Features Guide.

New Features - 957

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

None for this release.

Changed Functionality - 957

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.

Global Shipping Warehouse Addresses Changed

Sellers in the UK and US who take advantage of the Global Shipping Program send their shipments to the respective address of their international shipping provider's domestic warehouse, from which the carrier completes the shipment. The mailing addresses of the UK and US warehouses have changed.

The new warehouse addresses are returned by the OrderReport call. The new addresses are as follows:

UK Warehouse

GSP Shipping Centre, 1 Langham Park
South Normanton DE55 2GF

US Warehouse

1850 Airport Exchange Blvd #200
Erlanger KY 41025

For details about how to use this information, see Addressing a Global Shipping Program Shipment.

Documentation Changes and Errata - 957

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

None for this release.

Version 955

Index of Changed Calls - 955

Schema Changes - 955

Announcements - 955

New Features - 955

Changed Functionality - 955

Documentation Changes and Errata - 955

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

Index of Changed Calls - 955

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 - 955

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 - 955

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 - 955

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

None for this release.

Changed Functionality - 955

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.

Several Payment Methods are No Longer Supported

Skrill (formerly Moneybookers), Paymate, and ProPay are no longer supported as acceptable payment methods on any eBay site. Starting with Version 945, sellers were already blocked from specifying these payment methods in listing calls, but the enumeration values associated with these payment methods (Moneybookers, Paymate, and ProPay) were still being returned in OrderReport and SoldReport. These three enumeration values have now been removed from BuyerPaymentMethodCodeType and will not be returned in any calls.

Documentation Changes and Errata - 955

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

Fixed SetShipmentTrackingInfo Call Reference

The Shipment container in the request payload structure of the SetShipmentTrackingInfo call was previously misrepresented. The deprecated ShippingCarrierUsed and ShipmentTrackingNumber fields had been replaced by a new ShipmentTrackingDetails container with new versions of those same fields, as well as a set of Global Shipping Program fields, but neither the old or the new fields appeared in the documentation. This has been fixed, so the Shipment container now looks like the following:

<Shipment>
    <ShipmentTrackingDetails>
        <ShippingCarrierUsed></ShippingCarrierUsed>
        <ShipmentLineItem>
            <LineItem>
                <CountryOfOrigin></CountryOfOrigin>
                <Description></Description>
                <ItemID></ItemID>
                <Quantity></Quantity>
                <TransactionID></TransactionID>
            </LineItem>
        </ShipmentLineItem>
        <ShipmentTrackingNumber></ShipmentTrackingNumber>
    </ShipmentTrackingDetails>
    <ShippedTime></ShippedTime>
</Shipment>

Note: The ShipmentLineItem container is required only for Global Shipping Program shipments. For more information about all of the fields in the ShipmentTrackingDetails container, see the SetShipmentTrackingInfo call reference.

Version 951

Index of Changed Calls - 951

Schema Changes - 951

Announcements - 951

New Features - 951

Changed Functionality - 951

Documentation Changes and Errata - 951

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

Index of Changed Calls - 951

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 - 951

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 - 951

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 - 951

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

None for this release.

Changed Functionality - 951

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 - 951

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

Doc Cleanup and Maintenance

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

Version 949

Index of Changed Calls - 949

Schema Changes - 949

Announcements - 949

New Features - 949

Changed Functionality - 949

Documentation Changes and Errata - 949

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

Index of Changed Calls - 949

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 - 949

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 - 949

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 - 949

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

None for this release.

Changed Functionality - 949

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 - 949

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

Doc Cleanup and Maintenance

General cleanup of API Call Reference documentation was performed for Version 949, including an update to the copyright year in all page footers.

Version 947

Index of Changed Calls - 947

Schema Changes - 947

Announcements - 947

New Features - 947

Changed Functionality - 947

Documentation Changes and Errata - 947

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

Index of Changed Calls - 947

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 - 947

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 - 947

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 - 947

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

Flat Rate Freight Shipping Service

The eBay US site now supports a new type of flat rate shipping service: Flat Rate Freight. This feature provides convenience and predictable cost to buyers on freight shipping of heavy and bulky packages within the United States. Any listing that requires freight shipping can be offered by the seller with free shipping or a single flat rate for all domestic buyers. The seller negotiates the actual shipping cost with the freight carrier separately from the checkout process, so the sale can be completed quickly. This improves on conventional freight, which requires the seller to negotiate the shipping cost with the carrier and the buyer before completing the sale.

When using the Add, Relist, Revise, or Verify families of calls to create a listing, the combination of the ShippingDetails.ShippingType and ShippingDetails.ShippingServiceOptions.ShippingService fields is unique for each eBay site and freight shipping option. For Flat Rate Freight, set ShippingType to Flat and ShippingService to FlatRateFreight.

Flat Rate Freight is technically a flat rate option (ShippingType=Flat), but the guidelines for both flat rate shipping and freight shipping apply to Flat Rate Freight. For details, see Specifying Flat Rate Shipping and Specifying Freight Shipping.

Changed Functionality - 947

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 - 947

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

None for this release.

Version 945

Index of Changed Calls - 945

Schema Changes - 945

Announcements - 945

New Features - 945

Changed Functionality - 945

Documentation Changes and Errata - 945

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

Index of Changed Calls - 945

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 - 945

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 - 945

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.

Skrill/Moneybookers, ProPay, and Paymate No Longer Acceptable Payment Methods

Sellers can no longer specify Skrill/Moneybookers, ProPay, or Paymate as accepted payment methods when adding/revising/relisting items. If Moneybookers, Paymate, and/or ProPay are provided as values in a PaymentMethods field of an add/revise/relist call, the listing will be rejected. Existing listings that have any of these accepted payment methods will be allowed to stay active without any revisions, but beginning in mid to late November, eBay will start asking sellers to modify these listings as well, removing these deprecated payment methods from the listings.

Note that the Moneybookers, Paymate, and/or ProPay may still get returned in OrderReport in the short term, but once these values are hard deprecated, they will not be returned at all.

New Features - 945

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

None for this release.

Changed Functionality - 945

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 - 945

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

None for this release.

Version 943

Index of Changed Calls - 943

Schema Changes - 943

Announcements - 943

New Features - 943

Changed Functionality - 943

Documentation Changes and Errata - 943

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

Index of Changed Calls - 943

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 - 943

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 - 943

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.

Upcoming Change to ValueTypeCodeType in GetCategorySpecifics

Starting with Version 945 and going forward, the Decimal enumeration value of ValueTypeCodeType will be replaced by the Numeric data type when the recommended Item Specific is numeric in nature. For the Version 943 WSDL and older, Decimal will continue being returned.

New Features - 943

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

None for this release.

Changed Functionality - 943

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 - 943

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

None for this release.

Version 941

Index of Changed Calls - 941

Schema Changes - 941

Announcements - 941

New Features - 941

Changed Functionality - 941

Documentation Changes and Errata - 941

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

Index of Changed Calls - 941

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 - 941

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 - 941

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.

End of Hassle-Free Returns

The concept of "Hassle-free" returns has been replaced by a single, customizable Returns platform. Sellers no longer opt in to "Hassle-free" returns, but instead, go to Return preferences in My eBay and use basic and/or advanced return rules to automate and configure how return requests from buyers are handled.

The New Returns Flow is discussed in the 2015 Fall Seller Update.

Category and Item Specific Changes

Category and Item Specific changes are coming on October 12. These eBay Category and Item Specifics Updates are discussed in the 2015 Fall Seller Update.

End of Extended Holiday Returns Feature

Starting in October 2015, the Extended Holiday Returns feature will no longer be supported, and the schema elements that support this feature are scheduled for deprecation.

The ExtendedHolidayReturns field in the the Add, Relist, Revise, and Verify families of calls will be ignored (treated as false) by the eBay Trading API until it is removed from the schema. Similarly, you should not depend on the value of the ExtendedHolidayReturns field if it is returned by the GetItem call.

New Features - 941

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

None for this release.

Changed Functionality - 941

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.

IncludePrefillItemInformation Field Deprecated

The IncludePrefillItemInformation boolean field has been deprecated with version 941. The new IncludeeBayProductDetails boolean field should be used instead, and this field controls whether or not an eBay catalog product is used to help create or revise an item listing.

EAN and UPC Product ID Fields

To support cross-border trade and use cases where a seller may be selling a product manufactured in another country, the behavior of the EAN and UPC fields in listing calls has been changed so that the EAN field will accept UPC (Universal Product Code) values and the UPC field will accept EAN (European Article Number) values. Previously, a listing would be blocked if a seller used these fields interchangeably.

Documentation Changes and Errata - 941

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

eBay Catalog Product Lookup Not Supported for Multiple-Variation Listings

Corrected some misleading documentation for the ProductListingDetails.BrandMPN container used in Add/Revise/Relist/Verify calls. Previous documentation stated that only the Brand value should be included in the BrandMPN container, and the MPN value for each product variation should be specified in VariationSpecifics.NameValueList containers. In reality, the ProductListingDetails.BrandMPN container (and eBay catalog product lookup) is only intended for single-variation listings. If a multiple-variation listing with MPNs is to be created, the Brand should be specified in a ItemSpecifics.NameValueList container, and the MPNs for each variation of the product should be specified in VariationSpecifics.NameValueList containers.

Version 939

Index of Changed Calls - 939

Schema Changes - 939

Announcements - 939

New Features - 939

Changed Functionality - 939

Documentation Changes and Errata - 939

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

Index of Changed Calls - 939

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 - 939

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 - 939

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.

Fall 2015 Seller Update Page Released

The Fall 2015 Seller Update page has been released. Please visit this page to see the new products, features, and updated flows coming to eBay this fall. The page has information on the following topics:

New Features - 939

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

None for this release.

Changed Functionality - 939

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.

New IncludeeBayProductDetails Boolean Field in Add/Revise/Relist Calls

The new IncludeeBayProductDetails boolean field controls whether or not an eBay catalog product is used to help create or revise an item listing. Beginning with version 939, this boolean field has essentially replaced the soon-to-be deprecated IncludePrefillItemInformation boolean field.

If the seller wants to use the eBay product catalog to help create or revise the listing, the seller can include this field and set its value to true, or just omit this field, as it default value is true. If a seller doesn't want the eBay product catalog information in their listing, that seller would have to include this field and set its value to false. If the seller does this, they will also be required to pass in their own listing title and description, item specifics, and pictures, and select a listing category.

Documentation Changes and Errata - 939

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

None for this release.

Version 935

Index of Changed Calls - 935

Schema Changes - 935

Announcements - 935

New Features - 935

Changed Functionality - 935

Documentation Changes and Errata - 935

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

Index of Changed Calls - 935

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 - 935

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 - 935

Digital Gift Cards Listings Enabled

All Merchant Data API types and fields related to Digital Gift Card Listings have been enabled for version 935. For more information on the types and fields related to Digital Gift Card Listings, see the 933 Release Notes.

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 - 935

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

None for this release.

Changed Functionality - 935

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 - 935

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

None for this release.

Version 933

Index of Changed Calls - 933

Schema Changes - 933

Announcements - 933

New Features - 933

Changed Functionality - 933

Documentation Changes and Errata - 933

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

Index of Changed Calls - 933

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 - 933

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
DeliveryDetailsType Complex type New
DeliveryStatusType Complex type New
DigitalDeliverySelectedType Complex type New
DigitalDeliveryUserType Complex type New
DigitalGoodInfoType Complex type New
GiftSummaryType Complex type New
DeliveryMethodCodeType Enumerated type New
DeliveryStatusEmailCodeType Enumerated type New
DigitalStatusCodeType Enumerated type New
ItemType.DigitalGoodInfo Element New
TransactionStatusType.DigitalStatus Element New
TransactionType.DigitalDeliverySelected Element New
TransactionType.Gift Element New
TransactionType.GiftSummary Element New
LogisticsPlanCodeType.DigitalDelivery Enum New

Announcements - 933

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 - 933

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

eBay Plus is Introduced in Germany

eBay Plus is a premium account option for buyers which provides benefits such as free 2-day domestic shipping and unlimited free returns on selected items. Sellers receive an FVF discount and DSR protection for eBay Plus listings. This program applies only to domestic shipping, currently only in Germany (items must be located in Germany). More eBay marketplaces will support eBay Plus in the future.

Buyers can enroll in eBay Plus through My eBay; they pay an annual fee for the program. Top Rated Sellers can opt in to eBay Plus through My eBay. This does not obligate them to offer eBay Plus in any listing. Certain items do not qualify for eBay Plus listing, such as items that must be shipped by freight. Sellers can choose to offer eBay Plus by default in every qualified listing, or in none. In either case, participating sellers can decide to offer or not offer eBay Plus in any qualified listing on a case-by-case basis.

To offer eBay Plus in an item listing, sellers must:

When a seller offers eBay Plus for an item, qualified buyers who have enrolled in the program will see the eBay Plus shipping option.

For more information, see Offering eBay Plus.

Retrieving Digital Gift Card Order Details

New containers and fields are returned in OrderReport.

The DigitalDeliverySelected container consists of information related to the digital gift card order line item, including the delivery method, delivery status, and recipient of the gift card (either the buyer, or another individual that is receiving the gift card as a gift from the buyer). The seller will need to look at the DeliveryDetails.Recipient container to identify the recipient of the digital gift card. The recipient will either be the buyer, or it can be another individual if the buyer purchased the gift card for someone else. The seller will then email (currently, the only supported digital delivery method) the digital gift card to the recipient to fulfill the order.

Other returned digital gift card elements include the following:

Changed Functionality - 933

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 - 933

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

None for this release.

Version 931

Index of Changed Calls - 931

Schema Changes - 931

Announcements - 931

New Features - 931

Changed Functionality - 931

Documentation Changes and Errata - 931

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

Index of Changed Calls - 931

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 - 931

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 - 931

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 - 931

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

None for this release.

Changed Functionality - 931

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 - 931

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

None for this release.

Version 929

Index of Changed Calls - 929

Schema Changes - 929

Announcements - 929

New Features - 929

Changed Functionality - 929

Documentation Changes and Errata - 929

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

Index of Changed Calls - 929

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 - 929

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 - 929

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 - 929

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

None for this release.

Changed Functionality - 929

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 - 929

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

None for this release.

Version 927

Index of Changed Calls - 927

Schema Changes - 927

Announcements - 927

New Features - 927

Changed Functionality - 927

Documentation Changes and Errata - 927

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

Index of Changed Calls - 927

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 - 927

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 - 927

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 - 927

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

None for this release.

Changed Functionality - 927

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 - 927

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

None for this release.

Version 925

Index of Changed Calls - 925

Schema Changes - 925

Announcements - 925

New Features - 925

Changed Functionality - 925

Documentation Changes and Errata - 925

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

Index of Changed Calls - 925

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 - 925

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 - 925

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 - 925

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

None for this release.

Changed Functionality - 925

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 - 925

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

None for this release.

Version 923

Index of Changed Calls - 923

Schema Changes - 923

Announcements - 923

New Features - 923

Changed Functionality - 923

Documentation Changes and Errata - 923

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

Index of Changed Calls - 923

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 - 923

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 - 923

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 - 923

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

None for this release.

Changed Functionality - 923

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 - 923

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

None for this release.

Version 921

Index of Changed Calls - 921

Schema Changes - 921

Announcements - 921

New Features - 921

Changed Functionality - 921

Documentation Changes and Errata - 921

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

Index of Changed Calls - 921

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 - 921

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 - 921

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.

Recommending, then Requiring Product IDs for Some Categories

Sellers on the US, UK, Germany, and Australia sites will start getting notified at listing time when including a product identifier will enhance the new item listing by giving the listing greater visibility in searches, give the listing priority placement in eBay deals and other promotions, and the listing will automatically pick up robust listing information, including required and recommended item specifics. Beginning in late June, product identifiers will start being required in specific categories. For more information on recommended and required product identifiers, including some of the affected categories, see the 2015 Spring Seller Update page.

Several Product Identifier Fields Being Deprecated in Version 923

The GTIN and ListIfNoProduct fields used in the Add/Revise/Relist/Verify listing calls will be deprecated with Version 923. The GTIN field will no longer be available to sellers to specify a generic GTIN (Global Trade Identification Number). Instead, the sellers must use the EAN, ISBN, or UPC fields in the ProductListingDetails container (for single-variation listings) or the new VariationProductListingDetails container (for multiple-variation listings). The ListIfNoProduct boolean field will no longer be used to block the listing if no product match is found in the eBay catalog. When using the ProductListingDetails container to identify and match the product to a product in the eBay catalog, the API call will create a listing regardless of whether a product match is found or not.

For single-variation listings, product IDs (Brand/MPN, EAN, GTIN, ISBN, UPC) are specified in the ProductListingDetails container. For multiple-variation listings, product IDs are specified through a Variation.VariationSpecifics container. For multiple-variation listings, the same type of product ID must be used for all variations in the listing.

New Features - 921

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

GetCategoryFeatures Enhancement to Discover if a Category Supports/Requires Product IDs

To support the product identifier requirement (in some categories) that begins in late June, the Trading API's GetCategoryFeatures call has been enhanced to discover if a specific category supports or requires (requirement won't start until late June). It is recommended that a seller always specify a product ID (EAN, ISBN, UPC, Brand/MPN) if one is available for the product and the category supports product identifiers. Among other benefits, it can improve search results on eBay and on other search engines, and it is a shortcut to creating a listing with robust listing information, including relative and helpful item specifics.

To see if a specific category supports or requires product identifiers, use the GetCategoryFeatures call with the following parameter options:

After a successful call, look for the EANEnabled, ISBNEnabled, and UPCEnabled fields under the Category node. The values of each of these fields will either be 'Disabled', 'Enabled', or 'Required'. 'Disabled' indicates that particular product identifier type cannot be used in that category, 'Enabled' indicates that the product identifier type can be used for that category, and 'Required' indicates that the product identifier type is required when listing an item in that category. The value returned in the Category.BrandMPNIdentifierEnabled field is boolean, with 'true' indicating that a brand/MPN pair can be used to identify a product, and 'false' indicating that a brand/MPN pair cannot be used to identify a product.

Product Identifiers Added at the Variation Level

New VariationProductListingDetails container added to fixed-price listing calls to allow sellers to identify and match product variations to products in the eBay catalog. This change is only applicable to multiple-variation listings. An EAN, ISBN, and/or UPC value for each variation are specified in the new Variation.VariationProductListingDetails container. If using brand and MPN (manufacturer part number) values to identify each product variation, the brand name is specified at the item level in the ItemSpecifics.NameValueList container, and the MPN for each product variation is specified at the variation level in the VariationSpecifics.NameValueList container.

Unlike single-variation listings, using product identifiers to create a multiple-variation listing does not have the added benefit of item title, item description, product images, and item specifics being automatically picked up in the listing. So, the seller must manually add these fields along with the product identifiers.

Other Notes on Multiple-Variation Listings

Changed Functionality - 921

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.

Passing in Generic Text to Product Identifier Fields

Once the product identifier requirement (in some categories) begins in late June, eBay will expect EAN, ISBN, UPC, and/or Brand/MPN values in the corresponding fields if the listing category requires product identifiers. In some cases, a product identifier might not exist for a product. If this is the case, the seller must pass in specific, generic text into the corresponding field. This text can be retrieved with the GeteBayDetails call by including the DetailName field in the call request and setting its value to 'ProductDetails'. The ProductDetails.ProductIdentifierUnavailableText field that is returned in the response will contain the actual text that should be passed into the relevant product identification fields when creating a listing. This text can vary by site.

Maximum Length for Brand and MPN Values Decreased

If a Brand/MPN pair is used in the ProductListingDetails, ItemSpecifics, or VariationSpecifics containers to identify and match and product to a product in the eBay catalog, the length of these values cannot exceed 65 characters or the listing will fail.

Documentation Changes and Errata - 921

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

None for this release.

Version 919

Index of Changed Calls - 919

Schema Changes - 919

Announcements - 919

New Features - 919

Changed Functionality - 919

Documentation Changes and Errata - 919

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

Index of Changed Calls - 919

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 - 919

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 - 919

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 - 919

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

None for this release.

Changed Functionality - 919

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 - 919

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

None for this release.

Version 917

Index of Changed Calls - 917

Schema Changes - 917

Announcements - 917

New Features - 917

Changed Functionality - 917

Documentation Changes and Errata - 917

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

Index of Changed Calls - 917

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 - 917

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 - 917

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.

Four Listing Recommendation Types Disabled

The Category, ConditionDescription, GSP, and UPC listing recommendation types have been disabled in the Trading API and will no longer be returned in the Add/Revise/Relist/Verify calls.

Coming Soon: Recommending, then Requiring Product IDs for Some Categories

Beginning in June, sellers will be notified at listing time when including a Product ID will enhance the listing by giving the listing greater visibility in searches, give the listing priority placement in eBay deals and other promotions, and the listing will automatically pick up robust listing information, including required and recommended item specifics. And starting later in 2015, Product IDs will start being required in specific categories.

Product ID recommendations (and later, Product ID requirements) will only be applicable to branded items in 'New' condition. This change will affect the following eBay categories:

For single-variation listings, product IDs (Brand/MPN, EAN, GTIN, ISBN, UPC) are specified in the ProductListingDetails container. For multiple-variation listings, product IDs are specified through a Variation.VariationSpecifics container. For multiple-variation listings, the same type of product ID must be used for all variations in the listing.

New Features - 917

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

None for this release.

New Fast 'N Free Listing Recommendation Type Available

The Fast 'N Free listing recommendation type is now enabled in the Trading API. This listing recommendation type will advise sellers to offer expedited shipping (same-day shipping or 1-day handling) and/or a free shipping service option. Listings that offer both fast and free shipping options get the "Fast 'N Free" badge, which can increase sales. This recommendation type is supported by the US, UK, Germany, Australia, France, Italy, and Spain sites.

The two different Fast 'N Free recommendations are summarized below:

All Listing Recommendation types are supported by the following calls:

Changed Functionality - 917

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 - 917

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

None for this release.

Copyright © 2009–2014 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.