Migrating deprecated Trading API calls to eBay's REST APIs

eBay's Trading API (XML, Auth'n'Auth authentication) is in maintenance and some of its calls are being decommissioned on fixed dates. Keeping a dependency on it is a risk: the direction is clear, the REST APIs. This guide shows how to map the deprecated calls and migrate gradually without stopping sales.

Why migrate now

eBay publishes a deprecation schedule: for example GetCategoryFeatures is set for decommission (May 2026) in favour of the Taxonomy API. Legacy calls stop working on fixed dates, so plan sooner rather than later.

The Trading → REST map

Trading API (legacy)	REST equivalent
AddItem / ReviseItem	Inventory API (inventory item, offer, publish)
GetOrders	Fulfillment API
GetCategorySpecifics / GetCategoryFeatures	Taxonomy API
Movements and payouts	Finances API

For the SKU → listing model, see the guide on the eBay Inventory API.

Authentication: from Auth'n'Auth to OAuth

Trading uses Auth'n'Auth tokens; REST uses OAuth. Plan the transition of tokens and scopes: it's an often underestimated part of the migration.

Migrate gradually, not big bang

Migrate one domain at a time — inventory first, then orders and finances — keeping coexistence during the transition. It's the same approach described in the comparison between the Sell API and the Trading API. The buyer side (search and catalog) is a separate matter: see the guide on the eBay Browse API.

Common mistakes

• waiting for the decommission date instead of migrating with margin;
• reproducing the XML one-to-one instead of adopting the REST model;
• forgetting the move from Auth'n'Auth to OAuth;
• uncoordinated double writes during coexistence.

Conclusion

The Trading API isn't disappearing tomorrow, but its calls fall on fixed dates: plan the migration per domain, handle OAuth and keep coexistence under control. References: deprecation status and the Taxonomy API migration guide.