Search Call Deprecations and the Java and .NET SDKs

The deprecation of GetSearchResults and GetCategoryListings will affect users of the Java and .NET SDKs. Users of current versions of these SDKs will continue to have access to the deprecated calls and types until October 11, 2011. Users who adopt newer versions of these SDKs, starting with the April 28, 2011, point release, will not have access to the deprecated types. The April 28 release will include samples that show how to access the search functions in the Finding API from the Trading SDKs.

April 18, 2011 in Developer Community, Documentation, Finding API, Trading API | Permalink

Finding API Migration

The Developers Program launched the Finding API in July 2009. Today Finding API is successfully serving over 130 millions of requests daily. We are ready for our next critical milestone – support all developers to fully migrate to Finding API to take advantage of the eBay’s next generation search technology used to power the eBay site search ; and deprecate Trading APIs: GetSearchResults and GetCategoryListings, and Shopping APIs: FindItemsAdvanced and FindItems. These APIs will stop working after October 2011.

To better support developers’ migration, asks and needs, we have been focusing on Finding API for new and enhanced features, as well as technical support. Meanwhile the deprecation of Trading and Shopping Search APIs has started since January 2011. Although those four API calls are still working till October, developers should have noticed that the deprecated API calls and related schema have been removed from the public WSDL and XSD files. Related documentation has also been removed. These calls are also being removed from SDKs.  For adoption of newer version SDKs after April 2011, the deprecated types will no longer be accessible. A warning message will be returned by these API calls after June 2011, indicating the API is scheduled to be removed. Your application might be broken if it doesn’t follow eBay requirements for error handling. The search capabilities provided by these calls are supported in the Finding API. If you're building new search applications, start with the Finding API. If you have applications that use these calls, please migrate your item search functions to the Finding API.

 

Why Finding API?

The Finding API leverages eBay’s next generation search technology and have been designed to provide greater flexibility, better performance and scalability. Increased search relevancy and parity with the eBay site search features are some of the highlights of the new API. The latest Best Match and Fitment algorithms are available in Finding API. A series of benchmark testing has been conducted that shows on par performance of Finding API to the Shopping API (FindItemsAdvanced & FindItems); and significant improvement over the Trading API (GetSearchResults & GetCategoryListings).

The following are the functionalities and features added by Finding API for item searches:

1.       Retrieve aspect histograms and filter by aspects and/or domains – supply data by item attributes which enables eBay site alike left navigation as well as search refinement by applying constraints aligned with eBay search classification.

2.       Support new search capabilities:

  • Item Condition histogram and filters
  • Restrict searches to as many as 3 categories at a time
  • Expedited Shipping filters
  • Top-Rated Sellers Only filter
  • Returns Accepted Only filter

 

3.       Image Search API (findItemsByImage): expend eBay’s capabilities in fashion to developers for the “More Like This” functionality.

4.       Three sizes of gallery image: 140x140, 96x96, 80x80 that users can choose to use based on their application’s needs.

As our commitment to the Developer Community, we are always working continuously and diligently to enable the latest, high performance, world-class eBay search technology and features to Finding API. Enhancements to picture URL, Multi-variations, LocatedIn etc. filters and more will be released in May.

 

How to Migrate to Finding API?

The following migration guides map input and output fields for GetSearchResults in the Trading API and FindItemsAdvanced in the Shopping API to the corresponding input and output fields in findItemsAdvanced in the Finding API:

Please contact us for questions or more information on Finding API or migration.

 

 

April 7, 2011 in Affiliates, Critical Notes from Tech Support, Developer Website, Documentation, Finding API, Shopping API, Trading API | Permalink

Rate Limit Changes to Shopping, Finding, and Merchandising API

To manage your call limits better, eBay is changing the basis for rate limiting API usage for the Shopping, Finding and Merchandising APIs. Starting March 1, 2011, call usage will be measured by application instead of IP address. The call counts will be aggregated for your application based on the AppID used to make the request, rather than the IP address from which the request is coming.

What does this mean to you?

If your application is making more than 5,000 calls a day, go through the compatible application check to get your call limits increased to prevent any disruption to your application.

January 7, 2011 in Best Practices, Critical Notes from Tech Support, Developer Community, Finding API, Merchandising API, Shopping API | Permalink

Developer Impact: Fall 2010 Changes

Today, Dinesh Lathi posted an important announcement about the Fall 2010 Seller Update (SR10.3). Here is the developer impact for those features. More details will follow in the documentation as each feature is released. Most Fall 2010 changes will go live the week of September 7, 2010.

New shopping experience for iPod/MP3 players, GPS, and DVDs highlight s great eBay values on these hot holiday products. Starting mid-September, listing with the eBay catalog will be required in these subcategories (Auction-style and Fixed Price, including Good 'Til Cancelled). Pay no Insertion Fees when you list or relist with the catalog.

Developer Impact:

eBay will be providing a 100% product-based shopping experience in three categories. These categories are:

  • iPod & MP3 Players (subcategory # 73839) [US, CA, UK, IE, DE, AT]
  • GPS Devices (subcategory # 156955) [US, CA, UK, IE, DE, AT]
  • DVDs, HD DVDs & Blu-ray (subcategory # 617) [US, CA]

This means that sellers will need to list using a product ID in those categories if a product ID is available for that item. If no product ID is available, sellers should list the usual way in that category.

Items listed with a product ID will show up on the improved product page. The best-value item will appear in an easy to use "value box" at the top of the page. Several factors go into determining who gets this placement, including eTRS status and competitive pricing.

Items that have an available product ID, but are not listed with that product ID will not be eligible for prominent placement on the product page, and will not get the insertion fee discount. However, the AddItem call will not fail.

More Catalogs Available

To support this requirement, eBay has increased the number of items that it provides pre-filled item information for. You may find product IDs for items that did not have product IDs in the past.

Code to Support Even More Future Catalogs

eBay is bringing more catalogs on as they become available. We suggest as a best practice that you build into your listing process for all items an initial search for a product ID. As a convenience, you can search for product ID by UPC and by product title. Then if a product ID is not available, list without the product ID.

This ensures items can take advantage of the additional information provided with pre-filled information, the improved product experience, and will be eligible for prominent placement.

For more information, see:

Release Date:

Enforcement: September 13 September 7

Site Support:

US, CA, UK, IE, DE, AT

eBay Listing Analytics application gives you new insight into how your listings are performing: impressions, clicks, sales.

eBay is replacing the Search Visibility tool with the Listing Analytics application to provide more information on listing performance. At the same time, the corresponding BestMatchItemDetails API is being updated.

Get answers to key seller questions:

  • How do my listings rank for a given search?
  • What does my sales funnel (impressions, clicks, views, and sold items) look like for my active and completed listings?
  • How do my listings compare to the top five listings showing up on the first page of search results (impressions, average views) for a given query?
  • What are best practices for getting more buyers to click on my listings and buy after they click them?

While every effort is made to ensure that API changes are backward compatible, the new version of the BestMatchItemDetails API may not be compatible with the previous version of the API.

For more information, see:

Release Date (Application and API):

US and Motors: Week of September 7

International: Early October

Site Support:

US, Motors, CA, CAFR, UK, IE, DE, AT, CH, FR, IT

Bulk-edit more fields, revise up to 500 listings at once with new functionality in the eBay bulk edit and relist flow.

Developer Impact:

With this release, the new on-site bulk listing management flow becomes generally available on the site. The underlying API that drives the flow will be made available in early 2011. It is a new API that is optimized for bulk editing and relisting.

The new API is robust and flexible and off-loads many listing tool functions like business logic validation to the API itself. Developers may want to consider this as an alternative to the Trading API.

The new API will be released early next year. There are currently no plans to deprecate the Trading API.

For more information, see:

Release Date:

Bulk listing management flow: General release week of September 7

New API: Early 2011

Site Support:

All sites

Get your unpaid items re-listed and back in front of buyers fast with auto-relist option in Unpaid Item Assistant. Choose to exempt some customers from the automated process.

Developer Impact:

Starting in September, Unpaid Item Assistant will be turned on automatically for all PowerSellers and above. The UPI Assistant will automatically open unpaid item cases 16 days after a buyer hasn't paid. This duration can be changed in the seller's My eBay Site Preference Settings (My eBay > My Account > Site Preferences > Unpaid Item Assistant Preferences).

eBay is also offering the option to automatically relist the item when the UPI case closes without a payment. Sellers must opt-in to this feature.

In addition, you can create a list of preferred customers for whom cases will not automatically be created.

Unpaid Item Assistant is available for eBay Checkout items and those that offer only approved electronic payment methods (for example, PayPal, Paymate, Integrated Merchant Credit Cards, and so on).

The UPI Assistant is not directly available via the API. Some developers may already provide similar functionality using the Trading API call AddDispute. You may want to turn that feature off for PowerSellers and above to avoid duplication. Or, your sellers may wish to opt out of UPI Assistant.

For sellers who opt into the auto-relist feature, there is currently no way to determine via the API if an item has been automatically relisted. You may wish to keep a careful eye on any UPI cases and see if GetSellerTransactions starts returning any unexpected RelistedItemID values. Sellers may prefer not to opt into the auto-relist feature.

For more information, see:

Release Date:

The week of September 7

Site Support:

All sites

Industry-standard shipping terms —Economy, Standard, Expedited, and One-day—used to describe domestic shipping services. Shipping options displayed prominently along with estimated delivery time on the item page and in checkout.

Developer Impact:

To reduce shipping-related questions—including confusion about the carrier services offered and time of delivery— we will be displaying the shipping options offered, along with estimated delivery, more prominently throughout the buying process. The existing generic shipping service (e.g. Standard Flat Rate, Expedited Flat Rate, Overnight Flat Rate, and Other) will be automatically renamed with one of the new Industry-standard shipping terms and the corresponding delivery estimates will be automatically added as shown in this table:

Current service name

New service classification

Shipping time used for estimated delivery

Other (see description)

Economy shipping

1 - 10 business days

Standard Flat Rate Shipping Service

Standard shipping

1 - 5 business days

Expedited Flat Rate Shipping Service

Expedited shipping

1 - 3 business days

Overnight Flat Rate Shipping Service

One-day shipping

1 business day

In addition, we are adding three new generic shipping services for sellers who ship into the U.S. from abroad. These services have longer shipping estimates to better account for international shipping and customs clearing times.

New service name

Shipping time

Economy Shipping from outside U.S.

11 - 20 business days

Standard Shipping from outside U.S.

5 - 10 business days

Expedited Shipping from outside U.S.

1 - 4 business days

At the top of the item page and during checkout, four familiar industry-standard service level terms will be used:

  • Economy (1-10 business days)
  • Standard (1-5 business days)
  • Expedited (1-3 business days)
  • One-day (1 business day)

As always, the estimated delivery displayed to buyers will be the shipping time plus your handling time. If the sellers selects a branded shipping service (e.g. UPS Ground, or USPS Priority Mail) this information will continue to be available on the shipping details section of the item page and during checkout.

If a seller currently lists with any of the UPS or USPS services or the "Overnight Flat Rate Shipping Service," their listings won't require any changes.

If a seller currently uses "Standard Flat Rate Shipping", "Expedited Flat Rate Shipping" or "Other (see description)", they should make sure their carrier's published delivery estimates match the shipping times eBay will be using for estimated delivery (See the table above). They may want to change their listings—and possibly their services or handling time to stay competitive and set the right expectations for their buyers.

For more information, see:

Release Date:

The week of September 7

Site Support:

US, UK, DE

Shipping to Alaska and Hawaii, APO/FPO addresses, and special US areas such as Guam and Puerto Rico: Exclude these buyers or show exact charges based on their location.

Developer Impact:

Sellers set the new special shipping rates in their My eBay. There is no way to specify this with the API. Developers should pass a flag in AddItem to indicate that the special shipping rates should be used for a particular listing.

For more information, see:

Release Date:

The week of September 7

Site Support:

DE, UK, North America, Asia-Pacific

Pass on your shipping discounts to buyers with the Shipping Calculator: Specify one domestic and one international discount.

Developer Impact:

Sellers set the shipping discounts in their My eBay. There is no way to specify this with the API.

For more information, see:

Release Date:

The week of September 7

Site Support:

US, CA, AU

Low-cost shipping insurance: Available exclusively with eBay label printing.

Developer Impact:

This feature is only available on the eBay site as part of the label printing process. There is no API equivalent.

For more information, see:

Release Date:

The week of September 7

Site Support:

US

Updates to reduce and manage buyer contacts: Ask a question link moved down on item page; Automated Answers turned on for all sellers.

Developer Impact:

No new API changes for this feature.

For more information, see:

Release Date:

Early August.

Enhancements to My Messages: Use it as your central inbox for buyer email with out-of-office reply, customized email signatures, and message filtering.

Developer Impact:

Newly available in the Sandbox, a preview version of upcoming changes to MyMessages allows you to set selected messages as high priority, retrieve only high priority messages, and get counts of high priority messages.

For more information, see:

Release Date:

Preview currently available in the Sandbox

Available in Production the week of September 7

Site Support:

All sites

Category and Item Specifics changes consolidated with other updates. Find out if your listings are impacted.

Developer Impact:

Please refresh your cached categories and item specifics when the changes go live.

For more information, see:

Get complete details about all these important updates.
See the Seller Checklist for more information about how these updates affect you.

Sellers and developers will benefit from reviewing this information.

For more insight, you're also invited to:
Take part in an upcoming webinar on Thursday, July 15.
Join me and other leaders from eBay in a Town Hall meeting on Wednesday, July 14. Check the Announcement Board for more details coming soon.
Talk with members of my staff during the next two days on a special discussion board we've set up for this purpose.
As always, thank you for selling on eBay.

We recommend taking advantage of the resources that Dinesh mentions above. More developer impact details will follow in the documentation as each feature is released.

July 13, 2010 in Categories and Item Specifics, Finding API, Product News, Sandbox, Seller Releases, Shopping API, Trading API | Permalink

Deprecation Deadline Extended: Selected Trading and Shopping API Calls

As part of our ongoing commitment to the Developer Community, we are pleased to announce that the we are extending the previously announced date of June 2010 for deprecation of Shopping APIs calls (FindItems, FindItemsAdvanced) and Trading API Calls (GetSearchResults and GetCategoryListings).  The new date for deprecation of these APIs will be announced shortly.

This extension is being granted in response to requests received from several members of eBay Developers Program. The extension will provide additional time for all developers who are in the process of migration or are in early stages of their migration process to successfully complete their migration process. 

We do strongly encourage all developers to prioritize and expedite their efforts in upgrading to Finding APIs. The Finding APIs leverage eBay's next generation search technology and have been designed to provide greater flexibility, better performance and scalability. For more information on Finding APIs, please visit  http://developer.ebay.com/products/finding/

For more information on Shopping APIs or migration please send your requests to http://developer.ebay.com/contactus/

June 2, 2010 in Finding API, Product News, Shopping API, Trading API | Permalink

We heard your requests! Several API enhancements

The 653 Version of the Trading API with Developer-Requested API Enhancements is now available!

Enhancements in this release include:

Shipping: Tracking Number and Carrier Used

Tracking Number and Carrier Used are now returned by GetOrders and GetOrderTransactions for both Trading and Half.com. On Half.com, you can use the GetOrders and GetOrderTransactions calls to retrieve unshipped Half.com orders, such as orders that the seller has received but has not yet processed.

New VerifyRelistItem Call

The new VerifyRelistItem request allows you to preview the response and fees for an item you want to relist, before you make the actual RelistItem call. This call requests and returns the same data as RelistItem (same inputs, same outputs, and same usage rules), but without actually listing the item to an eBay site.

Applications can use this call to test the definition of an item before actually listing it to eBay with RelistItem, reducing item listing-related errors.

VerifyOnly Field for ReviseItem

You can use the VerifyOnly boolean field with the flag set to 'true', if you want the response to include the calculated listing price change (if there is an increase in the BIN/Start price) but you do not want the values to persist in the database. See ReviseItem for more details.

Including the VerifyOnly field in ReviseItem is similar to using VerifyAddItem or VerifyRelistItem.

GetPromotionalSaleDetails Enhancement to Filter by Status

A new input field, PromotionalSaleStatus, has been added to GetPromotionalSaleDetails call to restrict the promotional sales returned to those that match the specified status only.

Sellers Can Subscribe to Notification for SellerClosedDisputes

Previously, Buyers have been able to subscribe to get notified when a seller has closed a listing dispute. Now the Seller can also subscribe to the SellerClosedDisputes notification. For more information, see options for platform notification.

Updates to GetMyeBaySelling

In response to your product feedback, these enhancements have been made to GetMyeBaySelling:

  • Listings with variations now return Variation.StartPrice.
  • A new OrderStatusFilter in the request enables you to filter SoldList based on whether transactions have been marked as Paid and/or Shipped in My eBay.
For more information about the contents of the 653 release, see the Trading API release notes.
Reblog this post [with Zemanta]

January 27, 2010 in Categories and Item Specifics, Developer Education, Documentation, Finding API, Merchandising API, Platform Notifications API, Trading API | Permalink

Developer Impact: Spring 2010 Announcements

Today, Dinesh Lathi posted an important announcement about the Spring 2010 Release (SR10.1). Here is the developer impact for those features. More details will follow in the documentation as each feature is released.

OUR LOWEST INSERTION FEES EVER COMING THIS SPRING: FREE AUCTION-STYLE LISTINGS; FIXED PRICE AS LOW AS 3¢ WITH FULL SEARCH EXPOSURE
Great news: Starting March 30 the upfront cost of selling on eBay will be dramatically reduced for sellers of all sizes with our lowest Insertion Fees ever. Whether you're running a business or selling to earn extra cash, choose from a range of options designed to make your selling easier and more profitable:
Choose the option that's best for you:
1.  New "eBay everyday" standard rates: List Auction-style FREE—pay only if it sells
The new eBay standard rates are perfect if you sell occasionally. 

  • List up to 100 items a month Auction-style free—no Insertion Fees—when you start your Auction-style listing under $1.
  • Get new, lower Insertion Fees for all other start prices.
  • Either way, pay one easy Final Value Fee of 9% of the winning bid—and never more than $50—pay only if your item sells.
  • List in Fixed Price for 50¢ with Final Value Fees mostly the same as today

2.  New eBay Stores subscription packages: Fixed Price with full search exposure as low as 3¢ plus great low rates for auctions
The new eBay Stores subscription packages are the right choice for most sellers with 50 or more listings a month:

  • List in Fixed Price with full search exposure for as low as 3¢ Insertion Fees with Final Value Fees for the most part the same as today
  • Get FREE pictures
  • Get deeply discounted fees on Auction-style listings

Developer Impact:
No API changes are needed to support this change. Any rate or subscription changes will be automatically reflected in the API. Sellers are encouraged to review their listing strategy to see which options work best for them.

Only one Fixed Price format
"Full search exposure" is key because starting March 30, there will be just one Fixed Price listing format on eBay. Store Inventory Format listings will automatically become regular Fixed Price listings with the same duration and renew at the new rates—and surface in search results right along with all other listings.

Developer Impact:
In the API, the FixedPriceItem (FPI) listing format will be replacing the StoresFixedPrice (SFP) listing format. We are offering a migration phase where AddItem will continue to accept either FPI or SFP as listing formats. However, the item will be displayed as FPI on the site and in search results. GetItem and other Get calls will return the format you originally used in the request (FPI or SFP).

In early 2011, SFP will no longer be an accepted option, and your AddItem call will fail if you include it. We recommend you take the following actions as early as possible to avoid issues:

  • Remove StoresFixedPrice as a listing option from your user interface
  • Start using FixedPriceItem in your AddItem instead of StoresFixedPrice.

Starting with 653 (late Jan), the existing eBayNotes field in will start returning whether or not that item has had sales in the last 16 months. Sellers can use that information to help them make decisions about which selling strategy works best for them.

As of March 30th, 2010, any existing SFP listings will be treated as FPI on the site. Items will immediately get the higher FPI exposure, and will renew or relist at the FPI price.

Any listing enhancements (e.g., bold, subtitle, etc.) will also renew or relist at FPI rates. Sellers will want to evaluate their use of listing enhancements to see if it supports their listing strategy at the higher rates.

This feature will be available in the Sandbox for testing after the Production release. Note, however, that most Sandbox items will not meet the criteria for having sales information returned in eBayNotes (a listing with no sales for 16 months).

Developers who do not yet support the eBayNotes field in GetMyeBaySelling should consider adding support for it. Sellers will find that information particularly valuable between now and late March as they evaluate their existing SFP listings.

Subscribe or upgrade your subscription early and save!
We want to make sure you have plenty of time to get ready: Use the handy Fee Illustrator to determine which option will be most cost-effective for you. Then subscribe or upgrade now with no additional monthly fee until April.

Developer Impact:
No new API changes for this feature.

BUILDING BUYER CONFIDENCE—NEW EBAY BUYER PROTECTION PROGRAM
We're making a big move to bring buyers and keep them on eBay with the new eBay Buyer Protection program. All over eBay, the message to buyers will be loud and clear: "eBay's got you covered," so buy on eBay with the confidence and satisfaction you expect from a trusted retailer. As always, direct communication between buyers and sellers to get issues resolved will continue to be encouraged.

Developer Impact:
No new API changes for this feature.

The eBay Top-rated seller badge also ensures quality service and keeps buyers coming back. More and more of you are now enjoying the benefits. U.S. sellers can also now qualify for Top-rated status in more countries.

Developer Impact:
We know that sellers appreciate visibility into their performance on eBay. Sellers who sell on UK/IE/DE/AT/CH currently have only 3 possible status levels returned in GetSellerDashboard for those sites: BelowStandard, Standard (default), and TopRated. We are adding an additional level of granularity to the response so sellers can also see if they are AboveStandard.

AboveStandard indicates that the seller is performing above the standard level for that country. UK and DE PowerSellers who are AboveStandard are eligible for Final Value Fee discounts.
Starting early Feb, if you specify version 653 or later in your request, you'll also start seeing AboveStandard (when applicable) in the response.

AboveStandard is an already existing enum (as of 635) so you do NOT need to upgrade to the 653 WSDL to pick up this tag. You probably already support it for the US site.
3rd-party developers will want include this status tag in any user dashboard, or listing cost estimates they provide. Note that a default status value is returned for all sites (whether or not there have been any sales on that site), so developers may want to filter out values for sites that the seller does not sell on.

MORE UPDATES TO BOOST SELLER EFFICIENCY
Sellers in eBay Motors Parts & Accessories will be able to create one listing with a complete list of compatible vehicles—a huge saving in Insertion Fees and time.

Developer Impact:
The API fully supports Parts Compatibility. Developers with sellers who list in Motors: Parts & Accessories will want to add support for this feature to their applications.

Parts Compatibility is available today in the Motors Sandbox in selected test categories. Starting in mid-March, Parts Compatibility will be supported in limited Parts & Accessories categories in the Production environment.

Trading API SDK support for Parts Compatibility will also follow in March.

Listing with Parts Compatibility:

  • Use the new Product API to retrieve the correct eBay Product ID (ePID) for your part (if available). Include that ePID value in the ProductReferenceID container in your AddItem request. The Product API will be available with 655 (early Feb).
  • Use the new Product Metadata API to retrieve a list of parts compatibility information specified as name and value pairs. For example, to specify a part's compatibility with a vehicle, the name would map to standard vehicle characteristics (e.g., Year, Make, Model, Trim, and Engine). The values would describe the specific vehicle, such as a 2006 Honda Accord. Pass those name value pairs in the new Item.ItemCompatibilityList container in AddItem. The Product Metadata API will be available with 655 (early Feb).
  • Specify parts compatibility manually by specifying the part's relevant dimensions and characteristics (e.g., Section Width, Aspect Ratio, Rim Diameter, Load Index, and Speed Rating for a tire) using attributes in Item.AttributeSetArray. A table of attribute values is available now.

Finding Parts Compatibility Items:
Parts compatibility improves search relevancy and frees up item titles and descriptions for more useful descriptions of the part. Listings with parts compatibility information also get a Best Match boost in search results. The compatibility match is also displayed in the search results (e.g., Fits: 2004 Honda Accord).

This new search behavior is supported by the Finding API and the Best Match Item Details API. The deprecated calls FindItems, FindItemsAdvanced, GetSearchResults and GetCategoryListings do not support Parts Compatibility items.

For more information, see the Trading API Release Notes.

You'll be able to list multiple variations of a product in one Fixed Price listing in many more categories.

Developer Impact:
The Items with Variations feature has been added to more categories. For technical information on how to use this feature in the API, see Describing Variations in a Listing.

Return policy and handling time will be required for new listings and re-listings in eBay Motors Parts & Accessories in June—editing tools make updating listings easy

Developer Impact:
Return Policy is specified in Item.ReturnPolicy. ReturnsNotAccepted is a valid value. Handling time is specified in Item.DispatchTimeMax.

Most listing-tool developers should already support required Return Policy and Handling Time in other eBay categories. In late 2010, they will also be required in Motors: Parts & Accessories.

Only new, relisted, and renewed items will be checked for compliance.

Developers can help sellers comply with the new requirement by flagging non-compliant listings for their review. Also by offering bulk editing tools to so sellers can search live listings and revise.

Category and Item Specifics changes are also coming with the rest of these.

Developer Impact:
Please refresh your cached categories and item specifics when the changes go live.

In keeping with the practice started last year, we're continuing to consolidate changes that impact your business into two or three major releases a year. Get details on all the updates coming in the spring 2010 update, including the new fee structure.
For more insight into the upcoming changes, including fees, you're also invited to:

  • Take part in the upcoming webinar on Thursday, January 28.
  • Join me and other leaders from eBay and PayPal in a Town Hall meeting on Thursday, January 29. Check the Announcement Board for more details coming soon.
  • Talk with members of my staff during the next two days on a special discussion board we've set up for this purpose.

We recommend taking advantage of the resources that Dinesh mentions above. eBay developers can also get their questions answered:

 

January 26, 2010 in Best Practices, Business News, Categories and Item Specifics, eBay Motors, Finding API, Product News, Sandbox, Shopping API, Trading API | Permalink

Mismatched CONTENT-TYPE Will Now Cause Call Failure

As of January 15, 2010, eBay evaluates the CONTENT-TYPE header against the request payload format. If the CONTENT-TYPE value is incorrect for the payload, the request will fail. Previously, eBay did not validate the CONTENT-TYPE header in requests.

This HTTP header is optional. If you do not submit the CONTENT-TYPE header with your request, eBay will determine the content type from the payload.

The following table lists the correct CONTENT-TYPE header values for HTTP POST request formats:

Request Payload Format

Content-Type Value

XML

text/xml

SOAP12

application/soap+xml

SOAP11

text/xml (in conjection with SOAPAction header being sent - value can be anything)

See File Transfer Service: Making An API Call for more information about the call format for the File Transfer API.

January 22, 2010 in Critical Notes from Tech Support, Finding API, Large Merchant Services | Permalink

Updates to Summer 2009 Release; Part 2 of 2.

Updates to Summer 2009 Release; Part 2 of 2.

On July 29, 2009, Laurel posted an announcement about the July 2009 updates. In this entry, we highlight part 2 of the features that were released since then

For the list of calls changed with each Trading API version, see the Trading API Release Notes.

Because there are many updates, the details have been split into two entries. The first part can be found here. This is the second entry and covers the following topics:

Listing Enhancements

[627] Changes to ListingFeatureDetails and Some Listing Features to Be Removed and Restricted

Selling Manager Applications

Shipping

ShippingCarrierUsed: Type Change
LeaveFeedback and Shipping API Detailed Seller Ratings (DSRs)

Top-Rated Sellers

Misc

Reminder: Return Policy and Handling Time Required When You Renew GTC Listings


As a reminder, the first entry included: will link to part 1 entry.

If you would like the complete details on the July 2009 Update, please refer to the following links and to the API Release Notes.

Seller Resources


Listing Enhancements

[627] Discontinued: Bold title, border, Featured First, Featured Plus!, gift icon, highlight, Homepage Featured, and ProPack. See the Release Notes.

[627 ] Changes to ListingFeatureDetails and Some Listing Features to Be Removed and Restricted

  • All features are not available to all Sellers, use the Trading call GeteBayDetails to find out which features are available for your site. As part of the seller release, some listing upgrades were removed for some sites, and some will be restricted to eBay Top-Rated Sellers or PowerSellers. The listing features include bold title, border, Featured First, Featured Plus!, gift icon, highlight, Homepage Featured, and ProPack. A new type, ListingFeatureDetails, has been added to the GeteBayDetails response that returns which listing features are available to the seller for the site. Another addition to the GeteBayDetails response, UpdateTime, reports the time of the most recent modification to any Detail.
  • A type has been added to the Trading call ListingStartPriceDetailsType.MinBuyItNowPricePercent, which returns the minimum percentage difference between the start price and the Buy It Now price for a listing on the specified site. There is one exception: Use category details to find the percentage requirements for Motor Vehicles (using Site ID 100 - the eBay Motors site.)

Items with Variations

[629 ] Multi-Variation Listings: GetSellerEvents and Other Enhancements

  • GetSellerEvents now returns variation details in Item.Variations, including StartPrice, Quantity, and QuantitySold, plus SKU and/or VariationSpecifics. Multiple variations are returned together in the same Variations node (similar to GetItem).
  • To keep the GetSellerEvents response smaller, the variation specifics are not returned if the variation has a SKU.
  • With RelistFixedPriceItem and ReviseFixedPriceItem, you can now use SKU to uniquely identify an existing variation, regardless of whether the listing has inventory tracking set to SKU.
  • ReviseInventoryStatus now supports modifying variations when InventoryTrackingMethod is set to ItemID.
  • For the site specified in the request, GeteBayDetails now returns variation constraints, such as maximum number of variations, in VariationDetails.
  • GetUser now returns QualifiesForVariations (a boolean) to indicate whether the user is eligible to list with variations on the site specified in the request.
  • In SetUserNotes, you can now set private notes for variations. These notes will be visible to the user for variations that are displayed in My eBay.
  • GetMyeBayBuying and GetMyeBaySelling now return PrivateNotes for applicable variations. Depending on how the notes were set (what was specified in the SetUserNotes request), the variations may be returned within Variations or within Item

Selling Manager Applications

    • Sellers may subscribe to Selling Manager Applications through My eBay.
    • Developers can create Selling Manager Applications using the Selling Manager API

Shipping

    • [635] Shipping Insurance option has been removed from many sites. If shipping insurance is included in AddItem, it will be dropped with a warning, but won't fail. See the Release Notes.
    • [635] Using My eBay, you can create an Exclude Ship-To List of the locations to where you will not ship items. Once set up, all items that you list on eBay will, by default, use the Exclude Ship-To List to exclude the locations you specified in the list. If a buyer's primary ship-to location is a location that you have listed as an excluded ship-to location (or if the buyer does not have a primary ship-to location), they will receive an error message if they attempt to buy or place a bid on your item. Use GetUserPreferences to review the default set of excluded locations that you have set up in My eBay. Use GetUserPreferences to retrieve your global exclusion list. See the Release Notes.
    • [635] Tracking for multiple package shipment for a single item. ShippingCarrierUsed and ShipmentTrackingNumber have been moved to a repeatable ShipmentTrackingDetails container. See the Release Notes.

ShippingCarrierUsed: Type Change

  • [627] More shipping carriers supported. The type for ShipmentType.ShippingCarrierUsed has been changed from ShippingCarrierCodeType to string. This enables sellers to specify a shipping carrier (via CompleteSale) other than the ones noted in ShippingCarrierCodeType.
  • With a request version lower than 627, the value you specify for CompleteSale's ShippingCarrierUsed must be a value found in ShippingCarrierCodeType. If the request version is 627 or higher, you can specify the shipping carrier of your choice, even if it is not in the ShippingCarrierCodeType list, and GetSellingManagerSaleRecord will return that value. See the Release Notes.

LeaveFeedback and Shipping Detailed Seller Ratings (DSRs)

  • [629] Local Pickup: Shipping Time DSRs ignored, Shipping and Handling Charges MAY be ignored.
  • In the Trading API LeaveFeedback call, DSRs left for Shipping Time will be ignored for all Local Pickup transactions. DSRs left for Shipping and Handling Charges will be ignored for Local Pickup transactions where the seller did not add any special handling fees. See the Release Notes.
  • This change affects the following eBay sites: AU, Mn-AT, BE-FR, BE-NL, CA, CA-FR, FR, DE, HK, IN, Mn-IE, IT, MY, Motors, NL, PH, PL, SG, ES, Mn-CH, UK, US

Top-Rated Sellers

  • [635] Seller Status Now Returned by GetSellerDashboard. See the Release Notes.
  • Avoid 1s and 2s
  • Only domestic DSRs count
  • [629 ] Top-Rated Seller Details Available via GetUser and Other Calls; SellerInfo.SellerLevel to Be Removed
    • When Top-Rated Seller details became available in October (see Announcement), GetUser began returning fields that identify the seller as a Top-Rated Seller and gave details about the Top-Rated Seller program. These fields are already present and documented for GetUser and other calls. They include TopRatedSeller and TopRatedSellerDetails.TopRatedProgram, which identifies the Top-Rated-Seller programs for which the seller is qualified. See the Release Notes.
    • When the Top-Rated Seller feature became active on the US, DE, and UK sites, SellerInfo.SellerLevel no longer returned results for those sites. Affected calls include GetUser, GetBidderList, GetSellerList, GetItem, and GetItemTransactions.

Misc

More categories are becoming catalog-enabled

Reminder: Return Policy and Handling Time Required When You Renew GTC Listings

When Good Till Canceled (GTC) listings are renewed, they will be checked for Return Policy and Handling Time. If these details are not included, the GTC listing renewal will fail. For more info, see this entry in the Forum.

 

December 17, 2009 in Best Practices, Categories and Item Specifics, Certified Provider, Client Alerts API, Developer Community, Documentation, Finding API, Large Merchant Services, Merchandising API, Product News, Shopping API, Trading API | Permalink

Updates to Summer 2009 Release: Part 1 of 2

On July 29, 2009, Laurel posted an announcement about the July 2009 updates. In this two part entry, we highlight the features that were released since then.(For the change details with each API version, see the API Release Notes.)

Because there have been many updates, this topic will be split into two entries.

  1. This first entry includes:

    Best Match

    New Feature: Gallery Plus Pictures
    Doc changes: Updated Value for SellerBusinessType Item Filter
    Reminder of what changed in Best Match

    Editing Live Items (ELI)

    [627] New TransactionID Field for GetItem Request
    Platform Notification changes and client alerts

    Search

    New: Gallery Plus Pictures
    Updated Value for SellerBusinessType Item Filter
    eBay Top-rated Seller
    Clarifications in Documentation for Unpaid Item Disputes
    Multi-Variation Listings: GetSellerEvents and Other Enhancements
    [629] Multi-Variation Listings: GetSellerEvents and Other Enhancements

  2. The second entry (to be published on, or around, December 17) will include:

    Items with Variations

    • [629] Multi-Variation Listings: GetSellerEvents and Other Enhancements

    Listing Enhancements

    • [627] Changes to ListingFeatureDetails and Some Listing Features to Be Removed and Restricted

    Selling Manager Applications
    Shipping

    • ShippingCarrierUsed: Type Change
    • LeaveFeedback and Shipping API Detailed Seller Ratings (DSRs)

    Top-Rated Sellers
    Misc

    • Reminder: Return Policy and Handling Time Required When You Renew GTC Listings

If you would like details on the July 2009 Update, please refer to the following links and to the API Release Notes.

Seller Resources


Best Match

Please see the BestMatchItemDetails API release notes for details.

[1.2.0] New Feature: Gallery Plus Pictures

[1.2.0] Doc changes: Updated Value for SellerBusinessType Item Filter

Reminder of what changed in Best Match (Details)

  • New listing performance score for Fixed Price to replace recent sales
  • New multi-quantity and single-quantity Fixed Price listings will be given exposure in Best Match
  • Titles are more important than ever
  • Seller performance continues to count
  • Shipping cost continues to count
  • No changes to Auction-style listings
  • Optimized by category

Editing Live Items (ELI)

 [627 ] New TransactionID Field for GetItem Request

    • As part of the Edit Live Items feature, a new TransactionID field was added to the GetItemRequest call. This new field will allow both Sellers and Buyers to retrieve a listing as it was at the time of a given purchase by invoking GetItem with a TransactionID in the request (even if the seller has made significant revisions to the listing, following the purchase).
    • Sellers are also able to make revisions to their multi-quantity fixed price listings after a purchase has been made (currently, Sellers can not change their multi-quantity fixed price listings, after at least one item in the listing has been purchased).
    • Sellers are able to view the updated listing for each transaction, but Buyers are only able to view the transactional version of a listing where they are the successful buyer. Past transactional views of an item will be available for up to 90 days from the date the transaction took place.

[635] Platform Notification changes and client alerts

    • Changes to the GetItemTransaction API call may cause a change to the behavior of the following Platform Notifications: EndOfAction, AuctionCheckoutComplete, FixedPriceEndOfTransaction, CheckoutBuyerRequestTotal, FixedPriceTransaction, Checkout, FixedPriceTransactionForSeller, FixedPriceTransactionForBuyer, ItemMarkedAsShipped, and ItemMarkedAsPaid.
    • The following Client Alerts may have a behavior change as a result of this project: EndOfAuction, FixedPriceEndOfTransaction, FixedPriceTransaction, ItemSold, and ItemWon. Each notification will now be based on the state of the item (a 'snapshot' of the item) at the time the transaction was created.

Search

Finding API - see the Finding API release notes for details.

[1.1.0] New: Gallery Plus Pictures

[1.1.0] Updated Value for SellerBusinessType Item Filter

[1.0.1] eBay Top-rated Seller

With the launch of the Top-rated Sellers program, buyers can find items listed by the highest quality sellers on eBay based on the feedback of other buyers. The sellerInfo node in the search results (searchResult.item.sellerInfo) for the "findItems" calls now includes the topRatedSeller field to indicate (true or false) whether the seller of an item qualifies as an eBay Top-rated Seller. Additionally, a new TopRatedSellerOnly item filter has been added to limit search results to items listed by Top-rated Sellers only.

Note the following site restrictions:

  • The searchResult.SellerInfo.topRatedSeller field in the response for the finding calls is supported for the following sites only: US (EBAY-US), Motors (EBAY-MOTOR), DE (EBAY-DE), AT (EBAY-AT), and CH (EBAY-CH).
  • The TopRatedSellerOnly item filter is supported for the following sites only: US (EBAY-US), Motors (EBAY-MOTOR), UK (EBAY-GB), IE (EBAY-IE), DE (EBAY-DE), AT (EBAY-AT), and CH (EBAY-CH).

Top-rated sellers consistently receive highest buyers' ratings, ship items quickly, and have earned a track record of excellent service. eBay regularly reviews the performance of these sellers to confirm they continue to meet the program's requirements. See the Top-rated Sellers page on the eBay site for more information.

Trading API - See the Trading API release notes for details.

[643] Clarifications in Documentation for Unpaid Item Disputes

  • Version 639 release notes surveyed various process changes for Unpaid Item Disputes.
  • Support for the old process will be removed around March 2010, so please migrate your UPI dispute code to work with the new process.
  • How do you know whether the newer or older process applies to your disputes or not? It is all about the request version. If you created a UPI dispute with a request version lower than 637, the old timelines apply and the various platform notifications for messaging are still supported. But if the request version is 637 or greater, the new timelines apply.
  • Further, since AddDisputeResponse can no longer be used (for 637 or greater) for buyer or seller communication, these notifications are no longer triggered: BuyerResponseDispute, SellerRespondedToDispute.
  • See Newer versus Older Unpaid Item Disputes Process - a before/after table of facts.

[639] New Features for 639

  • Multiple-Package Details for a Single Item
  • Selling Manager Calls: No Integration with eBay.com Is Required
  • Unpaid Item Disputes: Process Change

[629 ] Multi-Variation Listings: GetSellerEvents and Other Enhancements

GetSellerEvents now returns variation details in Item.Variations, including StartPrice, Quantity, and QuantitySold, plus SKU and/or VariationSpecifics. Multiple variations are returned together in the same Variations node (similar to GetItem).

December 2, 2009 in Best Practices, Categories and Item Specifics, Client Alerts API, Developer Community, Developer Education, Documentation, Feedback API, Finding API, Large Merchant Services, Platform Notifications API, Shopping API, Trading API | Permalink