This archive document contains information about releases that go back longer than four quarters ago. For more recent releases, see the current Release Notes.
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 2009 | Q4 2008 | Q3 2008 | Q2 2008 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Version | Release Date | Version | Release Date | Version | Release Date | Version | Release Date | ||||
| 609 | 2009-3-18 | 597 | Not Released | 583 | 2008-9-17 | 571 | 2008-6-25 | ||||
| 607 | 2009-3-4 | 595 | 2008-12-10 | 581 | 2008-9-3 | 569 | 2008-6-11 | ||||
| 605 | 2009-2-18 | 593 | Not Released | 579 | 2008-8-20 | 567 | 2008-5-28 | ||||
| 603 | 2009-2-4 | 591 | 2008-11-12 | 577 | 2008-8-6 | 565 | 2008-5-14 | ||||
| 601 | 2009-1-21 | 589 | 2007-10-29 | 575 | 2008-7-23 | 563 | 2008-4-30 | ||||
| 599 | 2009-1-7 | 587 | 2008-10-15 | 573 | 2008-7-9 | 561 | 2008-4-16 | ||||
| 585 | 2008-10-3 | 559 | 2008-4-2 | ||||||||
These releases go back longer than four quarters ago. For more recent releases, see the current Release Notes.
Documentation Changes and Errata - 609
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
NameRecommendationType |
Complex type | New |
NameValueRelationshipType |
Complex type | New |
RecommendationValidationRulesType |
Complex type | New |
RecommendationsType |
Complex type | New |
ValueRecommendationType |
Complex type | New |
ValueTypeCodeType |
Enumerated type | New |
GetCategorySpecificsRequestType.CategorySpecific |
Element | New |
GetCategorySpecificsRequestType.ExcludeRelationships |
Element | New |
GetCategorySpecificsRequestType.IncludeConfidence |
Element | New |
GetCategorySpecificsResponseType.Recommendations |
Element | New |
GetRecommendationsRequestContainerType.ExcludeRelationships |
Element | New |
GetRecommendationsRequestContainerType.IncludeConfidence |
Element | New |
GetRecommendationsResponseContainerType.ProductListingDetails |
Element | New |
GetRecommendationsResponseContainerType.Recommendations |
Element | New |
GetRecommendationsResponseContainerType.Title |
Element | New |
ProductListingDetailsType.DetailsURL |
Element | New |
ProductListingDetailsType.ProductDetailsURL |
Element | New |
ProductListingDetailsType.ProductReferenceID |
Element | New |
SelectionModeCodeType.FreeText |
Enum | New |
SelectionModeCodeType.Prefilled |
Enum | New |
SelectionModeCodeType.SelectionOnly |
Enum | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 609.
Starting in 2009, some categories that support ID-based Attributes may be converted to support custom Item Specifics instead. Use GetCategoryFeatures to determine which categories support the custom Item Specifics format (see ItemSpecificsEnabled).
Keep an eye on the eBay Developers Program newsletter and blog for details about category changes.
This release note entry describes the anticipated API behavior after a category has been converted from Attributes to custom Item Specifics. More details and examples will be provided in a future release.
To maintain backward compatibility, and to give you more time to migrate your listing templates, you can still pass Item.AttributeSetArray in AddItem, ReviseItem, RelistItem, and VerifyAddItem even after a category has been converted to custom Item Specifics. In these cases, eBay automatically moves the relevant Attribute data into the Item.ItemSpecifics node on your behalf when we receive your request.
| Note: When a category still supports ID-based attributes (i.e., it hasn't been converted), there is no change to AddItem and related calls, no mapping occurs, and there is no need to change listing templates. |
To support catalog and historical Attribute details, GetCategory2CS, GetAttributesCS, and GetProductSellingPages may continue to indicate that categories are Attribute-enabled even after they have been converted. If this occurs, you can assume the settings in GetCategoryFeatures take precedence over the settings in GetCategory2CS when you are choosing how to specify Item Specifics in listing requests.
You use the usual catalog product search process (GetProductSearchResults, etc.) for converted categories. However, if you list with Item.ProductListingDetails or Item.ExternalProductID, and the category supports custom Item Specifics, then GetItem returns the product Item Specifics in Item.ItemSpecifics instead of Item.AttributeSetArray.
If you use GetItem to read Item Specifics data, it is a good idea to check for both Item.ItemSpecifics and Item.AttributeSetArray in the response.
Note: The way GetItem returns Item Specifics depends on whether the category currently supports ID-based Attributes or custom Item Specifics:
|
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.
When you specify version 609 or higher in a GetCategorySpecifics request, the response returns Recommendations (a new node) instead of CategoryItemSpecifics.
Recommendations includes relevant Item Specific names and values (if any). In addition, it includes listing rules, such as whether you can specify more than one value for a name in listing requests. It also may include relationships (if any) between Item Specifics (e.g., City usually only makes sense when State is also specified). In 2009, you might only start seeing relationship details after certain categories are converted from ID-based Attributes to custom Item Specifics.
In addition, you can iteratively pass in Item Specific names and values to refine and improve the precision of the recommendations.
When you specify version 609 or higher in a GetItemRecommendations request, and you use the Item Specifics recommendation engine, the response returns Recommendations (a new node) instead of ItemSpecificsRecommendations.
Recommendations includes relevant Item Specific names and values (if any). In addition, it includes listing rules, such as whether you can specify more than one value for a name in listing requests. It also may include relationships (if any) between Item Specifics (e.g., City usually only makes sense when State is also specified). In 2009, you might only start seeing relationship details after certain categories are converted from ID-based Attributes to custom Item Specifics.
In addition, you can iteratively pass in Item Specific names and values to refine and improve the precision of the recommendations.
With request version 609 and higher, you can also use GetItemRecommendations instead of GetProductSellingPages to render product details for categories that support custom Item Specifics. If you pass a product ID in the GetItemRecommendations request (by using Item.ProductListingDetails or Item.ExternalProductID), and you use the Item Specifics recommendation engine, then Recommendations includes the product's Item Specifics (marked as prefilled) in addition to the custom Item Specific recommendations (if any). In addition, the response includes a Title recommendation (based on the product title), and ProductListingDetails with other details from the catalog.
In preparation for Picture Manager retirement in late 2009, new subscriptions and subscription upgrades have been disabled as of this release. UploadSiteHostedPictures has new functionality which will allow a user to retrieve a picture from a URL on an external Web server. Once retrieved, the picture will be copied to eBay Picture Services (EPS).
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 609 and Changed Functionality - 609.
None for this release.
Documentation Changes and Errata - 607
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
AddSellingManagerTemplateRequestType.SellingManagerDetails |
Entity | Removed |
GetSellingManagerTemplatesRequestType.IncludeCrossPromotion |
Entity | Removed |
SellingManagerDetailsType |
Entity | Removed |
AddSellingManagerTemplateRequestType.ProductID |
Element | New |
AddSellingManagerTemplateRequestType.SaleTemplateName |
Element | New |
ShippingServiceCodeType.DE_DHLPaeckchenPackstation |
Enum | New |
ShippingServiceCodeType.DE_DHLPaketPackstation |
Enum | New |
ShippingServiceCodeType.DE_DHLStarPaeckchen |
Enum | New |
ShippingServiceCodeType.DE_HermesPaketShop2Shop |
Enum | New |
ShippingServiceCodeType.DE_HermesPaketShop2ShopKaeufer |
Enum | New |
ShippingServiceCodeType.DE_eBayDHLPaeckchen |
Enum | New |
ShippingServiceCodeType.DE_eBayHermesPaketShop2Shop |
Enum | New |
ShippingServiceCodeType.DE_eBayHermesPaketShop2ShopKaeufer |
Enum | New |
ShippingServiceCodeType.UK_OtherCourier3Days |
Enum | New |
ShippingServiceCodeType.UK_OtherCourier5Days |
Enum | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 607.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
Several new shipping services have been added, including two new USPS services for a small, flat- rate box (added in release 605), and new UK and DE shipping services.
See Schema Changes for a list of new UK and DE shipping services added in this release.
A couple unused schema elements and a related type have been removed from Selling Manager calls. These calls were made available for Open eBay participants building applications related to Selling Manager only. The affected calls, AddSellingManagerTemplate and GetSellingManagerTemplates, are unsupported for general use.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 607 and Changed Functionality - 607.
None for this release.
Documentation Changes and Errata - 605
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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.
AddLiveAuctionItemRequestType |
Entity | Removed |
AddLiveAuctionItemResponseType |
Entity | Removed |
ApproveLiveAuctionBiddersRequestType |
Entity | Removed |
ApproveLiveAuctionBiddersResponseType |
Entity | Removed |
BidApprovalArrayType.LiveAuctionBid |
Entity | Removed |
BidderDetailType.LiveAuctionBidResult |
Entity | Removed |
GetLiveAuctionBiddersRequestType |
Entity | Removed |
GetLiveAuctionBiddersResponseType |
Entity | Removed |
GetLiveAuctionCatalogDetailsRequestType |
Entity | Removed |
GetLiveAuctionCatalogDetailsResponseType |
Entity | Removed |
ItemType.LiveAuctionDetails |
Entity | Removed |
ItemType.NowAndNew |
Entity | Removed |
LiveAuctionApprovalStatusArrayType |
Entity | Removed |
LiveAuctionApprovalStatusType |
Entity | Removed |
LiveAuctionBidArrayType |
Entity | Removed |
LiveAuctionBidType |
Entity | Removed |
LiveAuctionCatalogType |
Entity | Removed |
LiveAuctionDetailsType |
Entity | Removed |
ReviseLiveAuctionItemRequestType |
Entity | Removed |
ReviseLiveAuctionItemResponseType |
Entity | Removed |
SellerType.LiveAuctionAuthorized |
Entity | Removed |
FeedbackTypeCodeType |
Enumerated type | New |
FeeType.DiscountedFee |
Element | New |
FeeType.RelatedDiscountedFeeName |
Element | New |
GetFeedbackRequestType.FeedbackType |
Element | New |
GetMyeBayBuyingRequestType.BuyingSummary |
Element | New |
GetMyeBaySellingRequestType.SellingSummary |
Element | New |
TransactionType.BuyerCheckoutMessage |
Element | New |
UploadSiteHostedPicturesRequestType.ExternalPictureURL |
Element | New |
UserType.BillingEmail |
Element | New |
BuyerSatisfactionStatusCodeType.Excellent |
Enum | New |
BuyerSatisfactionStatusCodeType.VeryPoor |
Enum | New |
DisputeRecordTypeCodeType.HalfDispute |
Enum | New |
ShippingServiceCodeType.USPSPriorityMailInternationalSmallFlatRateBox |
Enum | New |
ShippingServiceCodeType.USPSPriorityMailSmallFlatRateBox |
Enum | New |
eBay is no longer offering eBay Live Auctions. All Live Auction API functionality has been retired as of this release.
As previously announced, Now & New (Sofort & Neu) has been retired as of this release. This retirement includes the deprecation of Now & New enums for search in GetSearchResults and GetMyeBayBuying.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 605.
Previously, the only way to retrieve comments left by buyers during checkout was via the UI or
an email. This was often a tedious process that could cause shipping delays. Now the Transaction
container in the responses for GetItemTransactions and GetSellerTransactions includes a
BuyerCheckoutMessage field.
When a user has their billing option set to 'email', they can include the new BillingEmail element in a GetUser request to retrieve their own email bills.
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.
You can now retrieve feedback that you received as a buyer, feedback you received as a seller, or feedback you left for others (as either a buyer or a seller). Specify FeedbackReceivedAsSeller, FeedbackReceivedAsBuyer, FeedbackLeft, or use the default option of FeedbackReceived, with the GetFeedback call to use these new options.
With this release, you no longer need to include ItemID in an AddMemberMessageRTQ request, if the request includes a RecipientID in the MemberMessage container.
Example:
<?xml version="1.0" encoding="utf-8"?>
<AddMemberMessageRTQRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<ItemID>190001385789</ItemID--> <-- No longer required
<MemberMessage>
<Body>This should contain the answer to a question that
an eBay user asks you (the seller) about an active listing.</Body>
<ParentMessageID>5140381</ParentMessageID>
<RecipientID>braggybuyer@yahoo.com</RecipientID> <-- if this tag is present
</MemberMessage>
<RequesterCredentials>
<eBayAuthToken>ABC...123</eBayAuthToken>
</RequesterCredentials>
</AddMemberMessageRTQRequest>
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 605 and Changed Functionality - 605.
Documentation incorrectly stated that PaidTime would be the transaction time if the seller was not a Selling Manager Pro user. This statement was removed.
Documentation Changes and Errata - 603
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
IntegratedMerchantCreditCardInfoType |
Complex type | Reserved for future use |
CheckoutStatusType.IntegratedMerchantCreditCardEnabled |
Element | Reserved for future use |
ItemType.IntegratedMerchantCreditCardEnabled |
Element | Reserved for future use |
OrderType.IntegratedMerchantCreditCardEnabled |
Element | Reserved for future use |
SellerType.IntegratedMerchantCreditCardInfo |
Element | Reserved for future use |
SellingManagerOrderStatusType.IntegratedMerchantCreditCardEnabled |
Element | Reserved for future use |
TransactionStatusType.IntegratedMerchantCreditCardEnabled |
Element | Reserved for future use |
BuyerPaymentMethodCodeType.IntegratedMerchantCreditCard |
Enum | Reserved for future use |
BuyerPaymentMethodCodeType.Moneybookers |
Enum | New |
BuyerPaymentMethodCodeType.Paymate |
Enum | New |
As announced, eBay will retire Now & New (Sofort & Neu) by March 2009. This retirement includes the deprecation of Now & New enums for search in GetSearchResults and GetMyeBayBuying.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 603.
Schema changes have been done for the Integrated Merchant Credit Card feature in preparation for Payflow registration becoming available to users as of the end of February 2009. Please see upcoming release notes for more details on the functionality and availability of this feature.
On the US site, you can list items with the Paymate and Moneybookers payment methods. These payment methods, which have been added to BuyerPaymentMethodCodeType, also are available in the Parts and Accessories category of the US eBay Motors site.
For more information about Paymate and Moneybookers, see this announcement.
The Trading API now includes support for eBay Motors fee changes, that are designed to draw new sellers into the vehicles market. These changes are back-end calculation adjustments that do not affect existing API calls or behavior.
The new pricing includes no Insertion Fees for the first 4 vehicles sold within a 12-month period. For five or more vehicle listings in one year, an Insertion Fee applies, but the Successful Listing Fees are lower. You can see the fee structure in the eBay Motors online help.
Every year at the seller's anniversay date (the date of the seller's first vehicle listing after September 2, 2008), the Insertion Fee will return to zero and the Successful Listing fee will be slightly higher.
Note that the Trading API does not include a specific call to find out if you have sold more than four vehicles, but you can use existing calls, such as GetMyeBaySelling to see your sales information.
Note also that re-listing a vehicle does not increase your total vehicle count.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
The new item sorting enumeration values, HighestPricedPlusShipping and LowestPricedPlusShipping, which were enabled for the US site in the 601 release are now available to UK (3), CA (2), and CAFR (210) sites. These sorting values should be made available to all eBay sites by the end of February 2009.
For more information, see the Sorting Items by Price Plus Shipping Cost Supported for eBay Stores entry in the 601 release notes.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 603 and Changed Functionality - 603.
CompleteSale supports orders, so there is no need for you to call CompleteSale repeatedly for each transaction, as previously stated in CompleteSale documentation.
Documentation Changes and Errata - 601
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
TransactionPlatformType |
Entity | Removed |
TransactionType.TransactionPlatform |
Entity | Removed |
ListingStartPriceDetailsType |
Complex type | New |
GeteBayDetailsResponseType.ListingStartPriceDetails |
Element | New |
DetailNameCodeType.ListingStartPriceDetails |
Enum | New |
NotificationEventTypeCodeType.ItemMarkedPaid |
Enum | New |
NotificationEventTypeCodeType.ItemMarkedShipped |
Enum | New |
As announced, eBay will retire Now & New (Sofort & Neu) by March 2009. This retirement includes the deprecation of Now & New enums for search in GetSearchResults and GetMyeBayBuying.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 601.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
Buy It Now can now be used for Adult Only listings. Thus, sellers can list Adult Only items in Buy It Now, Fixed Price and Store Inventory Format listings. Restrictions limiting the number of pictures have been removed.
Please see the Adult Only policy for complete information on listing in Adult Only categories: Adult Only Category Policy
This affects the AddItem family of calls.
The search results returned by GetSearchResults when Order is set to BestMatchSort now match eBay site search results sorted by Best Match. Similarly, results returned by GetCategoryListings when OrderBy is set to BestMatchSort now match eBay site results when browsing a category sorted by Best Match. Best Match sorting is the default setting for both the API and the site.
Two new item sorting enumeration values, HighestPricedPlusShipping and LowestPricedPlusShipping, have been enabled for specifying the default sort order for displaying store items. Store owners can use these new values with Store.ItemListSortOrder in SetStore to specify the default order for displaying their store items. Buyers can use SellerFavoriteItemPreferences.SearchSortOrder in SetUserPreferences to specify the default order items are displayed in the favorite seller email marketing they receive.
These values were added to the schema in the 589 release, but were disabled until now. These values are enabled for the US site only, initially, but will be available for eBay Stores on all eBay sites soon.
Sellers are now allowed to remove a number of listing enhancements with ReviseItem. This applies to fixed-price listings with Good Til Cancelled (GTC) durations only. This funtionality is available on the following sites only: AT (16), CA (2), CAFR (210), CH (193), DE (77), IE (205), IT (101), and UK (3).
When the seller removes the listing feature, the listing will immediately lose the search benefits associated with the feature. Seller do not get a full or partial refund (GTC renewal/billing is monthly). However, if the seller adds the feature back sometime after it was removed, but before the item renews for GTC, there is no additional charge. If the listing does not have the feature on it when the GTC listing is renewed (moves into the next billing period), then the seller will not get charged for it at that time. If the seller decides to add the feature after the listing has renewed, then seller is billed at the price for that feature as it pertains to that 30 day listing period.
If the seller removes a feature that is part of a bundle, and the seller had currently opted for the bundle, the bundle option is removed. No refund is given for the bundle, but if the seller opts for the bundle again before GTC renewal, then they will not be charged for it a second time.
For Featured First, note the differences due to the durations associated with the feature:
TransactionPlatformType and the TransactionPlatform field in TransactionType are being discontinued as of this release. If you were expecting to use the TransactionType.TransactionPlaform in your code, use TransactionType.Plaform instead.
You can now retrieve the minimum starting price for each listing type (such as 'Chinese', 'Dutch', 'AdType', 'FixedPriceItem', and others), using GeteBayDetails.ListingStartPriceDetails.
You can now receive ItemMarkedPaid and ItemMarkedShipped Platform Notifications when a seller sends a CompleteSaleRequest call with the 'Shipped' and 'Paid' elements set as 'true'.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 601 and Changed Functionality - 601.
The Trading API Guide contains preview information for calls related to Selling Manager and Selling Manager Pro. For more information about these calls, see Preview of Calls Related to Selling Manager and Selling Manager Pro.
Documentation Changes and Errata - 599
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No schema changes in this release.
The following Picture Manager calls will be deprecated by late 2009: GetPictureManagerDetails, GetPictureManagerOptions, and SetPictureManagerDetails.
As announced, eBay will retire Now & New (Sofort & Neu) by March 2009.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 599.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 599 and Changed Functionality - 599.
The following documentation sections have been modified to fix errors or clarify information:
No 597 schema was released.
No new calls in this release.
No changed calls in this release.
Documentation Changes and Errata - 595
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
ItemType.InventoryTrackingMethod |
Element | New |
As announced, starting December 31, 2008, eBay will no longer offer eBay Live Auctions. The corresponding functionality in the API also will be retired.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 595.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 595 and Changed Functionality - 595.
For additions to the Trading API Guide regarding affiliate commissions through use of PlaceOffer, please see the PlaceOffer Policies and Guidelines.
No 593 schema was released.
No new calls in this release.
No changed calls in this release.
Documentation Changes and Errata - 591
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
No schema changes in this release.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 591.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
Updated Nov. 26: As recently announced in the eBay Developers Program blog, eBay's Large Merchant APIs are now in Beta. Large Merchant Services offer a powerful new way to list and manage items in bulk. These APIs can save developers processing power and bandwidth, and allow sellers to react quickly to marketplace dynamics.
The Trading API can be used in conjunction with eBay's Large Merchant Services (LMS) to complete your large merchant solution. The Merchant Data API (in LMS) defines two requests for creating new listings: AddFixedPriceItem and RelistFixedPriceItem. When you create a listing with these requests, you can optionally use an InventoryTrackingMethod field to choose whether you prefer to track the listing by item ID or by your own unique SKU. If you track by SKU, it means you can pass your SKU instead of the item ID in subsequent Merchant Data API requests, such as ReviseFixedPriceItem, and in several Trading API calls. The Trading API's AddItem and RelistItem calls do not offer the inventory tracking preference. However, you can use GetItem, GetSellerList, GetSellerTransactions, and other Trading API calls to retrieve data about these listings and transactions. ReviseInventoryStatus also supports tracking listings by SKU.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 591 and Changed Functionality - 591.
None for this release.
Documentation Changes and Errata - 589
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
ShippingPackageDetailsType.Default |
Entity | Removed |
AddItemFromSellingManagerTemplateRequestType |
Complex type | New |
AddItemFromSellingManagerTemplateResponseType |
Complex type | New |
AddSellingManagerInventoryFolderRequestType |
Complex type | New |
AddSellingManagerInventoryFolderResponseType |
Complex type | New |
AddSellingManagerProductRequestType |
Complex type | New |
AddSellingManagerProductResponseType |
Complex type | New |
AddSellingManagerTemplateRequestType |
Complex type | New |
AddSellingManagerTemplateResponseType |
Complex type | New |
DeleteSellingManagerInventoryFolderRequestType |
Complex type | New |
DeleteSellingManagerInventoryFolderResponseType |
Complex type | New |
DeleteSellingManagerItemAutomationRuleRequestType |
Complex type | New |
DeleteSellingManagerItemAutomationRuleResponseType |
Complex type | New |
DeleteSellingManagerProductRequestType |
Complex type | New |
DeleteSellingManagerProductResponseType |
Complex type | New |
DeleteSellingManagerTemplateAutomationRuleRequestType |
Complex type | New |
DeleteSellingManagerTemplateAutomationRuleResponseType |
Complex type | New |
DeleteSellingManagerTemplateRequestType |
Complex type | New |
DeleteSellingManagerTemplateResponseType |
Complex type | New |
GetSellingManagerAlertsRequestType |
Complex type | New |
GetSellingManagerAlertsResponseType |
Complex type | New |
GetSellingManagerEmailLogRequestType |
Complex type | New |
GetSellingManagerEmailLogResponseType |
Complex type | New |
GetSellingManagerInventoryFolderRequestType |
Complex type | New |
GetSellingManagerInventoryFolderResponseType |
Complex type | New |
GetSellingManagerInventoryRequestType |
Complex type | New |
GetSellingManagerInventoryResponseType |
Complex type | New |
GetSellingManagerItemAutomationRuleRequestType |
Complex type | New |
GetSellingManagerItemAutomationRuleResponseType |
Complex type | New |
GetSellingManagerSaleRecordRequestType |
Complex type | New |
GetSellingManagerSaleRecordResponseType |
Complex type | New |
GetSellingManagerSoldListingsRequestType |
Complex type | New |
GetSellingManagerSoldListingsResponseType |
Complex type | New |
GetSellingManagerTemplateAutomationRuleRequestType |
Complex type | New |
GetSellingManagerTemplateAutomationRuleResponseType |
Complex type | New |
GetSellingManagerTemplatesRequestType |
Complex type | New |
GetSellingManagerTemplatesResponseType |
Complex type | New |
InventoryStatusType |
Complex type | New |
MoveSellingManagerInventoryFolderRequestType |
Complex type | New |
MoveSellingManagerInventoryFolderResponseType |
Complex type | New |
ReviseInventoryStatusRequestType |
Complex type | New |
ReviseInventoryStatusResponseType |
Complex type | New |
ReviseSellingManagerInventoryFolderRequestType |
Complex type | New |
ReviseSellingManagerInventoryFolderResponseType |
Complex type | New |
ReviseSellingManagerProductRequestType |
Complex type | New |
ReviseSellingManagerProductResponseType |
Complex type | New |
ReviseSellingManagerSaleRecordRequestType |
Complex type | New |
ReviseSellingManagerSaleRecordResponseType |
Complex type | New |
ReviseSellingManagerTemplateRequestType |
Complex type | New |
ReviseSellingManagerTemplateResponseType |
Complex type | New |
SaveItemToSellingManagerTemplateRequestType |
Complex type | New |
SaveItemToSellingManagerTemplateResponseType |
Complex type | New |
SellingManagerAlertType |
Complex type | New |
SellingManagerAutoListAccordingToScheduleType |
Complex type | New |
SellingManagerAutoListMinActiveItemsType |
Complex type | New |
SellingManagerAutoListType |
Complex type | New |
SellingManagerAutoRelistType |
Complex type | New |
SellingManagerAutoSecondChanceOfferType |
Complex type | New |
SellingManagerDetailsType |
Complex type | New |
SellingManagerEmailLogType |
Complex type | New |
SellingManagerFolderDetailsType |
Complex type | New |
SellingManagerOrderStatusType |
Complex type | New |
SellingManagerProductInventoryStatusType |
Complex type | New |
SellingManagerProductType |
Complex type | New |
SellingManagerSearchType |
Complex type | New |
SellingManagerSoldOrderType |
Complex type | New |
SellingManagerSoldTransactionType |
Complex type | New |
SellingManagerTemplateDetailsArrayType |
Complex type | New |
SellingManagerTemplateDetailsType |
Complex type | New |
SellingManagerVendorDetailsType |
Complex type | New |
SetSellingManagerItemAutomationRuleRequestType |
Complex type | New |
SetSellingManagerItemAutomationRuleResponseType |
Complex type | New |
SetSellingManagerTemplateAutomationRuleRequestType |
Complex type | New |
SetSellingManagerTemplateAutomationRuleResponseType |
Complex type | New |
TimeRangeType |
Complex type | New |
VATRateType |
Complex type | New |
DayOfWeekCodeType |
Enumerated type | New |
SellingManagerAlertTypeCodeType |
Enumerated type | New |
SellingManagerAutoRelistOptionCodeType |
Enumerated type | New |
SellingManagerAutoRelistTypeCodeType |
Enumerated type | New |
SellingManagerAutoSecondChanceOfferTypeCodeType |
Enumerated type | New |
SellingManagerAutomationPropertyTypeCodeType |
Enumerated type | New |
SellingManagerEmailSentStatusCodeType |
Enumerated type | New |
SellingManagerEmailTypeCodeType |
Enumerated type | New |
SellingManagerGeneralPropertyTypeCodeType |
Enumerated type | New |
SellingManagerInventoryPropertyTypeCodeType |
Enumerated type | New |
SellingManagerPaidStatusCodeType |
Enumerated type | New |
SellingManagerPaisaPayPropertyTypeCodeType |
Enumerated type | New |
SellingManagerProductSortCodeType |
Enumerated type | New |
SellingManagerSearchTypeCodeType |
Enumerated type | New |
SellingManagerShippedStatusCodeType |
Enumerated type | New |
SellingManagerSoldListingsPropertyTypeCodeType |
Enumerated type | New |
SellingManagerSoldListingsSortTypeCodeType |
Enumerated type | New |
UnpaidItemStatusTypeCodeType |
Enumerated type | New |
GetItemRequestType.SKU |
Element | New |
GetSellerTransactionsRequestType.InventoryTrackingMethod |
Element | New |
ItemTransactionIDType.SKU |
Element | New |
ItemType.PaymentAllowedSite |
Element | New |
SellingManagerProductDetailsType.FolderID |
Element | New |
SellingManagerProductDetailsType.Note |
Element | New |
SellingManagerProductDetailsType.RestockAlert |
Element | New |
SellingManagerProductDetailsType.RestockThreshold |
Element | New |
SellingManagerProductDetailsType.VendorInfo |
Element | New |
SendInvoiceRequestType.SKU |
Element | New |
ShippingPackageDetailsType.DefaultValue |
Element | New |
FeatureIDCodeType.IntangibleEnabled |
Enum | New |
NotificationEventTypeCodeType.BulkDataExchangeJobCompleted |
Enum | New |
StoreItemListSortOrderCodeType.HighestPricedPlusShipping |
Enum | New |
StoreItemListSortOrderCodeType.LowestPricedPlusShipping |
Enum | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 589.
This Trading API release contains a preview of calls related to Selling Manager and Selling Manager Pro. These calls will be available in 2009 for Open eBay participants who are building applications related to Selling Manager and Selling Manager Pro. For more information about Open eBay, please see http://developer.ebay.com/echo.
As stated in the description of each call in the Call Reference, these calls are unsupported and are currently available only to Open eBay pilot participants. These calls are subject to change without notice; the deprecation process is inapplicable to these calls.
For information about Selling Manager and Selling Manager Pro, please see http://pages.ebay.com/selling_manager_pro and http://pages.ebay.com/selling%5Fmanager.
More information about these calls will be provided in 2009. For the names of the new calls, please see the New Calls section, above.
The Item.PaymentAllowedSite field, which can be returned by GetItem, enables you to view the sites on which an item can be purchased, based on the payment methods offered for the item.
By March 2009, a Payflow account (obtainable in January 2009 in My eBay) will be required when sellers on the US site offer credit cards (Visa, MasterCard, American Express, and Discover).
For general information about specifying payment methods, see Payment Method Differences. For information on payment changes on the US site, see August Payments Policy Changes.
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.
When sellers first list fixed-price items, their search ranking is determined by seller qaulity (DSRs) and title relevance. Best Match search ranking also takes into account buyer activity. When items in a listing begin to sell, the Resent Sales History factors into search ranking. Items that sell the fastest are given a relative lift in search results.
Recent Sales history is tracked with a moving window to ensure it reflects the most recent activity. Due to the moving window, it is advantageous for sellers to maintain item availability for a GTC listing (that is, keep quanitity from dropping too low), or to relist as quickly as possible when an item ends (recent sales scores can be transferred to the relisted item). Refer to How the Moving Window Affects Recent Sales in the Developers Program Community Blog for more information.
ShippingPackageDetailsType.Default (returned by GeteBayDetails) was deprecated with version 589. DefaultValue is its replacement. The API returns only DefaultValue for versions greater than or equal to 589. The API returns both Default and DefaultValue for versions lower than 589. We recommend that you change your application to handle the return of DefaultValue.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 589 and Changed Functionality - 589.
In the Call Reference, the Item.PictureDetails.PictureURL field has been removed from the output of GetSearchResults, as a documentation correction.
Documentation Changes and Errata - 587
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
SellingManagerProductDetailsType.PartNumber |
Entity | Removed (unused by calls) |
SellingManagerProductDetailsType.ProductPartNumber |
Entity | Removed (unused by calls) |
ShippingPackageDetailsType.DimensionsSupported |
Element | New |
ShippingServiceDetailsType.ShippingServicePackageDetails |
Element | New |
ShippingServiceDetailsType.WeightRequired |
Element | New |
ShipmentDeliveryStatusCodeType.Error |
Enum | Reserved for future use |
ShipmentDeliveryStatusCodeType.Unconfirmed |
Enum | Reserved for future use |
ShipmentDeliveryStatusCodeType.Unknown |
Enum | Reserved for future use |
ShippingServiceCodeType.CA_PostExpeditedFlatRateBox |
Enum | New |
ShippingServiceCodeType.CA_PostExpeditedFlatRateBoxUSA |
Enum | New |
TransactionPlatformCodeType.WorldOfGood |
Enum | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 587.
WorldOfGood has been added as a TransactionPlatformCodeType value. It is returned by GetItemTransactions, GetMyeBayBuying, GetMyeBaySelling, GetOrderTransactions, and GetSellerTransactions.
If you are still using Item.AttributeSetArray instead of Item.ReturnPolicy to specify a return policy, you can now pass -10 in ValueID and ReturnsNotAccepted in ValueLiteral to specify "Returns Not Accepted" in AddItem. This value was available on the US site in early October. It should be available on international sites in late October. See the eBay Developer Newsletter and blog for updates on when sellers will be required to specify a return policy.
Please note that GetAttributesCS has not been updated to mirror the latest changes to the Return Policy fields that each site supports. For example, GetAttributesCS does not return the -10 value for "Returns Not Accepted", but AddItem does accept this value. GetAttributesCS also may show return policy attributes or values that are no longer applicable on some sites. If you pass inapplicable attributes or values in AddItem, they will be dropped, and a warning may be returned.
Featured First is a paid feature that sellers may purchase for individual listings to get a chance to increase exposure. It is currently available for the following sites: US (0 - not Motors), Canada (2), Canada (French) (210), UK (3), Ireland (205), Germany (77), Austria (16), Switzerland (193), and Italy (101). Featured First gives you an opportunity, but no guarantee, to have your listing appear on the first page of search results in the Featured Items section.
With Featured First:
See the Featured First online help page for more information.
As part of this change, Featured Plus now behaves slightly differently for browse functionality. When browsing, instead of all Featured Plus items being shown prior to any non-featured items, Featured Plus items are now shown in real time, at the top of the page they would normally show up on. The behavior for keyword searching has not changed.
See the Featured Plus online help page for more information.
The Featured First option is selected by specifying Featured in the PictureDetails.GalleryType field. The behavior of your listing within the search results is determined as follows:
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.
eBay has simplified (reduced) the list of package types for the shipping calculator. If a seller relists or revises an item with a deprecated package type, eBay will automatically map the deprecated package type to an appropriate active package type. Simplification of the package types only applies to the shipping calculator for the eBay US site and eBay Motors Parts and Accessories.
In the future, eBay will require sellers to provide package dimensions for the shipping calculator when it is used for large packages, irregular sized packages, and all the UPS air services for packages.
If a seller provides package dimensions for a service that does not require dimensions, eBay will use the dimensions to more accurately calculate shipping rates. We encourage sellers to provide package dimensions whenever possible so that shipping rates are more accurate for buyers. (If dimensions are omitted, eBay uses a set of default values for rate calculations.)
Developer impact
587:
In the future:
Affected calls: GeteBayDetails and the AddItem family of calls.
To learn about the shipping calculator, see GetItemShipping documentation.
The shipping mechanisms discussed in the 585 Release Notes will go into effect for eBay DE around November 4. eBay DE is currently the only site for which the GroupN style of elements apply.
See Schema Changes for a list of new shipping services.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 587 and Changed Functionality - 587.
None for this release.
Documentation Changes and Errata - 585
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
BuyerPaymentMethodCodeType.Moneybookers |
Entity | Removed |
BuyerPaymentMethodCodeType.allpay |
Entity | Removed |
AddItemRequestContainerType |
Complex type | New |
AddItemResponseContainerType |
Complex type | New |
AddItemsRequestType |
Complex type | New |
AddItemsResponseType |
Complex type | New |
EndItemRequestContainerType |
Complex type | New |
EndItemResponseContainerType |
Complex type | New |
EndItemsRequestType |
Complex type | New |
EndItemsResponseType |
Complex type | New |
Group1MaxFlatShippingCostDefinitionType |
Complex type | New |
Group2MaxFlatShippingCostDefinitionType |
Complex type | New |
Group3MaxFlatShippingCostDefinitionType |
Complex type | New |
MaxFlatShippingCostCBTExemptDefinitionType |
Complex type | New |
MaxFlatShippingCostDefinitionType |
Complex type | New |
PaymentMethodDefinitionType |
Complex type | New |
ShippingServicePackageDetailsType |
Complex type | New |
CostGroupFlatCodeType |
Enumerated type | New |
CategoryFeatureType.Group1MaxFlatShippingCost |
Element | New |
CategoryFeatureType.Group2MaxFlatShippingCost |
Element | New |
CategoryFeatureType.Group3MaxFlatShippingCost |
Element | New |
CategoryFeatureType.PaymentMethod |
Element | New |
FeatureDefinitionsType.Group1MaxFlatShippingCost |
Element | New |
FeatureDefinitionsType.Group2MaxFlatShippingCost |
Element | New |
FeatureDefinitionsType.Group3MaxFlatShippingCost |
Element | New |
FeatureDefinitionsType.MaxFlatShippingCost |
Element | New |
FeatureDefinitionsType.MaxFlatShippingCostCBTExempt |
Element | New |
FeatureDefinitionsType.PaymentMethod |
Element | New |
FeedbackDetailType.FeedbackRevised |
Element | New |
ShippingServiceDetailsType.CostGroupFlat |
Element | New |
SiteDefaultsType.Group1MaxFlatShippingCost |
Element | New |
SiteDefaultsType.Group2MaxFlatShippingCost |
Element | New |
SiteDefaultsType.Group3MaxFlatShippingCost |
Element | New |
SiteDefaultsType.PaymentMethod |
Element | New |
FeatureIDCodeType.Group1MaxFlatShippingCost |
Enum | New |
FeatureIDCodeType.Group2MaxFlatShippingCost |
Enum | New |
FeatureIDCodeType.Group3MaxFlatShippingCost |
Enum | New |
FeatureIDCodeType.MaxFlatShippingCost |
Enum | New |
FeatureIDCodeType.MaxFlatShippingCostCBTExempt |
Enum | New |
FeatureIDCodeType.PaymentMethods |
Enum | New |
ShippingServiceCodeType.CA_PriorityWorldwide |
Enum | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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.
As announced in Version 583, eBay is imposing limits on shipping costs for selected categories.
Starting October 8, this cost threshold applies to items listed on the eBay US site (regardless of whether shipping within or shipping into the US) for items in the Books, Movies & DVDs, Music, and Video Games categories. (Items listed on other sites yet shipped into the US are not limited by these thresholds.)
For details, see Maximum Flat Rate Shipping Cost in the Specifying Shipping Costs portion of the Shipping documentation. (If you read the Version 583 documentation, please note that there is no MaxFlatShippingCostEnabled element and that the *Cost elements may be returned in both the SiteDefaults and Category containers.)
Rollout schedule:
Affected calls: GetCategoryFeatures, GeteBayDetails, the AddItem family of calls.
Beginning in late October 2008, you can use ProPay as a payment method for listings on the US site. You also can use PayOnPickup for cases of cash on pickup.
For general information about specifying payment methods, see Payment Method Differences. For information on payment changes on the US site, see August Payments Policy Changes.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 585.
As previously announced, changes are occurring in the allowed payment methods for listings. Please use GetCategoryFeatures to determine the available payment methods for a site or category. For more information, see Payment Method Differences. Please also note that, as previously announced, you can use GetCategoryFeatures to determine if a listing must include PayPal as a payment method.
AddItems is a new batch listing call. It will list up to five(5) items per request.
EndItems is another new batch call. It will end up to ten(10) items early.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 585 and Changed Functionality - 585.
ShippedTime was added to ShipmentType on version 583. This was not mentioned in 583 release notes.
Documentation Changes and Errata - 583
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
InventoryTrackingMethodCodeType |
Enumerated type | New |
AbstractResponseType.ExternalUserData |
Element | New |
CategoryFeatureType.MaxFlatShippingCost |
Element | New |
NotificationUserDataType.ExternalUserData |
Element | New |
ShipmentType.ShippedTime |
Element | New |
SiteDefaultsType.MaxFlatShippingCost |
Element | New but deprecated (Do not use) |
SiteDefaultsType.MaxFlatShippingCostCBTExempt |
Element | New |
BuyerPaymentMethodCodeType.Moneybookers |
Enum | New |
BuyerPaymentMethodCodeType.PayOnPickup |
Enum | New |
BuyerPaymentMethodCodeType.ProPay |
Enum | New |
BuyerPaymentMethodCodeType.allpay |
Enum | New |
QuestionTypeCodeType.None |
Enum | New |
ShippingCarrierCodeType.Nacex |
Enum | New |
As previously announced, starting in September 2008, on the Australia site, sellers and bidders will be unable to retrieve each other's email addresses unless they are in a transactional relationship.
The Bid Assistant feature will be removed from the eBay site, and related API elements such as BidAssistantList and BidGroupArrayType that are used in the GetMyeBayBuying call, as well as BidGroupItemStatusCodeList, BidGroupItemType, BidGroupStatusCodeList, BidGroupType, and BidRangeType, will be decremented in the beginning of October.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 583.
"Total flat rate shipping cost" is the sum of the seller's base flat rate shipping charge and the cost of insurance (if insurance is required by the seller). Starting in October, there will be certain categories in which a listing with flat rate shipping can be created only if the total cost of shipping matches or is below the maximum shipping cost set by eBay for the category that the listing is in.
This cost threshold will initially apply only to items listed on the eBay US site (regardless of whether shipping within or shipping into the US) for items in the Books, Movies & DVDs, Music, and Video Games categories. (Items listed on other sites yet shipped into the US are not limited by these thresholds.)
You can start learning about the future API mechanism now by reading Maximum Flat Rate Shipping Cost in the Specifying Shipping Costs portion of the Shipping documentation.
Rollout schedule:
A new field, HideDuplicateItems, has been added to GetCategoryListings, GetProducts, and GetSearchResults to suppress duplicate item listings from search results. When HideDuplicateItems is set to true in the request, duplicate item listings will not be returned in the response. If duplicate items were filtered from the search results, then DuplicateItems will be returned in the response with a value of true.
Items are considered duplicates when all of the following conditions are met:
The listing format for the duplicate and the original item listing must both fall into the same basic type of listing:
HideDuplicateItems is optional and defaults to false if not specified.
In the 565 release, changes were made to treat Store Inventory Format (StoresFixedPrice)items as basic fixed price (FixedPriceItem) items on the Italy site. This change is now extended to many more eBay sites. Starting mid-September, these changes will be available on the following eBay sites: US, US Motors, CA and CA-FR. Use GetCategoryFeatures with FeatureID set to CombinedFixedPriceTreatment to determine whether a given site or category are affected.
Additional changes for fixed price listings include:
FixedPriceItem) listings and Store inventory format (StoresFixedPrice) listings on the eBay Italy site. Listing durations of 30 days and "Good Til Cancelled" (GTC) are being allowed for store subscribers and non-store subscribers for basic fixed price and Store inventory format listings on additional sites and categories. Use GetCategoryFeatures with FeatureID set to ListingDurations to determine the standard listing durations allowed for a given site or category. Set FeatureID set to StoreOwnerExtendedListingDurationsEnabled to determine whether a given site or category supports extended listing durations for store owners. Set FeatureID to StoreOwnerExtendedListingDurations to get any extended durations.FixedPriceItem and StoresFixedPrice) listings. Use GetCategoryFeatures with FeatureID set to PayPalRequiredForStoreOwner to determine whether store owners must offer PayPal as a payment method for fixed price listings on a given site or category.ReviseQuantityAllowed or RevisePriceAllowed to determine whether quantity or price for fixed price listings can be revised at any time, despite standard restrictions.Please refer to the 565 release notes for additional information for these changes.
In the 565 release, the ability for sellers to specify the duration for Featured First (known as Gallery Featured on other eBay sites) was made available on the eBay Italy site. Starting in October, this feature will be supported by additional eBay sites. Use GetCategoryFeatures with FeatureID set to GalleryFeaturedDurations to determine whether a given site or category are affected. Please refer to the 565 release notes for additional information for these changes.
The new SetSellingManagerFeedbackOptions call allows Selling Manager and Selling Manager Pro subscribers to store up to ten comments that can be left as feedback to buyers. Selling Manager Pro subscribers can use AutomatedLeaveFeedbackEvent to specify an event that will trigger automated feedback to buyers.
A new field, ExternalUserData, is added to NotificationUserDataType in Set/GetNotificationPreferences requests, and to AbstractResponseType. The field is an XML-compliant string, not to exceed 256 characters. An example use case for this field is to set a third-party user-identifier string that will be returned with each notification payload. Please use due caution and encryption if you are passing any sensitive information
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.
Nacex and Correos were added to ShippingCarrierCodeType for domestic shipping for eBay Spain.
As previously announced, eBay will require all listings to specify a return policy and handling time (dispatch time) in Q1 2009. As some sellers may need to modify existing GTC (Good 'Til Canceled) listings to support these requirements, you can now use ReviseItem to add a return policy and/or dispatch time to an existing GTC listing, even when it has sales.
When Messages.Message.MessageType isn't set to AskSellerQuestion, a new value of None (in Message.QuestionType) is returned.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 583 and Changed Functionality - 583.
None for this release.
Documentation Changes and Errata - 581
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
FeedbackCommentArrayType |
Complex type | New |
HandlingTimeEnabledDefinitionType |
Complex type | New |
PayPalRequiredForStoreOwnerDefinitionType |
Complex type | New |
RefundDetailsType |
Complex type | New |
ReturnPolicyDetailsType |
Complex type | New |
ReturnPolicyEnabledDefinitionType |
Complex type | New |
ReturnPolicyType |
Complex type | New |
ReturnsAcceptedDetailsType |
Complex type | New |
ReturnsWithinDetailsType |
Complex type | New |
RevisePriceAllowedDefinitionType |
Complex type | New |
ReviseQuantityAllowedDefinitionType |
Complex type | New |
SetSellingManagerFeedbackOptionsRequestType |
Complex type | New |
SetSellingManagerFeedbackOptionsResponseType |
Complex type | New |
ShippingCostPaidByDetailsType |
Complex type | New |
StoreOwnerExtendedListingDurationsDefinitionType |
Complex type | New |
StoreOwnerExtendedListingDurationsEnabledDefinitionType |
Complex type | New |
StoreOwnerExtendedListingDurationsType |
Complex type | New |
WarrantyDurationDetailsType |
Complex type | New |
WarrantyOfferedDetailsType |
Complex type | New |
WarrantyTypeDetailsType |
Complex type | New |
AutomatedLeaveFeedbackEventCodeType |
Enumerated type | New |
RefundOptionsCodeType |
Enumerated type | New |
ReturnsAcceptedOptionsCodeType |
Enumerated type | New |
ReturnsWithinOptionsCodeType |
Enumerated type | New |
ShippingCostPaidByOptionsCodeType |
Enumerated type | New |
WarrantyDurationOptionsCodeType |
Enumerated type | New |
WarrantyOfferedCodeType |
Enumerated type | New |
WarrantyTypeOptionsCodeType |
Enumerated type | New |
CategoryFeatureType.HandlingTimeEnabled |
Element | New |
CategoryFeatureType.PayPalRequiredForStoreOwner |
Element | New |
CategoryFeatureType.ReturnPolicyEnabled |
Element | New |
CategoryFeatureType.RevisePriceAllowed |
Element | New |
CategoryFeatureType.ReviseQuantityAllowed |
Element | New |
CategoryFeatureType.StoreOwnerExtendedListingDurations |
Element | New |
CategoryFeatureType.StoreOwnerExtendedListingDurationsEnabled |
Element | New |
FeatureDefinitionsType.HandlingTimeEnabled |
Element | New |
FeatureDefinitionsType.PayPalRequiredForStoreOwner |
Element | New |
FeatureDefinitionsType.ReturnPolicyEnabled |
Element | New |
FeatureDefinitionsType.RevisePriceAllowed |
Element | New |
FeatureDefinitionsType.ReviseQuantityAllowed |
Element | New |
FeatureDefinitionsType.StoreOwnerExtendedListingDurations |
Element | New |
FeatureDefinitionsType.StoreOwnerExtendedListingDurationsEnabled |
Element | New |
GetCategoryListingsRequestType.HideDuplicateItems |
Element | New |
GetCategoryListingsResponseType.DuplicateItems |
Element | New |
GetProductsRequestType.HideDuplicateItems |
Element | New |
GetProductsResponseType.DuplicateItems |
Element | New |
GetSearchResultsRequestType.HideDuplicateItems |
Element | New |
GetSearchResultsResponseType.DuplicateItems |
Element | New |
GeteBayDetailsResponseType.ReturnPolicyDetails |
Element | New |
ItemType.ReturnPolicy |
Element | New |
SiteDefaultsType.HandlingTimeEnabled |
Element | New |
SiteDefaultsType.PayPalRequiredForStoreOwner |
Element | New |
SiteDefaultsType.ReturnPolicyEnabled |
Element | New |
SiteDefaultsType.RevisePriceAllowed |
Element | New |
SiteDefaultsType.ReviseQuantityAllowed |
Element | New |
SiteDefaultsType.StoreOwnerExtendedListingDurations |
Element | New |
SiteDefaultsType.StoreOwnerExtendedListingDurationsEnabled |
Element | New |
UserType.EnterpriseSeller |
Element | Reserved for future use |
DetailNameCodeType.ReturnPolicyDetails |
Enum | New |
FeatureIDCodeType.HandlingTimeEnabled |
Enum | New |
FeatureIDCodeType.PayPalRequiredForStoreOwner |
Enum | New |
FeatureIDCodeType.ReturnPolicyEnabled |
Enum | New |
FeatureIDCodeType.RevisePriceAllowed |
Enum | New |
FeatureIDCodeType.ReviseQuantityAllowed |
Enum | New |
FeatureIDCodeType.StoreOwnerExtendedListingDurations |
Enum | New |
FeatureIDCodeType.StoreOwnerExtendedListingDurationsEnabled |
Enum | New |
As announced in the eBay Developers Program blog, eBay has added or will soon be adding a number of new requirements for eBay listings. These include:
In the new View Item page, the user description is hosted by eBay on a different domain and loaded into an iFrame for display on the View Item page. This helps eBay to separate user content from eBay content, and protects users from content that could be harmful. With this change, your scripts will only be allowed to modify and control your item description and the area it occupies.
eBay has implemented this in a way that will not impact your SEO.
Here are some steps you can take to make sure your content appears as expected inside an iFrame.
Content Dimensions
File Linking
Content Validity
See also the blog post and commentary on the View Item page domain split.
For details on sizing pictures in the new View Item page, see this blog post.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 581.
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.
As previously announced in the blog, on the US site starting in October 2008, only four payment methods will be permitted in most categories. See the blog post on Paperless Payments for preliminary details. For general information about specifying payment methods, see Payment Method Differences.
By October 2008, most categories will require the seller to specify how long it will take the seller to ship an item after receiving cleared payment. This handling time (dispatch time) does not not include the shipping time itself (the time in transit). Use GetCategoryFeatures to determine which categories require a handling time. See Handling Time and Estimated Delivery Time.
In Q1 2009, most categories will require the seller to specify a return policy. Use GetCategoryFeatures to determine which categories require a return policy, and use GeteBayDetails to determine the return policy options each site supports. See Offering a Clear Return Policy.
To make return policies easier to specify, we have added a new ReturnPolicy node in the AddItem and GetItem families of calls. The new node will be functional in mid-September 2008.
You will no longer need to use the Attribute API to specify return policy details. However, the Attribute format will still be supported as input to the AddItem family of calls until after the 2008 holiday season. Please note that some sites have added a new "Return shipping will be paid by" attribute (3993) with two values: Buyer (81120) and Seller (81121). Some sites have also added an "Item must be returned within" value of 60 days (95148). GetItem no longer returns the Return Policy attributes, regardless of your request version.
As previously announced, sellers on the US site now are required to specify at least one domestic shipping service (exception: freight shipping). For those who intend to not ship an item (that is, local pickup only), a special "shipping service" has been created for the purpose of local pickup only. For more information, see Specifying Shipping Costs.
France joins several other European Union countries where users who have sold more than 2000 EUR a month over a period of three months will have to update their account type from 'personal' to 'business'. They will receive an error message if they try to use one of the AddItem family of API calls if their account is not defined or if it has been flagged as 'business required'.
For business accounts, a return policy is required.
See Changes for Business Sellers in Release 549 for more information.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 581 and Changed Functionality - 581.
None for this release.
Documentation Changes and Errata - 579
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
AuthenticationEntryArrayType |
Entity | Removed |
AuthenticationEntryType |
Entity | Removed |
CartItemArrayType |
Entity | Removed |
CartType |
Entity | Removed |
CheckoutCompleteRedirectType |
Entity | Removed |
ConditionSelectionCodeType |
Entity | Removed |
DomainHistogramType |
Entity | Removed |
ExpressDetailLevelCodeType |
Entity | Removed |
ExpressHistogramSortCodeType |
Entity | Removed |
ExpressItemSortCodeType |
Entity | Removed |
ExpressProductSortCodeType |
Entity | Removed |
GetCartRequestType |
Entity | Removed |
GetCartResponseType |
Entity | Removed |
GetExpressWishListRequestType |
Entity | Removed |
GetExpressWishListResponseType |
Entity | Removed |
GetItemRequestType.IncludeExpressRequirements |
Entity | Removed |
GetSearchResultsExpressRequestType |
Entity | Removed |
GetSearchResultsExpressResponseType |
Entity | Removed |
GetUserPreferencesResponseType.ExpressPreferences |
Entity | Removed |
ItemType.ExpressDetails |
Entity | Removed |
ItemType.ExpressOptOut |
Entity | Removed |
ListingDetailsType.ExpressItemRequirements |
Entity | Removed |
ListingDetailsType.ExpressListing |
Entity | Removed |
ProductArrayType |
Entity | Removed |
SellerType.ExpressEligible |
Entity | Removed |
SellerType.ExpressSellerRequirements |
Entity | Removed |
SellerType.ExpressWallet |
Entity | Removed |
SetCartRequestType |
Entity | Removed |
SetCartResponseType |
Entity | Removed |
SetUserPreferencesRequestType.ExpressPreferences |
Entity | Removed |
WishListSortCodeType |
Entity | Removed |
WishListType |
Entity | Removed |
CharityInfoType.DisplayNameInCheckout |
Element | New |
By the end of September 2008, US eBay Express will be shut down. Any eBay Fixed Price and/or Store Inventory listings that appear on both eBay and US eBay Express will be removed from US eBay Express. These listings will remain active on eBay.com. The UK and Germany eBay Express sires were shut down in April 2008.
The following eBay Express-specific API calls (and related schema) have been deprecated as of release 579:
With request versions lower than 579, the calls will continue to work. However, regardless of the request version specified, the calls will stop working when the site is closed.
Please refer to the release notes and the respective Express sites for more information.
Please see the Developers Program Blog for information about recent announcements aimed at satisfying buyers and lowering upfront costs for sellers.
Starting in September 2008 on the Australia eBay site, sellers and bidders will not be able to retrieve each other's email addresses unless they are in a transactional relationship. If a listing is active, sellers will not be able to view the bidder's email address when using the following calls: GetHighBidders, GetBidderList, GetAllBidders. Please see the Anonymization of Email Addresses in Member to Member Communication section in the 573 release notes for more information.
Starting in September 2008, GetMyMessages API changes will be made available for the Australia Site. Please see the GetMyMessages Returns More Data section of the 573 release notes for details about the changes.
Also starting in September 2008 on the Australia site, the AddMemberMessageAAQToBidder call can be used for all categories and is not limited to Motors and Business & Industrial categories only.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 579.
Now you can set the DisplayNameInCheckout flag in CharityInfoType to display a nonprofit company name on the Review Your Purchase checkout page. If the user hovers the mouse over the nonprofit company name, the company's mission statement will be displayed. The value for the DisplayNameInCheckout field is returned with the GetCharities response.
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.
Starting in late August 2008, GetAttributesCS will start returning more item condition choices for US Media listings (Books, DVDs & Movies, Music, and Video Games).
At time of this writing, we expect to support the following value names and IDs for the Condition attribute (10244) in Media-related characteristic sets:
with the following exceptions:
In general, we are reusing the previous "New" (including "New in Box" and "New, Never Opened") value IDs for "Brand New", and the previous "Used" value IDs for "Acceptable". If you leave the item condition as unspecified for Media listings, we will also map it to "Acceptable". This means that if you are using the old conditions in your listing templates, they will still work. But the value names will be different on eBay and in GetItem (as described above). To help your sellers describe their items more accurately to buyers, we recommend that you use GetAttributesCS to get the latest values and to keep them up to date.
Please note that the LookupAttribute field in AddItem does not support the new condition values. You can only specify "New" or "Used". eBay will map those values to "Brand New" or "Acceptable" as appropriate.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 579 and Changed Functionality - 579.
None for this release.
Documentation Changes and Errata - 577
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
AdFormatLeadType.FirstName |
Entity | Removed |
AdFormatLeadType.LastName |
Entity | Removed |
AdFormatLeadType.Phone |
Entity | Removed |
AdFormatLeadType.Phone2 |
Entity | Removed |
ConfirmIdentityRequestType |
Complex type | New |
ConfirmIdentityResponseType |
Complex type | New |
CompleteSaleRequestType.OrderID |
Element | New |
SellerType.StoreSite |
Element | New |
GetReturnURL |
Call | Removed |
GetRuName |
Call | Removed |
SetReturnURL |
Call | Removed |
AuthenticationEntryType |
Complex type | Removed |
AuthenticationEntryArrayType |
Complex type | Removed |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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.
We have made several improvements to the User Token retrieval process, and made it even easier for developers to configure and maintain their application level settings.
New features of the token retrieval process include:
Enhanced User Consent Page: the User Consent Page now supports the ability for an application to upload their Application Name, Logo, Description, and URL for display to the end user on the User Consent Page. This improvement makes the User Consent Page more friendly to new users, and provides a way for users to find out more information about the application they are authorizing. For more information, please see http://developer.ebay.com/DevZone/XML/docs/WebHelp/GettingTokens-.html.
eBay UserID Verification Option: An ID Verification option has been added to the User Consent flow, for applications that only need to confirm an eBay UserID. This option is supported at the RuName level, and allows an application to confirm an eBay UserID by taking the user through the standard User Consent Flow [also known as the Auth & Auth flow]. The application can use the ConfirmIdentity call to verify the UserID that was provided at login time. For more information, please see http://developer.ebay.com/DevZone/XML/docs/WebHelp/GettingTokens-Getting_Tokens_for_Applications_with_Multiple_Users.html.
A new configuration tool is now available on developer.ebay.com for developers to view their stored user token, manage application level Platform Notification and Client Notification settings, and customize the User Consent Page. Please try out the new tool at https://developer.ebay.com/devzone/account/appsettings/ (requires login).
With the introduction of the improved token retrieval process, the following calls are deprecated: SetReturnURL, GetReturnURL, and GetRuName.
For logical or functional changes to existing features and calls, including code list changes, see Changed Functionality - 577.
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.
You can now use the CompleteSale call to designate that a multiple-item order is complete. When an OrderID is used in the CompleteSaleRequest, ItemID and TransactionID are ignored by the call. The CompleteSale status applies to the order as well as to all of the child transactions of that order.
The AddMemberMessageAAQToPartner call could previously only be used after the end of an auction/sale, which made it difficult for sellers with GTC (Good 'Til Closed) listings. Now you can use this call to contact a buyer during the active listing.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 577 and Changed Functionality - 577.
The documentation for GetAdFormatLeads has been updated to reflect the actual call behavior with respect to returning phone numbers for leads. For request versions 561 and later, lead phone numbers, Phone and Phone2, are returned in AdFormatLead.Address. Similarly, FirstName and FirstName are returned in AdFormatLead.Address. Phone, Phone2, FirstName, and LastName in AdFormatLeadType have been deprecated.
The schema and documentation for GetUser have been updated to include StoreSite.
Documentation Changes and Errata - 575
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
GetAttributesCSRequestType.DigitalDelivery |
Entity | Removed |
OrderType.DigitalDelivery |
Entity | Removed |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 575.
The GetSearchResults call returns more information. It returns the seller's UserID (Item.Seller.UserID) if IncludeFeedback is set to true in GetSearchResultsRequest.
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.
As of March 2008, all digital listings (downloadable goods) selling on eBay US are required to be listed in a Classified Ad format within the Everything Else > Information Product category. The previous digital delivery feature is disabled as of March 28, 2008. AddItem and related calls using the DigitalDeliveryDetails fields will fail. Remaining digital delivery fields, such as GetAttributesCSRequestType.DigitalDelivery and OrderType.DigitalDelivery, have been removed from the schema.
For a complete list of deprecated objects (and which objects to use instead), see Deprecated Objects.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 575 and Changed Functionality - 575.
The description of this notification has been corrected to include "fixed price": "An AuctionCheckoutComplete notification is sent when a buyer completes the checkout process for an auction item or for a fixed price item."
When you call GetItemsAwaitingFeedback as a Seller, you receive a list of the items you are selling that have not received feedback, and the Buyer associated with each item. Likewise, when you call GetItemsAwaitingFeedback as a Buyer, you receive a list of the items you have purchased, and the Seller associated with each item. The Seller information, which was missing from the documentation for the GetItemsAwaitingFeedback response, is now included.
Documentation Changes and Errata - 573
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
CategoryFeatureType.DigitalDeliveryEnabled |
Entity | Removed |
DigitalDeliveryDetailsType |
Entity | Removed |
DigitalDeliveryEnabledCodeType |
Entity | Removed |
DigitalDeliveryEnabledDefinitionType |
Entity | Removed |
DigitalDeliveryMethodCodeType |
Entity | Removed |
ExpressItemRequirementsType.NoDigitalDelivery |
Entity | Removed |
FeatureDefinitionsType.DigitalDeliveryEnabled |
Entity | Removed |
GetSearchResultsRequestType.DigitalDelivery |
Entity | Removed |
ItemType.DigitalDeliveryDetails |
Entity | Removed |
SiteDefaultsType.DigitalDeliveryEnabled |
Entity | Removed |
AnnouncementMessageType |
Complex type | New |
MyMessagesExternalMessageIDArrayType |
Complex type | New |
AnnouncementMessageCodeType |
Enumerated type | New |
GetMyMessagesRequestType.ExternalMessageIDs |
Element | New |
GetMyeBayBuyingRequestType.DeletedFromLostList |
Element | New |
GetMyeBayBuyingRequestType.DeletedFromWonList |
Element | New |
GetMyeBayBuyingResponseType.DeletedFromLostList |
Element | New |
GetMyeBayBuyingResponseType.DeletedFromWonList |
Element | New |
GetMyeBaySellingRequestType.BidList |
Element | New |
GetMyeBaySellingRequestType.DeletedFromSoldList |
Element | New |
GetMyeBaySellingRequestType.DeletedFromUnsoldList |
Element | New |
GetMyeBaySellingResponseType.BidList |
Element | New |
GetMyeBaySellingResponseType.DeletedFromSoldList |
Element | New |
GetMyeBaySellingResponseType.DeletedFromUnsoldList |
Element | New |
MyMessagesMessageType.Content |
Element | New |
MyMessagesMessageType.ListingStatus |
Element | New |
MyMessagesMessageType.MessageType |
Element | New |
MyMessagesMessageType.QuestionType |
Element | New |
ShippingServiceDetailsType.DeprecationDetails |
Element | New |
ShippingServiceDetailsType.MappedToShippingServiceID |
Element | New |
ShippingServiceCodeType.BEFR_LaPosteCertifiedShipping |
Enum | New |
ShippingServiceCodeType.BEFR_LaPosteStandardShipping |
Enum | New |
ShippingServiceCodeType.BEFR_LaPosteTaxipost24h |
Enum | New |
ShippingServiceCodeType.BEFR_LaPosteTaxipostLLS |
Enum | New |
ShippingServiceCodeType.BEFR_LaPosteTaxipostSecur |
Enum | New |
ShippingServiceCodeType.BEFR_PostInternationalRegistered |
Enum | New |
ShippingServiceCodeType.BEFR_PostInternationalStandard |
Enum | New |
ShippingServiceCodeType.BEFR_TNTInternational |
Enum | New |
ShippingServiceCodeType.BENL_DePostCertifiedShipping |
Enum | New |
ShippingServiceCodeType.BENL_DePostStandardShipping |
Enum | New |
ShippingServiceCodeType.BENL_DePostTaxipost24h |
Enum | New |
ShippingServiceCodeType.BENL_DePostTaxipostLLS |
Enum | New |
ShippingServiceCodeType.BENL_DePostTaxipostSecur |
Enum | New |
ShippingServiceCodeType.BENL_OtherShippingMethods |
Enum | New |
ShippingServiceCodeType.BENL_PostInternationalRegistered |
Enum | New |
ShippingServiceCodeType.BENL_PostInternationalStandard |
Enum | New |
ShippingServiceCodeType.BENL_TNTInternational |
Enum | New |
ShippingServiceCodeType.DE_DHLPaket |
Enum | New |
ShippingServiceCodeType.DE_DHLPaketInternational |
Enum | New |
ShippingServiceCodeType.DE_DPBriefInternational |
Enum | New |
ShippingServiceCodeType.DE_DPBuecherWarensendung |
Enum | New |
ShippingServiceCodeType.DE_DPD |
Enum | New |
ShippingServiceCodeType.DE_DPDInternational |
Enum | New |
ShippingServiceCodeType.DE_Einschreiben |
Enum | New |
ShippingServiceCodeType.DE_Express |
Enum | New |
ShippingServiceCodeType.DE_ExpressInternational |
Enum | New |
ShippingServiceCodeType.DE_GLS |
Enum | New |
ShippingServiceCodeType.DE_GLSInternational |
Enum | New |
ShippingServiceCodeType.DE_HermesPaket |
Enum | New |
ShippingServiceCodeType.DE_HermesPaketInternational |
Enum | New |
ShippingServiceCodeType.DE_IloxxTransport |
Enum | New |
ShippingServiceCodeType.DE_IloxxTransportInternational |
Enum | New |
ShippingServiceCodeType.DE_Nachname |
Enum | New |
ShippingServiceCodeType.DE_Paket |
Enum | New |
ShippingServiceCodeType.DE_PaketInternational |
Enum | New |
ShippingServiceCodeType.DE_SonstigeDomestic |
Enum | New |
ShippingServiceCodeType.DE_SonstigeInternational |
Enum | New |
ShippingServiceCodeType.DE_SpecialDelivery |
Enum | New |
ShippingServiceCodeType.DE_UPS |
Enum | New |
ShippingServiceCodeType.DE_UPSInternational |
Enum | New |
As previously announced, sellers on the Germany (DE) and Spain (ES) sites must specify at least one domestic shipping service. In August, US sellers will likewise be required to specify at least one domestic shipping service (exception: freight shipping). For those who intend to not ship an item (that is, local pickup only), a special "shipping service" has been created for the purpose of local pickup only. For more information, see Specifying Shipping Costs.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 573.
If a particular shipping service will be or has been deprecated, the ShippingServiceDetails container (something that can be returned by GeteBayDetails) includes a DeprecationDetails container and a MappedToShippingServiceID.
How you use this deprecation information in your application is up to you. For example, you may choose to display a to-be-deprecated shipping service for the seller to select, or you may choose to only offer the service identified in MappedToShippingServiceID.
Response to a user selecting a deprecated service is different in the API version of the Sell/Revise/Relist Your Item flows than it is in the eBay Web site version.
For details, see Deprecated Shipping Services in the Shipping documentation.
Starting in September 2008, sellers and bidders will not be able to retrieve each other's email addresses unless they are in a transactional relationship. If a listing is active, sellers will not be able to view the bidder's email address when using the following calls: GetHighBidders, GetBidderList,GetAllBidders. This change is applicable to the Sandbox environment starting Mid-July 2008.
A seller can still view the email address of the winning bidder after the listing ends.
BidArray.Offer.User.Email will contain invalid request if an item is active and for users who are neither the winning bidder nor the seller of that item.
MemberMessage.HideSendersEmailAddress will be deprecated in sandbox environment starting mid-July 2008 and in production in September 2008.
The GetMyMessages call returns more information. It returns the status of a listing (Messages.Message.ListingStatus) when the member-to-member email question is formed. It also returns the type of message retrieved using Messages.Message.MessageType, and the context of the question sent in the email that corresponds to the subject of the message (Messages.Message.QuestionType).
The GetMyMessages call also returns the External message ID (in the Messages.Message.ExternalMessageID), which uniquely identifies a message.
Additionally, a new Content tag is returned (Messages.Message.Content). It contains the message body in plain text format.
Starting in mid July 2008, you can use GetMyeBaySelling.BidList to obtain a seller's BidList from My eBay. The BidList includes all listings with at least one bid from a seller's Active Selling view or Items I'm Selling list in My eBay.
Also, BidLists returned using GetMyeBayBuying and GetMyeBaySelling will now include FeedbackScore and FeedbackRatingStar in BidList.ItemArray.Item.Seller and BidList.ItemArray.Item.SellingStatus.HighBidder.
GetMyeBayBuying can now return a buyer's DeletedFromWonList and DeletedFromLostList which contain items won or lost and deleted from the buyer's My eBay. Furthermore, GetMyeBaySelling can now return a seller's DeletedFromSoldList and DeletedFromUnsoldList. These lists contain items that sold and items that did not sell (or were ended by the seller) which the seller has deleted from My eBay. You can use DurationInDays to return items that have been deleted up to 90 days before the present date.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
See Schema Changes for a list of new shipping services.
As of March 2008, all digital listings (downloadable goods) selling on eBay US are required to be listed in a Classified Ad format within the Everything Else > Information Product category. The previous digital delivery feature is disabled as of March 28, 2008. AddItem and related calls using the DigitalDeliveryDetails fields will fail. Most of the digital delivery fields, such as ItemType.DigitalDeliveryDetails, have been removed from the schema. All remaining digital delivery related fields will be removed in the subsequent release.
For a complete list of deprecated objects (and which objects to use instead), see Deprecated Objects.
Sellers who wish to continue to use the Trading API to offer digital goods can do so by setting the value of Item.ListingType to LeadGeneration and Item.ListingSubtype2 to ClassifiedAd instead (and list in the Everything Else > Information Product category). Using the Classified Ads format, sellers receive a 30-day ad at a fixed price. This solution enables sellers to continue to market their digital goods on eBay; however, because Classified Ad listings are a lead generation tool and do not result in transactions that go through eBay, Feedback cannot be exchanged between buyer and seller.
See Selling Digital Items in the eBay site help for more information and requirements for listing digitally delivered items.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 573 and Changed Functionality - 573.
None for this release.
Documentation Changes and Errata - 625
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
No changed calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
placeholder |
Element | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 625.
None for this release.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
None for this release.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 625 and Changed Functionality - 625.
None for this release.
Documentation Changes and Errata - 571
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
INEscrowWorkflowTimelineDefinitionType |
Complex type | New |
INEscrowWorkflowTimelineCodeType |
Enumerated type | New |
AddressType.Phone2 |
Element | New |
CategoryFeatureType.INEscrowWorkflowTimeline |
Element | New |
FeatureDefinitionsType.INEscrowWorkflowTimeline |
Element | New |
SiteDefaultsType.INEscrowWorkflowTimeline |
Element | New |
FeatureIDCodeType.INEscrowWorkflowTimeline |
Enum | New |
ShippingServiceCodeType.Courier |
Enum | New |
ShippingServiceCodeType.Freight |
Enum | New |
We have updated the version 569 WSDL, because the following types had mis-spellings in the names:
This has been corrected in version 571. If you have already downloaded version 569, please replace it with 571 or download it again.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 571.
Beginning in late June, 2008, the PaisaPay escrow workflow, which is available on selected categories on the India site (site ID 203) that offer the PaisaPayEscrow payment method, will be upgraded to define two additional escrow workflows. The request for GetCategoryFeatures now provides FeatureIDCodeType.INEscrowWorkflowTimeline to determine the escrow workflow that is active on an eligible category. It returns Default (the existing escrow workflow), WorkflowA or WorkflowB in CategoryFeatureType.INEscrowWorkflowTimeline in the GetCategoryFeatures response. For complete details, see Payment Method Differences in the Trading Webhelp.
Starting in early July 2008, sellers using the eBay UK Web site can select "Courier" for shipping (the UK equivalent of the US's "Freight") when listing items. A handful of API changes have been made to support this. See Specifying Freight Shipping in the Shipping chapter for details.
Affected calls: the AddItem family of calls, GetItem, GetItemTransactions, and GetItemShipping.
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.
FreightOtherShipping (an enumeration in ShippingServiceCodeType) had been used to represent US items shipped with a freight shipping service other than FreightQuote.com. The new enumeration for this concept is named Freight, and FreightOtherShipping has been deprecated.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 571 and Changed Functionality - 571.
See the revised section Specifying Freight Shipping in the Shipping chapter for a reworked presentation of steps for implementing freight shipping.
The table in "Restrictions on Changing Item Properties During a Revision" in the section Revising Items was missing details about a Version 563 improvement: shipping details can be revised for multi-quantity items.
Documentation Changes and Errata - 569
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
ClassifiedAdCompanyNameEnabledDefinitionType |
Complex type | New |
ClassifiedAdContactByAddressEnabledDefinitionType |
Complex type | New |
ClassifiedAdPhoneCountDefinitionType |
Complex type | New |
ClassifiedAdStreetCountDefinitionType |
Complex type | New |
GetClientAlertsAuthTokenRequestType |
Complex type | New |
GetClientAlertsAuthTokenResponseType |
Complex type | New |
LocalMarketAdFormatEnabledDefinitionType |
Complex type | New |
LocalMarketAutoAcceptEnabledDefinitionType |
Complex type | New |
LocalMarketAutoDeclineEnabledDefinitionType |
Complex type | New |
LocalMarketBestOfferEnabledDefinitionType |
Complex type | New |
LocalMarketCompanyNameEnabledDefinitionType |
Complex type | New |
LocalMarketContactByAddressEnabledDefinitionType |
Complex type | New |
LocalMarketContactByEmailEnabledDefinitionType |
Complex type | New |
LocalMarketContactByPhoneEnabledDefinitionType |
Complex type | New |
LocalMarketCounterOfferEnabledDefinitionType |
Complex type | New |
LocalMarketPaymentMethodCheckOutEnabledDefinitionType |
Complex type | New |
LocalMarketPhoneCountDefinitionType |
Complex type | New |
LocalMarketSellerContactDetailsEnabledDefinitionType |
Complex type | New |
LocalMarketShippingMethodEnabledDefinitionType |
Complex type | New |
LocalMarketStreetCountDefinitionType |
Complex type | New |
NonSubscriptionDefinitionType |
Complex type | New |
PremiumSubscriptionDefinitionType |
Complex type | New |
RegularSubscriptionDefinitionType |
Complex type | New |
SpecialitySubscriptionDefinitionType |
Complex type | New |
eBayMotorsProAdFormatEnabledDefinitionType |
Complex type | New |
eBayMotorsProAutoAcceptEnabledDefinitionType |
Complex type | New |
eBayMotorsProAutoDeclineEnabledDefinitionType |
Complex type | New |
eBayMotorsProBestOfferEnabledDefinitionType |
Complex type | New |
eBayMotorsProCompanyNameEnabledDefinitionType |
Complex type | New |
eBayMotorsProContactByAddressEnabledDefinitionType |
Complex type | New |
eBayMotorsProContactByEmailEnabledDefinitionType |
Complex type | New |
eBayMotorsProContactByPhoneEnabledDefinitionType |
Complex type | New |
eBayMotorsProCounterOfferEnabledDefinitionType |
Complex type | New |
eBayMotorsProPaymentMethodCheckOutEnabledDefinitionType |
Complex type | New |
eBayMotorsProPhoneCountDefinitionType |
Complex type | New |
eBayMotorsProSellerContactDetailsEnabledDefinitionType |
Complex type | New |
eBayMotorsProShippingMethodEnabledDefinitionType |
Complex type | New |
eBayMotorsProStreetCountDefinitionType |
Complex type | New |
GeographicExposureCodeType |
Enumerated type | New |
CategoryFeatureType.ClassifiedAdCompanyNameEnabled |
Element | New |
CategoryFeatureType.ClassifiedAdContactByAddressEnabled |
Element | New |
CategoryFeatureType.ClassifiedAdPhoneCount |
Element | New |
CategoryFeatureType.ClassifiedAdStreetCount |
Element | New |
CategoryFeatureType.LocalMarketAdFormatEnabled |
Element | New |
CategoryFeatureType.LocalMarketAutoAcceptEnabled |
Element | New |
CategoryFeatureType.LocalMarketAutoDeclineEnabled |
Element | New |
CategoryFeatureType.LocalMarketBestOfferEnabled |
Element | New |
CategoryFeatureType.LocalMarketCompanyNameEnabled |
Element | New |
CategoryFeatureType.LocalMarketContactByAddressEnabled |
Element | New |
CategoryFeatureType.LocalMarketContactByEmailEnabled |
Element | New |
CategoryFeatureType.LocalMarketContactByPhoneEnabled |
Element | New |
CategoryFeatureType.LocalMarketCounterOfferEnabled |
Element | New |
CategoryFeatureType.LocalMarketPaymentMethodCheckOutEnabled |
Element | New |
CategoryFeatureType.LocalMarketPhoneCount |
Element | New |
CategoryFeatureType.LocalMarketSellerContactDetailsEnabled |
Element | New |
CategoryFeatureType.LocalMarketShippingMethodEnabled |
Element | New |
CategoryFeatureType.LocalMarketStreetCount |
Element | New |
CategoryFeatureType.NonSubscription |
Element | New |
CategoryFeatureType.PremiumSubscription |
Element | New |
CategoryFeatureType.RegularSubscription |
Element | New |
CategoryFeatureType.SpecialitySubscription |
Element | New |
CategoryFeatureType.eBayMotorsProAdFormatEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProAutoAcceptEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProAutoDeclineEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProBestOfferEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProCompanyNameEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProContactByAddressEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProContactByEmailEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProContactByPhoneEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProCounterOfferEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProPaymentMethodCheckOutEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProPhoneCount |
Element | New |
CategoryFeatureType.eBayMotorsProSellerContactDetailsEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProShippingMethodEnabled |
Element | New |
CategoryFeatureType.eBayMotorsProStreetCount |
Element | New |
FeatureDefinitionsType.ClassifiedAdCompanyNameEnabled |
Element | New |
FeatureDefinitionsType.ClassifiedAdContactByAddressEnabled |
Element | New |
FeatureDefinitionsType.ClassifiedAdPhoneCount |
Element | New |
FeatureDefinitionsType.ClassifiedAdStreetCount |
Element | New |
FeatureDefinitionsType.LocalMarketAdFormatEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketAutoAcceptEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketAutoDeclineEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketBestOfferEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketCompanyNameEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketContactByAddressEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketContactByEmailEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketContactByPhoneEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketCounterOfferEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketPaymentMethodCheckOutEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketPhoneCount |
Element | New |
FeatureDefinitionsType.LocalMarketSellerContactDetailsEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketShippingMethodEnabled |
Element | New |
FeatureDefinitionsType.LocalMarketStreetCount |
Element | New |
FeatureDefinitionsType.NonSubscription |
Element | New |
FeatureDefinitionsType.PremiumSubscription |
Element | New |
FeatureDefinitionsType.RegularSubscription |
Element | New |
FeatureDefinitionsType.SpecialitySubscription |
Element | New |
FeatureDefinitionsType.eBayMotorsProAdFormatEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProAutoAcceptEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProAutoDeclineEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProBestOfferEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProCompanyNameEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProContactByAddressEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProContactByEmailEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProContactByPhoneEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProCounterOfferEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProPaymentMethodCheckOutEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProPhoneCount |
Element | New |
FeatureDefinitionsType.eBayMotorsProSellerContactDetailsEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProShippingMethodEnabled |
Element | New |
FeatureDefinitionsType.eBayMotorsProStreetCount |
Element | New |
SiteDefaultsType.ClassifiedAdCompanyNameEnabled |
Element | New |
SiteDefaultsType.ClassifiedAdContactByAddressEnabled |
Element | New |
SiteDefaultsType.ClassifiedAdPhoneCount |
Element | New |
SiteDefaultsType.ClassifiedAdStreetCount |
Element | New |
SiteDefaultsType.LocalMarketAdFormatEnabled |
Element | New |
SiteDefaultsType.LocalMarketAutoAcceptEnabled |
Element | New |
SiteDefaultsType.LocalMarketAutoDeclineEnabled |
Element | New |
SiteDefaultsType.LocalMarketBestOfferEnabled |
Element | New |
SiteDefaultsType.LocalMarketCompanyNameEnabled |
Element | New |
SiteDefaultsType.LocalMarketContactByAddressEnabled |
Element | New |
SiteDefaultsType.LocalMarketContactByEmailEnabled |
Element | New |
SiteDefaultsType.LocalMarketContactByPhoneEnabled |
Element | New |
SiteDefaultsType.LocalMarketCounterOfferEnabled |
Element | New |
SiteDefaultsType.LocalMarketPaymentMethodCheckOutEnabled |
Element | New |
SiteDefaultsType.LocalMarketPhoneCount |
Element | New |
SiteDefaultsType.LocalMarketSellerContactDetailsEnabled |
Element | New |
SiteDefaultsType.LocalMarketShippingMethodEnabled |
Element | New |
SiteDefaultsType.LocalMarketStreetCount |
Element | New |
SiteDefaultsType.NonSubscription |
Element | New |
SiteDefaultsType.PremiumSubscription |
Element | New |
SiteDefaultsType.RegularSubscription |
Element | New |
SiteDefaultsType.SpecialitySubscription |
Element | New |
SiteDefaultsType.eBayMotorsProAdFormatEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProAutoAcceptEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProAutoDeclineEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProBestOfferEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProCompanyNameEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProContactByAddressEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProContactByEmailEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProContactByPhoneEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProCounterOfferEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProPaymentMethodCheckOutEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProPhoneCount |
Element | New |
SiteDefaultsType.eBayMotorsProSellerContactDetailsEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProShippingMethodEnabled |
Element | New |
SiteDefaultsType.eBayMotorsProStreetCount |
Element | New |
DeviceTypeCodeType.ClientAlerts |
Enum | New |
FeatureIDCodeType.ClassifiedAdCompanyNameEnabled |
Enum | New |
FeatureIDCodeType.ClassifiedAdContactByAddressEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketAdFormatEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketAutoAcceptEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketAutoDeclineEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketBestOfferEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketCompanyNameEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketContactByAddressEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketContactByEmailEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketContactByPhoneEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketCounterOfferEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketPaymentMethodCheckOutEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketSellerContactDetailsEnabled |
Enum | New |
FeatureIDCodeType.LocalMarketShippingMethodEnabled |
Enum | New |
FeatureIDCodeType.NonSubscription |
Enum | New |
FeatureIDCodeType.PremiumSubscription |
Enum | New |
FeatureIDCodeType.RegularSubscription |
Enum | New |
FeatureIDCodeType.SpecialitySubscription |
Enum | New |
FeatureIDCodeType.eBayMotorsProAdFormatEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProAutoAcceptEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProAutoDeclineEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProBestOfferEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProCompanyNameEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProContactByAddressEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProContactByEmailEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProContactByPhoneEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProCounterOfferEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProPaymentMethodCheckOutEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProSellerContactDetailsEnabled |
Enum | New |
FeatureIDCodeType.eBayMotorsProShippingMethodEnabled |
Enum | New |
We have updated the WSDL, because the following types had mis-spellings in the names:
This has been corrected in version 571. If you have already downloaded version 569, please replace it with 571 or download it again.
In late May, 2008, several changes to listing policies were announced on the eBay site. The changes are described on the blog of the eBay Developers Program. Please review the changes at Developer Impact of May 2008 Listing Policy Changes.
Available near the end of June, the Best Offer Only option will no longer be required for Classified Ads on the eBay Motors site. Instead, you will be able to list a Classified Ad with or without a Best Offer option. In addition, you will have more options for contact settings. For instance, you may be able to add two phone numbers or addresses in the contact information, instead of only one.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 569.
You can use the GetClientAlertsAuthToken call to retrieve a token for the Client Alerts API.
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.
You may notice additional category definition types and elements associated with eBayMotors, ClassifedAd, and Local Market contact information. These elements have been added in preparation for more flexible contact options and Ad Format changes for the Motors site that are coming at the end of June. These new fields will allow you to retrieve more response data with the GetCategoryFeatures call.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 569 and Changed Functionality - 569.
The documentation has been updated to state that GetItemTransactions can return incorrect sales tax if the name of a state is not abbreviated (e.g. if the value is "Illinois" rather than "IL") in TransactionArray.Transaction.Buyer.BuyerInfo.ShippingAddress.StateOrProvince. If the name of a state is not abbreviated, sales tax should be obtained using GetOrderTransactions.
Documentation Changes and Errata - 567
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
DeliveryURLDetailType |
Complex type | New |
PayPalRequiredDefinitionType |
Complex type | New |
ApplicationDeliveryPreferencesType.DeliveryURLDetails |
Element | New |
CategoryFeatureType.PayPalRequired |
Element | New |
FeatureDefinitionsType.PayPalRequired |
Element | New |
GetFeedbackRequestType.CommentType |
Element | New |
GetFeedbackRequestType.ItemID |
Element | New |
GetFeedbackRequestType.TransactionID |
Element | New |
GetFeedbackResponseType.EntriesPerPage |
Element | New |
GetFeedbackResponseType.PageNumber |
Element | New |
GetFeedbackResponseType.PaginationResult |
Element | New |
GetNotificationPreferencesResponseType.DeliveryURLName |
Element | New |
GetOrderTransactionsRequestType.IncludeFinalValueFees |
Element | New |
GetSellerListRequestType.CategoryID |
Element | New |
NotificationDetailsType.DeliveryURLName |
Element | New |
SetNotificationPreferencesRequestType.DeliveryURLName |
Element | New |
SiteDefaultsType.PayPalRequired |
Element | New |
FeatureIDCodeType.PayPalRequired |
Enum | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 567.
When you retrieve a seller's items using GetSellerList, you can specify a category ID to restrict the results to items in a category.
When you retrieve orders using GetOrderTransactions, you can specify IncludeFinalValueFees if you want final value fees in the response. Formerly, a second call using GetItemTransactions was needed for final value fees.
The GetMyeBayBuying and GetMyeBaySelling calls return more transaction data. They return the created date, paid time, and shipped time for the item.
You can specify multiple notification URLs for an application. For more information, see Working with Platform Notifications.
GetFeedback now allows you to request feedback records by Transaction ID or Item ID, in addition to the original User ID option. You can also request just one type of feedback, such as Positive, Negative, or Neutral, using the CommentType element. You can use two CommentType elements in the same request to exclude the third type from the response.
If you're requesting feedback with the User ID and ReturnAll options, you can specify whether you want to return 25, 50, 100, or 200 items per page with the EntriesPerPage element. You can also designate which page of the results you would like to receive by including a PageNumber value in your request.
Your Seller Dashboard provides a brief summary of your status as an eBay seller. This status information can help you monitor your selling performance and keep your account in good standing.
A new API call, GetSellerDashboard, is now available in production. It gives you a quick view of the following information:
Unlike the Seller Dashboard that is shown on the eBay Web site, GetSellerDashboard does not provide information about your Detailed Seller Ratings. Instead, you can use GetFeedback to retrieve average ratings and other feedback information.
Please note that GetSellerDashboard cannot return the correct data in the Sandbox. You can test this call in production to get more useful results.
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.
As previously announced, starting on June 17, 2008, listings on the Australia site must be paid for with one of the following: PayPal, pay on pick up (i.e., paid for when picking up the item), or Visa/MasterCard (with transactions processed by PayPal). This affects AddItem and related calls.
After June 17, 2008, when you call GeteBayDetails, and specify that you want
the payment methods for the Australia site (site ID 15), the call response will contain the two valid payment methods
for the site: PayPal and CashOnPickup.
You can use GetCategoryFeatures to determine if listings on a site must include PayPal as a payment method.
Be sure to call GeteBayDetails periodically to obtain the latest set of valid payment methods for the sites on which listings will appear.
Starting on June 16, 2008, when you retrieve a seller's items using GetSellerList, the maximum time range allowed in a request is a value under 120 days.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 567 and Changed Functionality - 567.
A note in the Trading Web Services Guide that incorrectly stated that SetNotificationPreferences works only in Production has been removed.
The Trading Web Services Guide has been updated as follows: the table that showed site-specific payment options has been replaced by information about the API calls used for retrieving the site-specific payment options.
A note in the Call Reference that incorrectly stated that FetchToken requests using the call SecretID require a password has been removed. FetchToken requests require either the SecretID or the SessionID; SessionID is recommended.
Documentation Changes and Errata - 565
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
BuyerRequirementsType |
Entity | Removed |
ItemType.BuyerRequirements |
Entity | Removed |
BuyerRequirementDetailsType |
Complex type | New |
CombinedFixedPriceTreatmentEnabledDefinitionType |
Complex type | New |
ListingEnhancementDurationDefinitionType |
Complex type | New |
ListingEnhancementDurationReferenceType |
Complex type | New |
MaximumBuyerPolicyViolationsType |
Complex type | New |
MaximumUnpaidItemStrikesInfoType |
Complex type | New |
ListingEnhancementDurationCodeType |
Enumerated type | New |
PeriodCodeType |
Enumerated type | New |
ProductStateCodeType |
Enumerated type | New |
CatalogProductType.ProductState |
Element | New |
CategoryFeatureType.CombinedFixedPriceTreatmentEnabled |
Element | New |
CategoryFeatureType.GalleryFeaturedDurations |
Element | New |
ExpressProductType.ProductState |
Element | New |
FeatureDefinitionsType.CombinedFixedPriceTreatmentEnabled |
Element | New |
FeatureDefinitionsType.GalleryFeaturedDurations |
Element | New |
GetUserPreferencesRequestType.ShowEmailShipmentTrackingNumberPreference |
Element | New |
GetUserPreferencesResponseType.EmailShipmentTrackingNumberPreference |
Element | New |
ItemType.BuyerRequirementDetails |
Element | New |
PictureDetailsType.GalleryDuration |
Element | New |
ProductInfoType.ProductState |
Element | New |
SetUserPreferencesRequestType.EmailShipmentTrackingNumberPreference |
Element | New |
SiteDefaultsType.CombinedFixedPriceTreatmentEnabled |
Element | New |
SiteDefaultsType.GalleryFeaturedDurations |
Element | New |
FeatureIDCodeType.CombinedFixedPriceTreatment |
Enum | New |
FeatureIDCodeType.GalleryFeaturedDurations |
Enum | New |
ShippingServiceCodeType.CanadaPostExpeditedFlatRateBox |
Enum | New |
ShippingServiceCodeType.CanadaPostExpeditedFlatRateBoxUSA |
Enum | New |
As previously announced, starting on May 21, 2008, listings on the Australia site (site ID 15) must offer PayPal as a payment method.
Starting on June 17, 2008, listings on the Australia site must be paid for with one of the following: PayPal, Pay on pick up (i.e., paid for when picking up the item), or Visa/MasterCard (with transactions processed by PayPal). For information about the reasons for the changes, please see PayPal To Be A Required Payment Option for AU Sellers.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 565.
Starting in early June 2008, on the Italy site, Store Inventory Format (StoresFixedPrice)
items will be treated as basic fixed price (FixedPriceItem) items.
Please see the following location for more information: http://pages.ebay.it/ebaysirinnova/.
You can use GetCategoryFeatures to determine when this change has occurred and the categories to which it applies. Please also see Listing Types (Formats) and the documentation for ListingTypeCodeType.
Store subscribers and non-store subscribers can list
basic fixed price (FixedPriceItem) items with two new durations: 30 days and "Good Til Cancelled" (GTC),
in addition to the already existing durations of 3, 5, 7, and 10 days.
If a seller lists an item in the Store inventory format (StoresFixedPrice), and
then uses GetItem to retrieve the item data, the item will be returned as a Store inventory format (StoresFixedPrice) item.
Sellers can continue to list in the Store inventory format (StoresFixedPrice),
and if their existing Store inventory format listing is a "Good Til Cancelled" item,
it will be renewed as a Store inventory format item after the duration has expired.
If a seller relists or revises a Store inventory format item, it will be relisted or
revised as a Store inventory format (StoresFixedPrice) item.
Starting in early June 2008, on the Italy site, sellers can specify the duration for Gallery Featured items.
Use of this duration functionality is applicable only to
Gallery Featured items. When using AddItem, RelistItem, ReviseItem, or VerifyAddItem, specify the
duration of the Gallery Featured item in Item.PictureDetails.GalleryDuration. If the seller does not
specify the duration, a value of Lifetime is assumed.
An error is returned if a seller tries to downgrade from Lifetime to a limited duration.
However, a seller can change from a limited duration to Lifetime at any time.
After a limited duration of an item has expired, the item no longer is returned as Gallery Featured
in a GetItem call.
Use GetCategoryFeatures to determine if GalleryDuration is supported for the site and category you want to use. As of June 2, 2008, GalleryDuration will be available for all categories on the Italy site (site ID 101). Beginning in mid-September, 2008, the functionality will be available for sites such as US (site ID 0), DE (site ID 77), and UK (site ID 3).
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.
You can now specify whether you will accept buyers with more than two unpaid items or buyer policy violations within a specified time range, when you add, revise, relist, or verify a listing.
In order to make this change, the BuyerRequirements and MaximumUnpaidItemstrikes types have been deprecated and the following new types have been added: BuyerRequirementDetailsType, MaximumBuyerPolicyViolationsType, and MaximumUpaidItemStrikesInfoType.
You can still specify any of the other Buyer Requirements, such as LinkedPayPalAccount or VerifiedUser, by including them within the BuyerRequirementsDetails tags for a call, just as you included them previously within the BuyerRequirements tags.
This information comes back as part of the Item data for GetItem, GetItemRecommendations, GetBidderList, and GetSellerList.
The following code snippets show an example of BuyerRequrementDetails within an AddItem call.
Old (now deprecated):
<BuyerRequirements>
<MaximumUnpaidItemStrikes>true</MaximumUnpaidItemStrikes>
</BuyerRequirements>
New:
<BuyerRequirementDetails>
<MaximumUnpaidItemStrikesInfo>
<Count>2</Count>
<Period>Days_360</Period>
</MaximumUnpaidItemStrikesInfo>
<MaximumBuyerPolicyViolations>
<Count>2</Count>
<Period>Days_30</Period>
</MaximumBuyerPolicyViolations>
</BuyerRequirementDetails>
On the Australia site (site ID 15), by early June 2008, search results will include PayPal Buyer Protection. For information about PayPal Buyer Protection on the Australia site, see the following location: https://www.paypal.com/au/cgi-bin/webscr?cmd=p/gen/ua/policy_buyer_complaint-outside. For information about the API changes, see the Change History for GetSearchResults.
Starting in mid-2008, the eBay Germany, Austria, and Switzerland sites, the eBay US site, and Half.com will start migrating some catalogs to a new data provider. Initially, you may see changes in Media and Consumer Electronics catalogs. As part of this process, some products will undergo changes to their product details and pre-filled Item Specifics, some will be mapped to different products with similar information, and some will be deleted.
GetSearchResults, GetProducts, and GetSearchResultsExpress may return warnings if you pass in a product that has been modified or deleted.
During the migration period (typically 90 days), GetProducts and GetSearchResultsExpress will return a new ProductState field that specifies how a product changed or will change (if applicable).
The sell-side catalog search calls (the GetProductSearchResults family of calls) will continue to return the latest product information available, as they do today.
If you pass in an old product ID in the AddItem family of calls, eBay will attempt to map it to the latest product information available (with the latest pre-filled Item Specifics), and to return a warning that informs you of the change. If the product has been deleted and there is no replacement, the call will return an error.
Optionally, if you want to check the current status of an older product ID without searching for products, pass your item in GetItemRecommendations and check to see if the product includes a new ProductState field.
If you submit a scheduled listing before eBay changes a product in the catalog, your scheduled listing will not be affected. It will use the original product information you specified.
With ReviseItem, if you modify the listing but you don't pass in a new product ID, the listing will continue to use the original product information.
With RelistItem, if you don't pass in a new product ID, eBay will treat the request like any other new listing. That is, eBay will attempt to map the product to the latest product information available, drop pre-filled Item Specifics that are no longer applicable, and return a warning that informs you of the change. If the product has been deleted and there is no replacement, the call will return an error.
Good Till Canceled (GTC) listings are handled using the same logic as RelistItem when they relist.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 565 and Changed Functionality - 565.
The fields WatchCount and QuestionCount are returned if greater than 0. And SKU is returned if set. These facts were not previously mentioned in the documentation.
As noted in the Documentation Changes and Errata section for Version 561, one of the API Docs team's tasks is to improve samples for the Trading API and move them from the WebHelp to the Input/Output Reference. In Version 565 documentation, these were added: AddOrder Samples, GetSellerTransactions Samples, GetItemTransactions Samples.
Documentation Changes and Errata - 563
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
FeedbackSummaryType.SellerAverageRatingDetailArray |
Entity | Removed |
AverageRatingSummaryType |
Complex type | New |
BuyerGuaranteeEnabledDefinitionType |
Complex type | New |
BuyerRoleMetricsType |
Complex type | New |
BuyerSatisfactionDashboardType |
Complex type | New |
GetSellerDashboardRequestType |
Complex type | New |
GetSellerDashboardResponseType |
Complex type | New |
PayPalBuyerProtectionEnabledDefinitionType |
Complex type | New |
PolicyComplianceDashboardType |
Complex type | New |
PowerSellerDashboardType |
Complex type | New |
SearchStandingDashboardType |
Complex type | New |
SellerAccountDashboardType |
Complex type | New |
SellerDashboardAlertType |
Complex type | New |
SellerFeeDiscountDashboardType |
Complex type | New |
SellerRatingSummaryArrayType |
Complex type | New |
SellerRoleMetricsType |
Complex type | New |
BuyerSatisfactionStatusCodeType |
Enumerated type | New |
FeedbackSummaryPeriodCodeType |
Enumerated type | New |
ItemTypeCodeType |
Enumerated type | New |
PolicyComplianceStatusCodeType |
Enumerated type | New |
PreferredLocationCodeType |
Enumerated type | New |
SearchFlagCodeType |
Enumerated type | New |
SearchStandingStatusCodeType |
Enumerated type | New |
SellerAccountStatusCodeType |
Enumerated type | New |
SellerDashboardAlertSeverityCodeType |
Enumerated type | New |
SimpleItemSortCodeType |
Enumerated type | New |
CategoryFeatureType.BuyerGuaranteeEnabled |
Element | New |
CategoryFeatureType.PayPalBuyerProtectionEnabled |
Element | New |
FeatureDefinitionsType.BuyerGuaranteeEnabled |
Element | New |
FeatureDefinitionsType.PayPalBuyerProtectionEnabled |
Element | New |
FeedbackSummaryType.BuyerRoleMetrics |
Element | New |
FeedbackSummaryType.SellerRatingSummaryArray |
Element | New |
FeedbackSummaryType.SellerRoleMetrics |
Element | New |
GetAdFormatLeadsRequestType.EndCreationTime |
Element | New |
GetAdFormatLeadsRequestType.StartCreationTime |
Element | New |
ItemType.BuyerGuaranteePrice |
Element | New |
MyeBayFavoriteSearchType.BidCountMax |
Element | New |
MyeBayFavoriteSearchType.BidCountMin |
Element | New |
MyeBayFavoriteSearchType.CategoryID |
Element | New |
MyeBayFavoriteSearchType.Condition |
Element | New |
MyeBayFavoriteSearchType.Currency |
Element | New |
MyeBayFavoriteSearchType.EndTimeFrom |
Element | New |
MyeBayFavoriteSearchType.EndTimeTo |
Element | New |
MyeBayFavoriteSearchType.ItemSort |
Element | New |
MyeBayFavoriteSearchType.ItemType |
Element | New |
MyeBayFavoriteSearchType.ItemsAvailableTo |
Element | New |
MyeBayFavoriteSearchType.ItemsLocatedIn |
Element | New |
MyeBayFavoriteSearchType.MaxDistance |
Element | New |
MyeBayFavoriteSearchType.PaymentMethod |
Element | New |
MyeBayFavoriteSearchType.PostalCode |
Element | New |
MyeBayFavoriteSearchType.PreferredLocation |
Element | New |
MyeBayFavoriteSearchType.PriceMax |
Element | New |
MyeBayFavoriteSearchType.PriceMin |
Element | New |
MyeBayFavoriteSearchType.Quantity |
Element | New |
MyeBayFavoriteSearchType.QuantityOperator |
Element | New |
MyeBayFavoriteSearchType.QueryKeywords |
Element | New |
MyeBayFavoriteSearchType.SearchFlag |
Element | New |
MyeBayFavoriteSearchType.SellerBusinessType |
Element | New |
MyeBayFavoriteSearchType.SellerID |
Element | New |
MyeBayFavoriteSearchType.SellerIDExclude |
Element | New |
MyeBayFavoriteSearchType.SortOrder |
Element | New |
SellerType.TransactionPercent |
Element | New |
SiteDefaultsType.BuyerGuaranteeEnabled |
Element | New |
SiteDefaultsType.PayPalBuyerProtectionEnabled |
Element | New |
TransactionType.BuyerGuaranteePrice |
Element | New |
BuyerProtectionCodeType.NoCoverage |
Enum | New |
FeatureIDCodeType.BuyerGuaranteeEnabled |
Enum | New |
FeatureIDCodeType.PayPalBuyerProtectionEnabled |
Enum | New |
ShippingServiceCodeType.AU_RegisteredParcelPost |
Enum | New |
ShippingServiceCodeType.AU_RegisteredParcelPostPrepaidSatchel3kg |
Enum | New |
ShippingServiceCodeType.AU_RegisteredParcelPostPrepaidSatchel500g |
Enum | New |
ShippingServiceCodeType.AU_RegisteredSmallParcel |
Enum | New |
ShippingServiceCodeType.FreightOtherShipping |
Enum | New |
ShippingTypeCodeType.FreightFlat |
Enum | New |
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 563.
Store owners can create promotional sales to offer free shipping. Previously, promotional sales could only be created for price discount sales. Store owners can use the new PromotionalSaleType in SetPromotionalSale to create a price discount only sale, a free shipping only sale, or a price discount and free shipping sale.
Auction and auction/Buy It Now listings can be added to free shipping only sales. Free shipping sales for auction and auction/Buy It Now listings are supported for US and international sites, with the following exceptions: DE (77), AU (15), CH (193), AT (16), UK (3), and IE (205).
For more information, see Putting Store Items On Sale.
On the Australia site (site ID 15), by early June 2008, enhancements to PayPal Buyer Protection will be available. For information about PayPal Buyer Protection on the Australia site, see the following location: https://www.paypal.com/au/cgi-bin/webscr?cmd=p/gen/ua/policy_buyer_complaint-outside. For information about the API changes, see the change histories for the following affected calls: GetBidderList, GetCategoryFeatures, GetItem, GetItemTransactions, GetOrderTransactions, GetSellerList, and GetSellerTransactions.
Your Seller Dashboard provides a brief summary of your status as an eBay seller. This status information can help you monitor your selling performance and keep your account in good standing.
A new API call, GetSellerDashboard, will be available in production in late May 2008. It will give you a quick view of the following information:
We are providing the schema and documentation for GetSellerDashboard early to help you plan how to modify your applications. Additional details may be provided when this functionality becomes available in production.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
As announced back in February, beginning in May 2008, the eBay Feedback system will evolve to improve the accuracy and accountability of feedback given to our buyers and sellers. A few API calls have been updated to account for these changes.
The GetUser call now returns a new element called SellerInfo.TransactionPercent. This value is calculated by taking the ratio of the number of times a seller has sold successfully and the number of times a seller has bought an item throughout the past 365 days. This field is used to gather the seller's activity percentage.
The GetFeedback call now returns these three elements:
Each of these elements is added to support the changes to the way members can leave feedback for one another. This introduces a few new types to the API, used to capture the metrics of buyer and seller feedback:
For more information about the new types and elements, see the GetFeedback and GetUser I/O Call Reference.
The LeaveFeedback call will no longer let a seller leave a Neutral or Negative feedback for a buyer. Also, if a member attempts to leave feedback after 60 days from the end of the transaction, an error is returned. The existing error for leaving feedback after 90 days will remain the same. For buyers, they will not be able to leave Neutral or Negative feedback within 7 days from the end of the transaction, for active PowerSellers who have been on eBay for 12 months.
Note that in New Features - 549, buyers and sellers can earn repeat feedback from other members. As for 563 release, the logic behind unique and repeat feedback is changed to include repeat feedback only and all other feedback will be retroactively recalculated for each member. Further details can be found in the Upcoming Changes to Feedback announcement under the Repeat Feedback Credit section.
As of the first week of June, you can use two new fields in GetAdFormatLeads (StartCreationTime and EndCreationTime) to retrieve only those leads for a user that fall within a specified time window.
The eBay US seller who uses a freight service other than FreightQuote.com can either select "other freight" on the eBay Web site or can set ShippingType to FreightFlat (a new value in ShippingTypeCodeType) when listing the item. Listings using a non-FreightQuote.com service will return a ShippingService value of FreightOtherShipping (a new value in ShippingServiceCodeType). The seller who specifies FreightFlat cannot set ShippingServiceCost and cannot set ShippingService.
For a broader discussion of freight, see the "Shipping Types" discussion in Shipping.
Affected calls: AddItem family of calls, GetItem, GetItemTransactions, GetItemShipping.
GetMyeBayBuying now returns each search element within a user's Favorite Searches. The search name, search query, and search elements, such as QueryKeywords, SortOrder, and Condition are returned for each Favorite Search. The search elements that are returned by this call can be used as input for the Shopping API FindItemsAdvanced request. Using the Shopping API to find the search elements can result in faster search times.
You can also paste the Search Query response, that comes back as a URL, into a browser to re-play the Favorite Search using the Trading API.
The following types (that were previously only in the Shopping API) have been added to the Trading API to support this feature: SimpleItemSortCodeType, ItemTypeCodeType, SearchFlagCodeType, and PreferredLocationCodeType.
The MyeBayFavoriteSearchType has been modified to include elements that match the input values for the FindItemsAdvanced call.
By the beginning of May 2008, the response for Search related calls will not return an item with a listed price that is less than the Minimum Listing Amount (MLA) threshold on the eBay site where the item was originally listed.
The following calls are affected by this change:
The MLA varies by site ID (e.g. $0.99 on the US site and 1 euro on the UK site) and is an additional transparent filter that will not affect any existing functionality of the affected calls. The MLA filtering will automatically be applied to the following listing formats for items returned in the response of the calls:
However, MLA filtering will not apply to Chinese Auction and Chinese Auction + BIN Format for listings lasting 6 days or more.
Whenever the response of these calls returns items listed on another (international) eBay site, the price of those items is first converted to the local country currency and is then compared to the local MLA threshold.
The MLA will be applied across all eBay sites, including eBay Express and Motors (does not include Half.com).
(Prior announcements had set this as end of April.) Starting in mid May 2008, for multi-quantity Store Inventory Format listings and for multi-quantity Fixed Price listings, a seller can revise all shipping details of the listing (except for sales tax and for shipping type of Freight) for all unsold items. This applies to both domestic and international shipping. Checkout is not affected for those who bought items prior to the seller's shipping changes--the shipping details that were in effect at the time of purchase are used for that buyer at the time of checkout.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 563 and Changed Functionality - 563.
The eBay Web site has no way of specifying or changing the "ThirdPartyCheckout" field. Further, consequences related to ThirdPartyCheckout are different on the site for relisting and revising an item: site:
As noted in the Documentation Changes and Errata section for Version 561, one of the API Docs team's tasks is to improve samples for the Trading API and move them from the WebHelp to the Input/Output Reference. In Version 563 documentation, these were added: AddItem Samples, RelistItem Samples.
Documentation Changes and Errata - 561
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
CharitySellerStatusCodeType.Migrated |
Entity | Removed |
CharitySellerStatusCodeType.MigratedWithGiftAid |
Entity | Removed |
CharityAffiliationDetailType |
Complex type | New |
CharityAffiliationDetailsType |
Complex type | New |
AdFormatLeadType.Answer1 |
Element | New |
AdFormatLeadType.Answer2 |
Element | New |
AdFormatLeadType.ExternalEmail |
Element | New |
AdFormatLeadType.FinancingAnswer |
Element | New |
AdFormatLeadType.PurchaseTimeFrame |
Element | New |
AdFormatLeadType.TradeInMake |
Element | New |
AdFormatLeadType.TradeInModel |
Element | New |
AdFormatLeadType.TradeInYear |
Element | New |
SellerType.CharityAffiliationDetails |
Element | New |
Starting at the end of April 2008, UK and Germany eBay Express will be shutdown. The sites will no longer be accessible to all users and visitors. Those who try to access the sites will be redirected to a holding page to explain the shutdown. All users previously registered on UK or Germany eBay Express will have their registered status revoked and become ineligible for UK or Germany eBay Express.
For revoked seller's items, any active Express only items will be ended and moved to the unsold items folder and the full insertion fee credit will be issued to the seller. Any scheduled Express only items are also moved to the unsold items folder but not credited since the items were never charged. All other listings in any other format owned by revoked UK or Germany Express sellers will remain on the site as they were.
Beginning in May 2008, existing charity sellers will no longer be considered registered charity sellers until they agree to the new Terms & Conditions and create a donation account on eBay. After this date, any charity seller that tries to sell an item as a donation will be taken to the new Terms & Conditions page. When accepted, sellers will be marked as accepted and can continue being registered charity sellers as before.
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 561.
The lead form for vehicle classified listings is being improved to allow prospective buyers to leave more information. New fields have been added to gather the following types of information about prospective buyers:
Buyers do not need to log in to use the lead form.
For more information on how to use the GetAdFormatLeads call, see Local Market Listings in the "eBay Motors" chapter of the eBay Trading Web Services Guide.
For more information on the input and output fields for GetAdFormatLeads call see GetAdFormatLeads in the Input/Output Reference.
PayPal is now a supported payment method for the Hong Kong (201), Singapore (216), Malaysia (207), and Philippines (211) sites. Sellers who offer PayPal as a payment option in their eBay listings must comply with the PayPal Payments Policy.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
The User.CharityAffiliations element is being deprecated as of the 561 release, and is replaced by the User.SellerInfo.CharityAffiliationDetails element as the charity details container for sellers. The GetUser call is the only call affected by this change. It no longer returns User.CharityAffiliations in its response and instead returns User.SellerInfo.CharityAffiliationDetails.
The new User.SellerInfo.CharityAffiliationDetails container will have a child element, CharityAffiliationDetail, which contains three fields:
For more information on how to use these fields, please refer to CharityAffiliationDetailType.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 561 and Changed Functionality - 561.
One of the API Docs team's tasks is to improve samples for the Trading API and move them from the WebHelp to the Input/Output Reference, as you can see for a couple of the first to be refined and moved: ReviseItem Samples, GetItemShipping Samples. In coming months, more and more of the samples will be improved and moved to this new home, as the API Docs team works toward the Input/Output Reference being the consolidated reference for calls.
The documentation previously stated that Item.ListingDetails.BuyItNowAvailable was only returned for Dutch auctions on the eBay Germany site. This is no longer true. Currently, BuyItNowAvailable is also returned for Chinese auctions on US, UK, AU, and other sites, as long as the Buy It Now option is still available for a listing.
On some sites, the Buy It Now price for a Chinese auction may remain available for listings in certain categories even after a bid is placed. See the Longer Lasting Buy It Now community board post for more details and the latest list of eBay US categories that support this behavior. The eBay Spain site supports this behavior for all categories.
Documentation Changes and Errata - 559
For a current list of known issues, see System Announcements and the Knowledge Base.
These calls were added, modified, deprecated, or affected by documentation changes in this release. The changes are described below as well as in each call's Change History.
No new calls in this release.
Schema changes in pink (for example, SomeType.Somedata) are for future use. Monitor upcoming release notes for descriptions of their purpose and use.
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 |
|---|---|---|
BusinessSellerDetailsType |
Complex type | New |
AddressType.FirstName |
Element | New |
AddressType.LastName |
Element | New |
ItemType.BusinessSellerDetails |
Element | New |
VATDetailsType.VATID |
Element | New |
VATDetailsType.VATSite |
Element | New |
ListingTypeCodeType.Shopping |
Enum | New |
Starting in late April 2008, all sellers on the eBay UK site are required to offer PayPal on their listings. For more information and for links to other recent, PayPal-related announcements, please see the following locations:
See the System Announcements for bug fixes related to this release. For documentation-related issues, see the Documentation System Announcements.
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 - 559.
Beginning in early May 2008, you can use the International Site Visibility feature to make listings available in the default search results of another site.
The International Site Visibility feature is a listing upgrade that US, Canada, UK, and Ireland sellers can choose when they list an item on their primary listing site.
For information about the International Site Visibility feature, see the following recent Announcement Board posts:
For more information about the additions to the API, see Making Listings Available by Default on Another Site.
GetItem now returns the seller's information (in a business card format) if the seller's SellerBusinessCodeType is set to 'Commercial'. This is only applicable for sites where Business Seller options are supported.
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.
Starting April 8, 2008, new users who are listing for the first time (in selected categories on the US site) must specify at least one domestic shipping service and associated cost for this and all subsequent listings.
This applies to a category if GetCategoryFeatures returns true for Category.ShippingTermsRequired.
This change affects AddItem, VerifyAddItem, ReviseItem and RelistItem.
The Item.PictureDetails.PhotoDisplayType.PicturePack enum in AddItem, ReviseItem and RelistItem calls have the following changes:
These functionality changes apply to all sites that offer PicturePack, including US Motors, except for the Netherlands (site ID 146) site. On the NL site only, requests selecting PicturePack will be replaced with Item.PictureDetails.PhotoDisplayType.SuperSize, as NL already offers free bundled pictures. Listings on the NL site that specified PicturePack prior to 559 are not automatically upgraded to SuperSize (i.e. when using ReviseItem) after the change is in effect.
The Item.PictureDetails.PhotoDisplayType.SuperSize enum in AddItem and related calls have the following changes:
These functionality changes apply to all sites that support the SuperSize feature, except for sites that automatically upgrade SuperSize to PicturePack, including US Motors Parts & Accessories Category and US (site ID 0), CA (site ID 2) and CAFR (site ID 210) sites.
For AddItem and RelistItem, the Picture Show photo display options for creating a slide show in your Gallery are no longer available. For cases where an item has PictureShow selected, the PhotoDisplayType is replaced by the default value of None in the response if the requested PhotoDisplayType is SiteHostedPictureShow or VendorHostedPictureShow. If the requested PhotoDisplayType is SuperSizePictureShow, the response returns SuperSize. For ReviseItem, if PictureShow was added before 559, the PhotoDisplayType will not be modified. Otherwise, the same PhotoDisplayType replacement occurs.
Beginning on version 559, the green camera icon will no longer be available for use as a listing's gallery thumbnail in the search results on the following category and sites: US (site id 0), US Motors Parts & Accessories Category, CA (site id 2), CAFR (site id 210), FR (site id 71), NL (site id 146), ES (site id 186), and IT (site id 101). That is, a listing that has set the first PictureURL in the PictureURL array to the null-image URL (http://pics.ebay.com/aw/pics/dot_clear.gif) will no longer display the green camera icon in the search results for these sites starting on 559.
Depending on other available images included in the request and the site to display the listing, eBay will attempt to select a Gallery image source whenever the null-image URL has been specified, and in some cases will use an available eBay stock photo as the Gallery thumbnail (see Including Pictures in the Search Results Gallery for more information on the Gallery image selection process). If a valid image cannot be found, the Gallery thumbnail for the listing will display a blank in the search results. This change will allow sellers to create listings that directly benefit from the free basic Gallery feature available on most sites (see Changed Functionality - 551 for more information on free Gallery).
As of March 2008, all digital listings (downloadable goods) selling on eBay US are required to be listed in a Classified Ad format within the Everything Else > Information Product category. The previous digital delivery feature is disabled as of March 28, 2008. AddItem and related calls using the DigitalDeliveryDetails fields will fail. Sellers who wish to continue to use the Trading API to offer digital goods can do so by setting the value of Item.ListingType to LeadGeneration and Item.ListingSubtype2 to ClassifiedAd instead (and list in the Everything Else > Information Product category).
Using the Classified Ads format, sellers receive a 30-day ad at a fixed price. This solution enables sellers to continue to market their digital goods on eBay; however, because Classified Ad listings are a lead generation tool and do not result in transactions that go through eBay, Feedback cannot be exchanged between buyer and seller.
All digital delivery fields will be removed from the schema in a future release, and the documentation will be updated with more details at that time.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 559 and Changed Functionality - 559.
The section on listing an item with product data in the Trading API Guide has been updated to state that LookupAttributeArray is only supported for items on the eBay US site (site ID 0). The description of LookupAttributeArray has also been updated in the Input/Output Reference.
This documentation and the API may only be used in accordance with the eBay Developers Program and API License Agreement.
© 2005–2010 eBay Inc. All rights reserved.
eBay and the eBay logo are registered trademarks of eBay Inc.
All other brands are the property of their respective owners.