This guide provides high-level information and the steps required to migrate from Large Merchant Services (LMS, a SOAP API) to the Feed API (REST API).
Existing users should start using the sell Feed’s API interfaces. The Feed API introduces set of new REST APIs interfaces using existing feed formats that provides enhanced features.
See LMS Migration References for additional references.
The Feed API lets sellers upload and download feed files and reports. Both upload and download feed files are processed asynchronously by eBay. The status of all upload and download tasks are tracked with a unique 'task ID'. Each report can be customized with date ranges and other filter criteria. General Sell Feed API Tasks (Flows) provide basic use of the Sell Feed API.
Differences between LMS and Feed API
The following list describes the general differences between using LMS and the Feed API. Information specific to each flow (upload and download) and provided in a different section of this document.
- LMS works through SOAP API while the Feed API takes in REST API
- The Feed API accepts OAuth tokens. See Using eBay RESTful APIs for more information on working with eBay REST APIs.
- In the existing LMS flow, Bulk Data Exchange APIs are used to perform the jobs and File Transfer APIs used to upload and download files. These APIs are merged and come under a single Feed API for sellers.
- As the Bulk Data Exchange API is being updated to the new API, there are some changes to response elements. These differences are documented in this guide.
- Feed file formats are generally not changing, but any changes are documented in this guide.
The general guideline for when to use which verb is as follows:
- A GET is used for requesting information from the web service.
- A POST is used to put data to a web server. There is no specification as to where the web service should put the data.