We designed our latest APIs based on use cases that we have carefully vetted with buyers, sellers, and application providers.
After listening to our customers, we have revamped everything, from taking a more retail-standard approach to the functional capabilities we offer to buyers and sellers; to updating the overall architecture of our APIs; to changing basic operational details that matter to developers, such as how we think about error messages and API Call Limits (rate limiting).
eBay Buy API for buying, selling, general commerce and analytics.
eBay Sell API for buying, selling, general commerce and analytics.
eBay Commerce API for buying, selling, general commerce and analytics.
eBay Developer API for buying, selling, general commerce and analytics.
eBay developer documentation consists of several sets of documentation. The Using eBay RESTful APIs guide sits atop all the RESTful documentation and describes how to format requests, configure the OAuth authorization needed for each request, handle errors, and more. Refer to this guide for all the details on making RESTful requests.
Each RESTful API has a complete set of reference documentation, which includes the following documentation covered in the table below:
The Overview page for an API contains:
|Release Notes||Each API has a set of Release Notes that detail each major and minor release of the API.|
API reference documentation includes the following:
|Integration Guides||The Selling and Buying Integration Guides provide conceptual and how-to information for the main tasks performed by developers with selling and buying applications.|