Migrate listings (Ebay)

Migrates eBay listings created from the UI or Trading API into the Inventory API, making them manageable via EcartAPI's product endpoints.

With this call you will be able to control all the product listings created from the eBay UI with the Inventory API.

Before using the PUT products endpoint to update products, you must migrate the listings first.


Listing eligibility requirements

To be eligible for migration, the active eBay listing must meet all of the following requirements:

  • Listing type is Fixed-Price
  • Listing duration is GTC (Good 'til Cancelled)
  • SKU values must be assigned to every item. For multi-variation listings, each variation must also have its own individual SKU.
  • Business Policies (Payment, Return, and Shipping) must be applied to the listing. Legacy payment/return/shipping fields are not accepted. The Payment Policy must have immediate payment enabled and PayPal as the only accepted payment method.
  • Location must include a postal/zip code (PostalCode) or city (Location). Country is always required by the Trading API and will be present automatically.

Listings that do not meet these requirements will be rejected by eBay during migration. Verify each condition before submitting the migrate request.


Critical — variant listings and stock: If the listing is a product with variants, each variant must have at least 1 unit in stock before running the migration. Any variant with zero stock will be silently excluded from the migration — the product will be imported without those variants, and they will not appear in GET /products or in the product group.

Migration is a one-time operation. Once a listing has been migrated, eBay will return an error if you attempt to migrate it again ("This listing is already migrated"). There is no force or re-migrate option.


Recovery when a variant was missed

If a variant was excluded during migration due to zero stock, you must add it manually. The recommended process is:

  1. Create the missing productPOST /api/v1/products with the missing SKU, same structure as the other variants.

  2. Update the product groupPOST /api/v1/products/{inventoryItemGroupKey}/variants with the full group payload including the new SKU in variantSKUs. Retrieve the current group first to avoid losing existing data.

  3. Create and publish the offerPOST /api/v1/products/listings with the SKU, policies, location, price, and category matching the original listing.

As a last resort, if the above steps fail, the only option is to delete the product from eBay and recreate the entire variant structure from scratch, ensuring all variants have stock before migrating.

More information about the eBay resource.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
listings
object
required
Response
200
Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here!