Information about the schema location is in the Schema Location section of the Making an API Call topic.
Are you just getting started with the Shopping API? The following describes how to join the eBay Developers Program:
| Q3 2008 | Q2 2008 | Q1 2008 | Q4 2008 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Version | Release Date | Version | Release Date | Version | Release Date | Version | Release Date | ||||
| 583 | 2008-9-17 | 571 | 2008-6-25 | 557 | 2008-3-19 | 545 | Not Released | ||||
| 581 | 2008-9-3 | 569 | 2008-6-11 | 555 | 2008-3-5 | 543 | 2007-12-18 | ||||
| 579 | 2008-8-20 | 567 | 2008-5-28 | 553 | 2008-2-20 | 541 | Not Released | ||||
| 577 | 2008-8-6 | 565 | 2008-5-14 | 551 | 2008-2-6 | 539 | 2007-11-14 | ||||
| 575 | 2008-7-23 | 563 | 2008-4-30 | 549 | 2008-1-23 | 537 | 2007-10-31 | ||||
| 573 | 2008-7-9 | 561 | 2008-4-16 | 547 | 2008-1-9 | 535 | 2007-10-17 | ||||
| 559 | 2008-4-2 | 533 | 2007-10-3 | ||||||||
These release notes go back four quarters. For older release notes, see the Release Notes archive.
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.
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 |
|---|---|---|
ReviewSortCodeType |
Enumerated type | New |
FindReviewsAndGuidesRequestType.ReviewSort |
Element | New |
FindReviewsAndGuidesRequestType.SortOrder |
Element | New |
PopularSearchesType.CategoryName |
Element | New |
PopularSearchesType.CategoryParentName |
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 - 577.
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.
Now there are two new fields that allow you to sort the results for the FindReviewsAndGuides call. If you set the ReviewSort field to CreationTime, you can sort the Reviews and Guides according to the time they were created. Use SortOrder to retrieve the Reviews and Guides in Ascending or Descending order.
FindPopularSearches now returns CategoryParentName and CategoryName, in addition to CategoryID, CategoryParentID, and QueryKeywords, related searches and other information. These two new fields were added so that users will no longer have to make a second GetCategories call to find out the category name.
When using the FindItemsAdvanced call with Motors listings, you can specify a SubTitle in the ItemSpecifics field. Other Item Specifics for Motors include: Mileage, Year, and Condition.
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.
None for this release.
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.
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 - 575.
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 - 575 and Changed Functionality - 575.
The documentation for FindHalfProducts has been modified to include that ItemCount is only returned when ProductID is used in the search request and the IncludeSelector is set to Items or Details. It is not returned if you include a QueryKeyword in your request.
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 |
|---|---|---|
DigitalDeliveryMethodCodeType |
Entity | Removed |
SimpleItemType.DigitalDeliveryMethod |
Entity | Removed |
SimpleItemType.DigitalDeliveryRequirements |
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 - 573.
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.
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. All related digital delivery fields have been removed from the schema. FindItemsAdvanced and GetSingleItem no longer return the DigitalDeliveryMethod or DigitalDeliveryRequirements fields.
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 - 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.
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 - 571.
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 - 571 and Changed Functionality - 571.
None for this release.
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.
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 - 569.
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.
You can now search for items within a specific postal code or within multiple postal codes using the MaxDistance and PostalCode elements of the FindItemsAdvanced call.
These two elements are used in combination as follows:
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 FindItemsAdvanced topic has been updated to state that the following is not functional: specifying an ItemSort value of EndTime with a SortOrder of Descending.
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.
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 - 567.
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 - 567 and Changed Functionality - 567.
None for this release.
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 |
|---|---|---|
ExcludeFlagCodeType |
Enumerated type | New |
ProductStateCodeType |
Enumerated type | New |
SellerLevelCodeType |
Enumerated type | New |
CatalogProductType.ProductState |
Element | New |
FindItemsAdvancedRequestType.DescriptionSearch |
Element | New |
FindItemsAdvancedRequestType.ExcludeFlag |
Element | New |
FindItemsAdvancedRequestType.FeedbackScoreMax |
Element | New |
FindItemsAdvancedRequestType.FeedbackScoreMin |
Element | New |
FindPopularItemsRequestType.MaxEntries |
Element | New |
FindProductsRequestType.CategoryID |
Element | New |
GetMultipleItemsRequestType.IncludeSelector |
Element | New |
SimpleItemType.AutoPay |
Element | New |
SimpleUserType.SellerLevel |
Element | New |
SearchFlagCodeType.AutoPay |
Enum | New |
SearchFlagCodeType.Featured |
Enum | New |
SearchFlagCodeType.SuperFeatured |
Enum | New |
SimpleItemSortCodeType.BestMatchPlusEndTime |
Enum | New |
SimpleItemSortCodeType.BestMatchPlusPrice |
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 - 565.
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.
Many new search options have been added to FindItemsAdvanced. You can now search for: a seller's positive feedback percentage, item location, items that are Featured or SuperFeatured, Description, CharityID, AutoPay, Proximity, or Postal Code (with a specified distance range).
You can filter all FindItemsAdvanced results by Seller Feedback Score or AutoPay (which you can use to exclude results). In addition, you can filter your Best Match results using a range of end times or a range of prices.
You can now see up to 100 items in the FindPopularItems results and up to 20 items in the GetMultipleItems results.
GetSingleItem and GetMultipleItems now include a Text Description option in the Include Selector that returns only the text of the item description (without any mark-up, JavaScript, or image tags). The AutoPay field is now returned as part of the default Include Selector results. GetMultipleItems also lets you return item Details using the Include Selector.
FindProducts now allows you to filter your results by CategoryID and sort your results by popularity.
SellerLevel is now included in the default Include Selector results for GetUserProfile.
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 Item Specifics, some will be mapped to different products with similar information, and some will be deleted.
FindProducts, FindItemsAdvanced, and FindReviewsAndGuides may return warnings if you pass in a product that has been modified or deleted.
During the migration period (typically 90 days), FindProducts will return a new ProductState field that specifies how a product changed or will change (if applicable).
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.
A previous version of this release note mentioned that you could perform a postal code search within a set of postal codes and without a distance range. The Call Reference information may still include this error, but it will be updated and corrected in the next release.
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.
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 - 563.
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.
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).
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.
None for this release.
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.
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 - 561.
The FindHalfProducts call has been updated to return additional data for query searches. When you specify QueryKeywords in the request, the response includes Products.Product.ItemCount and a new fields, Products.Product.MinPrice. Products.Product.MinPrice gives the minimum price for all active items listed under the given product.
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 - 561 and Changed Functionality - 561.
None for this release.
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 |
|---|---|---|
AddressType |
Complex type | New |
BusinessSellerDetailsType |
Complex type | New |
VATDetailsType |
Complex type | New |
SimpleItemType.BusinessSellerDetails |
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 - 559.
GetSingleItem 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.
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 - 559 and Changed Functionality - 559.
None for this release.
Documentation Changes and Errata - 557
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 - 557.
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.
For eBay, the affiliate tracking URLs of Commission Junction will stop tracking starting May 1st, 2008. For information about affiliate tracking, see Affiliate URL Parameters and HTTP Header Values.
If you are a Commission Junction member, please join the eBay Partner Network. The eBay Partner Network replaces Commission Junction as a service provider for the eBay Affiliate Program. References in the documentation to Commission Junction have been changed to reference eBay Partner Network (https://www.ebaypartnernetwork.com).
Please migrate your affiliate account and all affiliate tracking to eBay Partner Network between April 1st and May 1st. For migration, please see Affiliate Migration to eBay Partner Network.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 557 and Changed Functionality - 557.
None for this release.
Documentation Changes and Errata - 555
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 |
|---|---|---|
ShippingDetailsType.CODCost |
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 - 555.
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.
By April, on the Italy site (site ID 101), the cost of cash-on-delivery shipping can be returned by the GetShippingCosts call.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 555 and Changed Functionality - 555.
A sample has been added to FindItemsAdvanced illustrating the use of the Value field in the URL request format. The field is not used in the XML request format.
Documentation Changes and Errata - 553
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.
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 - 553.
You can test Shopping API calls using the Sandbox environment (that is,
using the http://open.api.sandbox.ebay.com/shopping? endpoint).
For more information, see the
Testing Overview section of the Making an API Call topic.
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 January 29 announcements included the announcement that Best Match would become the default for search results in March 2008. The documentation for FindItems and FindItemsAdvanced has been updated with this change. For more information, see the eBay General Announcement Board for the announcements of January 29, 2008.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 553 and Changed Functionality - 553.
The documentation has been updated to state that if you specify an output format of JSON or NV (Name-Value pair), then instances of some wrappers of primitive types, such as instances of AmountType and DistanceFromBuyer, will include a Value field.
For example, in the FindItemsAdvanced NV response, here is an example of a possible instance of ShippingServiceCost (which is of type AmountType):
Item(1).ShippingCostSummary.ShippingServiceCost.Value=3.5.
Documentation Changes and Errata - 551
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.
Please see the eBay General Announcement Board for the announcements of January 29, 2008, about upcoming changes to feedback, as well as other changes.
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 - 551.
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 - 551 and Changed Functionality - 551.
None for this release.
Documentation Changes and Errata - 549
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 |
|---|---|---|
FeedbackHistoryType.UniqueNeutralFeedbackCount |
Element | New |
Please see the eBay General Announcement Board for the announcements of January 29, 2008, about upcoming changes to feedback, as well as other changes.
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 - 549.
Starting in early February 2008, the eBay Feedback system will allow buyers and sellers to affect each other's Feedback score by one point each week. This will encourage sellers and buyers to engage in repeat transactions with one another.
Currently, a member can impact another member's Feedback score at most +1 or -1 in their lifetime. After the upcoming changes a member will be able to impact another member's Feedback score at most +1 or -1 in a calendar week. Repeat positive or negative Feedback score in a week will not be counted, even if they have more than one transaction between them in that week.
GetUserProfile call will be changed as following:
For more information, see Upcoming Changes to Feedback.
This section describes logical or functional changes that have been made to existing functionality, including new code list values and/or changes in validation rules.
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 - 549 and Changed Functionality - 549.
The documentation has been revised to state that in cases where a comma can be embedded in a string, an array index must be used to prevent the comma from acting as a delimiter. For more information, see the Specifying Arrays in Requests section of the Making an API Call topic.
Documentation Changes and Errata - 547
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.
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 - 547.
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 - 547 and Changed Functionality - 547.
For the FindItemsAdvanced call, you must specify a QueryKeyword if you set the IncludeSelector value to ItemSpecifics.
No 545 schema was released.
No new calls in this release.
No changed calls in this release.
Documentation Changes and Errata - 543
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.
There will not be a 545 schema release. The 547 schema and API documentation will be available by January 14, 2008.
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 - 543.
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 - 543 and Changed Functionality - 543.
None for this release.
No 541 schema was released.
Documentation Changes and Errata - 539
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 |
|---|---|---|
| No schema changes in this release | Not applicable | Not applicable |
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 - 539.
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 - 539 and Changed Functionality - 539.
None for this release.
Documentation Changes and Errata - 537
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 | Schema component | Nature of Change |
|---|---|---|
BuyerPaymentMethodCodeType.PaisaPayEscrowEMI |
Enum | New |
PaymentMethodSearchCodeType.PaisaPayEscrowEMI |
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 - 537.
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.
In December 2007, the PaisaPayEscrowEMI payment method will be available for the India site (site ID 203).
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 537 and Changed Functionality - 537.
None for this release.
Documentation Changes and Errata - 535
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 | Schema component | Nature of Change |
|---|---|---|
CharityStatusCodeType |
Enumerated type | New |
CharityType.CharityListing |
Element | New |
CharityType.CharityName |
Element | New |
CharityType.CharityNumber |
Element | New |
CharityType.DonationPercent |
Element | New |
CharityType.LogoURL |
Element | New |
CharityType.Mission |
Element | New |
CharityType.Status |
Element | New |
SimpleItemType.MinimumToBid |
Element | New |
SimpleItemType.ProductID |
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 - 535.
In this release, some useful new fields are returned in the GetSingleItem when you specify the Details in the
IncludeSelector field. Specifically, the call now returns information about the minimum amount required to bid on the item, a product ID for the item, and details
about any nonprofit charity that the seller may have selected to benefit from the sale.
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.
The response for GetItemStatus now includes the HighBidder and ReserveMet fields, as shown below:
<GetItemStatusResponse xmlns="urn:ebay:apis:eBLBaseComponents"> <Timestamp>2007-10-18T03:03:32.015Z</Timestamp> <Ack>Success</Ack> <Build>e535_core_Bundled_5514987_R1</Build> <Version>535</Version> <Item> <ItemID>270000490370</ItemID> <EndTime>2007-10-04T02:05:18.000Z</EndTime> <ConvertedCurrentPrice currencyID="USD">1239.0</ConvertedCurrentPrice> <HighBidder><UserID>1191463482046_buyerx15</UserID></HighBidder> <ListingStatus>Ended</ListingStatus> <ReserveMet>true</ReserveMet> </Item> </GetItemStatusResponse>
Note that like many API calls, GetItemStatus only returns fields that are appropriate for the item. For instance, if the item ended with no bids, the HighBidder field would not be included in the response.
This section lists additional documentation changes and corrections that were made with this release and that are not already mentioned in New Features - 535 and Changed Functionality - 535.
The usage information for the GetItemStatus call has been updated to include the maximum limit of 10 items per call.
The usage information for the GetCategoryInfo call has been updated with a descripton of how to build a full or partial category hierarchy.
Documentation Changes and Errata - 533
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 | Schema component | Nature of Change |
|---|---|---|
GetCategoryInfoRequestType |
Complex type | New |
GetCategoryInfoResponseType |
Complex type | New |
GeteBayTimeRequestType |
Complex type | New |
GeteBayTimeResponseType |
Complex type | New |
ReturnPolicyType |
Complex type | New |
CategoryType.CategoryIDPath |
Element | New |
CategoryType.CategoryNamePath |
Element | New |
CategoryType.LeafCategory |
Element | New |
SimpleItemType.ReturnPolicy |
Element | New |
SimpleUserType.PositiveFeedbackPercent |
Element | New |
SimpleUserType.ReviewRank |
Element | 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 - 533.
If you are using URL-style input or Name-Value Pair input, repeatable fields now can be expressed using a comma-separated format. For example, for ItemID in GetItemStatus, you can specify &ItemID=123456789012,223456789012,323456789012. If you are specifying only one value, you can specify, for example, &ItemID=123456789012. For more information, see the samples in the calls with repeatable fields, such as GetItemStatus.
Formerly, when URL-style or Name-Value Pair input included a repeatable field, an array index was required (e.g., for ItemID in GetItemStatus, you had to specify input such as &ItemID(0)=123456789012&ItemID(1)=223456789012). The array index was required even if you passed in only one value. The array index is still supported, but it is recommended that you use the comma-separated format.
If you use the callbackname parameter in a request for data in JSON format, the response data is wrapped in a call to a function. The name of the function is the value you specified for the parameter.
For example, if you use the FindItems call and you specify callbackname=myfunction, then the FindItems response data will be wrapped in a call to a myfunction function.
For more information about the callbackname parameter and the corresponding header value, see the Standard URL Parameters and HTTP Header Values section of the Making an API Call topic.
You can use GeteBayTime to obtain the official eBay system time in GMT.
If an item has a return policy, you can use
GetSingleItem to obtain
the details about the policy. If you specify Details in the
IncludeSelector field, a ReturnPolicy container
has fields with information about the policy such as how a refund will be made (e.g., as an exchange)
and how soon an item must be returned for a refund.
You can use GetSingleItem to obtain the percentage value of a sellers's positive feedback.
You can use GetCategoryInfo to retrieve category information for a specific CategoryID (such as which categories it contains, what level each sub-category is within the hierarchy, and whether the sub-categories are leaf categories (bottom-level categories where items can be listed).
Now you can specify that you want the Shopping API to return the values from the latest schema version instead of returning 'CustomCode' for values that are from a newer schema than the one you specified in version (or in X-EBAY-API-VERSION). The Shopping Web Services - Making an API Call document contains the table that describes URL parameters and HTTP values.
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 - 533 and Changed Functionality - 533.
None for this release.
Back to top© 2007 eBay Inc. All rights reserved.
