Our eBay RePricing now supports the eBay Sell API in addition to the Trading API. This means we can now support both API models used to manage eBay listings in practice. 🔄
Why We Initially Built on the Trading API
When we developed our eBay RePricing in 2017, the Trading API had already been established for years. The Sell API, and especially the Inventory API, was still very new at the time.
For sellers and connected systems, the Trading API was by far the more relevant option. There was also an important technical limitation: listings were not automatically available across both API models.
A listing managed through the classic eBay model did not simply appear in the Sell Inventory API. Likewise, listings created through the Inventory model were managed separately there.
For a RePricing system, this is a crucial point. After all, the actual seller offers need to be reliably accessible.
That is why we built our eBay RePricing on the Trading API.
The Sell API Took a Long Time to Gain Traction
Over the following years, that decision proved to be the right one.
For a long time, we almost exclusively saw eBay inventories managed through the Trading API among our customers. The Sell API played only a very minor role in practice.
Even up to mid-2025, its use was still not a significant topic from our perspective.
That has now changed. 📈
We are increasingly seeing sellers and connected systems using eBay's newer Inventory and Offer model.
At that point, it became clear to us that supporting the Trading API alone would no longer be sufficient.
We Now Support Both APIs
With the latest update, our eBay RePricing can now work with either the Trading API or the Sell Inventory API. 🔧
This means we support both approaches currently used to manage eBay offers.
For sellers, the important part is simple: it no longer matters which API model the connected system uses.
If it uses the Trading API, eSagu can work with it.
If it uses the Sell Inventory API instead, we can now process those listings for price optimization as well.
Two API Models, the Same Price Optimization
Technically, the two approaches are quite different.
The Trading API is based on the classic listing model and works heavily with the eBay ItemID.
The Sell Inventory API uses a different structure, with concepts such as Inventory Items, Offers, and marketplaces playing a central role.
For the actual price optimization, however, this technical difference should not matter.
Regardless of which API is used, the familiar features of our eBay RePricing remain available, including:
- Minimum and maximum prices
- Different RePricing strategies
- Price and ranking optimization
- Competitor rules
- Filters based on delivery time and seller ratings
- Bulk Edit
- Automatic pricing rules
- CSV and REST API
A Small Anecdote to Finish 👀
The Sell API is not actually new territory for us.
When we started developing our eBay RePricing in 2017, our very first prototype was built on the then brand-new Sell API.
During development, however, we quickly discovered that listings were not simply available across both API worlds.
Since the Trading API was far more relevant in practice at the time, we discarded that prototype and rebuilt the RePricing around the Trading API.
Almost ten years later, things have come full circle: our eBay RePricing now supports both models — the Trading API and the Sell API. ✅