Skip to main content
Published: August 13 2010, 3:47:00 PMUpdated: November 28 2020, 8:39:51 PM

Here is a quick feature comparison to help you determine which API will work best for your use case:

Feature Trading API LMS
Programming model Simple - Syncrhonous request and response Asynchronous – needs a workflow implementation
create a job, upload job file, check for job completion, download job completion file
Infrastructure management
•For high volume inventory

•server errors & retries

•may need to adopt multi-threading to scale
•Client needs to implement retries for server errors
•Client needs to implement logging

•Upload all the requests in a single file and let eBay do the parallel processing
•Retries are automatically handled
•Logging is built in since the uploads and downloads are file based
Implementation of other API calls for features outside of listing & order management Does not require implementing any other APIs for the selling use case Requires Trading API for features such as buyer communication, disputes, stores management, user preferences, etc.
Frequency restriction
(5,000 per day by default, 1.5 million if app check cleared)
No restriction, as long as the total call volume is below the maximum Limits on data file uploads and downloads
rate limits
Simultaneous calls Limited to 18 threads Can have only 1 job running per job type
Order Acknowledgement Not available Available

Additional Information



How well did this answer your question?
Answers others found helpful