717 Trading, Shopping, Merchant Data API Docs Now Available

Please remember to use a test environment when updating applications to use a new schema version.

To find out when a version of the API will be available, see the table at the top of the Release Notes for that API.

You can find the latest API documentation at the eBay Developer Documentation Center.

Trading

Trading Release Notes

See the Trading API System Announcements for bug fixes included in this release.

Shopping

Shopping Release Notes

See the Shopping API System Announcements for bug fixes included in this release.

Merchant Data

Merchant Data Release Notes

See the Large Merchant Services API System Announcements for bug fixes included in this release.

Bradburn Young
API Tech Docs

April 18, 2011 in Developer Website, Documentation, Shopping 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

715 Trading, Shopping, Merchant Data API Docs Now Available

Please remember to use a test environment when updating applications to use a new schema version.

To find out when a version of the API will be available, see the table at the top of the Release Notes for that API.

You can find the latest API documentation at the eBay Developer Documentation Center.

Trading

Trading Release Notes

Release Highlights

See the Trading API System Announcements for bug fixes included in this release.

Shopping

Shopping Release Notes

Release Highlights

See the Shopping API System Announcements for bug fixes included in this release.

Merchant Data

Merchant Data Release Notes

See the Large Merchant Services API System Announcements for bug fixes included in this release.

Bradburn Young
API Tech Docs

April 5, 2011 in Developer Community, Developer Website, Documentation, Shopping API, Trading API | Permalink

709 Trading, Shopping, Merchant Data API Docs Now Available

Please remember to use a test environment when updating applications to use a new schema version.

To find out when a version of the API will be available, see the table at the top of the Release Notes for that API.

You can find the latest API documentation at the eBay Developer Documentation Center.

Trading

Trading Release Notes

Release Highlights

See the Trading API System Announcements for bug fixes included in this release.

Shopping

Shopping Release Notes

See the Shopping API System Announcements for bug fixes included in this release.

Merchant Data

Merchant Data Release Notes

See the Large Merchant Services API System Announcements for bug fixes included in this release.

Bradburn Young
API Tech Docs

February 25, 2011 in Developer Website, Documentation, Shopping API, Trading API | Permalink

Announcing a Powerful New Open Commerce Platform

As some of you may have already read, we are launching a new open platform business that combines the resources of both eBay and PayPal in one powerful commerce solution. Separately, the eBay and PayPal Developer Communities have done incredible work and continue to wow us every day. But the greatest success stories have always been when we are able to combine the full strength of both platforms and deliver a value proposition that enriches your products and services. I am very excited about what our new platform business will mean to our Developers and the new opportunities it will create. The team we are assembling under Matthew Mengerink's leadership are dedicated, talented folks who are passionate about helping our Developers and Partners be successful. To hear more from Matthew, see his blog post here: https://www.thepaypalblog.com/

February 17, 2011 in Developer Community, Developer Website, Developers Conference | Permalink

Starting Your Web App in the Cloud for Free

Blogging from the PayPal X Innovate conference, I wanted to share some of the key points from the Google App Engine session. If you are an eBay Developer looking for a simple way to try a cloud-based infrastructure without a large startup cost, you might want to take a look at Google App Engine.


WHAT IS IT?

Google App Engine is a cloud-based technology that allows Developers to build web applications on the same reliable and scalable infrastructure that powers Google Apps. Since its launch, more than 250000 Developers have created apps built on Google App Engine. With the free, entry-level tier, Developers can get started with 5M page views per month, 1 GB of bandwidth per month, 1 GB of storage, and 6.5 CPU hours per day. As your application grows, additional resources can be purchased. You can even enable billing customers for your apps to help cover the cost as your user activity grows.


The next level offering, Google App Engine for Business, is in preview and looks to address some of the additional needs of a growing business. Central management of all your Google App Engine apps and 99.9% reliability SLA come with the business tier, and pricing is cheaper than Amazon's AWS service.


HOW IS IT DIFFERENT FROM AMAZON AWS?

There are several key differences between Google and Amazon's cloud offering. Google App Engine requires that you adopt the entire stack, which isn't necessarily a bad thing, given that stack includes Google's BigTable database system. In this regard, Amazon's offering will give you quite a bit more flexibility in deciding which parts of your technology stack you want powered by Amazon. At the moment, Google App Engine only supports apps written in Java or python, with extending JVMs for additional languages. Amazon allows you quite a bit more flexibility in your preferred language. Then again, for this added flexibility, you will pay a bit more than you will on Google App Engine. With their current offering Amazon AWS looks to be easier to graduate to more app sophistication, but I am sure Google is looking to close this gap quickly.


WHO SHOULD TRY IT?

Developers who are just starting to build their apps and want to do so quickly and with little infrastructure investment. Approach with caution as this is a relatively new offering from Google and the system is still improving. Keep an active eye on your application growth, minding an upgrade or migration path should you need it.

October 26, 2010 in Developer Community, Developer Website | Permalink

685 Trading, Shopping, Merchant Data API Docs Now Available

Please remember to use a test environment when updating applications to use a new schema version.

To find out when a version of the API will be available, see the table at the top of the Release Notes for that API.

You can find the latest API documentation at the eBay Developer Documentation Center.

Trading

Trading Release Notes

Release Highlights

See the Trading API System Announcements for bug fixes included in this release.

Shopping

Shopping Release Notes

See the Shopping API System Announcements for bug fixes included in this release.

Merchant Data

Merchant Data Release Notes

See the Large Merchant Services API System Announcements for bug fixes included in this release.

Bradburn Young
API Tech Docs

August 27, 2010 in Developer Community, Developer Website, Documentation | Permalink

How to deal with the fast approaching Open Identity!

A User Who Came in From the cloud: How to Deal with the Fast-Approaching Open Identity Paradigms.  Best Practices for Relying Parties.  Farhang Kassaei Web

Problem: Managing Digital Identity
  •   We have too many accounts with too many passwords.  This is too difficult to manage for users, and its costly to secure for service providers.  Its insecure, tought to use and expensive.  Makes you think why we did this to begin with.
  • This is also a problem for businesses (e.g. eBay Sellers), who use multiple applications such as:  Market research, Ordering and SCM, Marketing, Promotions, Pre Sales, Inventory, CRM, etc.

Solution: Federated Identity

  •     What does Federated Identity mean?  Outsource the management of identities and their attributes to someone else.  This someone else has to be trustworthy, reliable (operational worth), complimentary to your business and not a competitor.  This someone else is the Identity provider, you are the relying party, and your customers are the consumers.

Gerneral Architecture Model - oAuth, Facebook Connect, OpenID

  •   Your consumer goes to your federated sign in page, and your app asks the consumer, which Identity Provider to use (eg Paypal, eBay, Facebook, etc).  The IDP provides an authorization token, which allows your consumer to consume the pages that are in your app.

Relying Party Best Practices

  •   Choose the right Identity Provider.  They should be business worthy, operational worthy, trustworthy.  The criteria includes type of identity, and profile data.  Quality of Idenityt profile data, Assurance level for Identity data.
  •   Contain the IDP Token.  Create your own STS and make that the "currency of the land".  Don't expose all of your services with the IDP.
  •   Understand the Protocol.  Do you need a prior relationship to register with the IDP?  Can you request extended attributes?  Can you make "back channel" calls in User Not Present mode?  Do you need to register a call back URL?  Do you need to exchange secretes with the IDP?  Do you need to run IDP code on your servers?
  •   Decide what you are relying on the IDP for.  Registration pre-fill.  Complimentary Identity Provider.  Exclusive Identity Provider.  Checkout and Transaction identity.  Confirmation, Assurance Reputation, Credit Decision.  Low consequence actvities like blog posts, etc.
  •   Link Accounts and give user control. In your account section, let people view thier primary identity provider, change it if they need to.
  •   Manage Session Properly.  Respect IDP's advice about token expiration.  Create your own session, do not reuse IDP session.  Protect IDP's token, do not put i in a cookie.  Implement a log out and report it to the IDP.

What happens when the user forgets their password?

  •   If users forget their password and cannot retrieve it with the IDP, should they be locked out of your service?  You should capture and manage one or more local secretes (eg. Secrete Questions etc)  Allow users to unlink the old IDP account from local accoutn and/or link with new ones.

The size of the federation Matters.

  •   What does this mean?  Let's say the user is logged into your application, now, and on the user's behalf, your app needs to:
  1. Access eBay API to create a listing.
  2. Paypal API later to get reports or issue refund
  3. FaceBook API to add it to users fan page
  4. Supply Chain Service they use to order more.

June 10, 2010 in Developer Community, Developer Education, Developer Website, Developers Conference | Permalink

2010 eBay Developers Program Survey Coming Soon!

Keep your eyes open for an invitation to take the 2010 eBay Developers Program Survey. The survey is your opportunity to provide us with direct feedback to improve our program to better meet your needs.

Results from past surveys of our developer community resulted in improvements to our Developer Sandbox,  Developer Tools and our communications regarding API changes.

We are working with a company called Qualtrics, so please look for our email in early April with a link to the survey on their site.

Please take this opportunity to share your opinions with us.

March 25, 2010 in Developer Website, Program Events | Permalink

We are 9! The 9th Anniversary of the eBay Developers Program

Many changes have taken place since our 8th anniversary:

  • In August 2009, eBay opened its new App Store for Sellers, offering developers the ability to embed their business productivity applications in My eBay, where hundreds of thousands of eBay Sellers currently manage their online business.
  • As of Q3 2009, the eBay Developers Program has grown to more than 100,000 members who have created over 13,000 live applications.
  • More than 60% of all eBay.com listings come through eBay Web services, with over 30% coming through third-party tools via the eBay Developers Program.
  • In Q3 2009, the eBay Platform handled over 27 billion Web service requests.
  • Five developers were honored this year with annual eBay Star Developer Awards for improving user experience, helping sellers adapt to rapid improvements in eBay Marketplaces, providing product input that improves the API platform for the eBay developer community, and more.

2009 eBay Star Developer Awards winners are:

Thank you all for another great year! :-)

December 2, 2009 in Best Practices, Business News, Developer Community, Developer Education, Developer Website, Partner News, Product News, Program Events | Permalink