Marketplaces

eBay

Official API, business policies, item specifics and sell-through data.

eBay is the most fully supported marketplace in Reskale, because it is the only one with a mature public API for everything: listing, orders, fees, returns and tracking.

Connecting

Press Connect on Connections and approve on eBay's own consent screen. This is OAuth — eBay never shows Reskale your password, and you can revoke access from your eBay account settings at any time.

eBay connections do not need the extension and do not need your browser open. They refresh themselves and rarely need attention.

Listing

Listings are created through eBay's API as fixed-price listings.

Categories

eBay has tens of thousands of leaf categories, and nearly every other requirement is derived from the one you pick. Reskale resolves categories against eBay's live Taxonomy API rather than a stored table — eBay retires and restructures categories regularly, and a hardcoded map goes stale silently.

If a listing fails with requirements that seem unrelated to your item, the category is the first thing to check.

Item specifics (aspects)

eBay requires per-category attributes: Department, Type, Style, Closure, Sleeve Length, and so on. Which ones are mandatory depends entirely on the leaf category.

Reskale reads the required aspects from eBay's taxonomy at crosspost time, so the list is current. Many can be filled from what the item already knows.

When eBay rejects a listing for missing aspects, it names them — one error per missing aspect, with the aspect name attached. Those come back as named fields you can fill, not a generic "listing failed".

Condition

Required, and the valid values differ per leaf category. A condition that is valid for one category is rejected in another. Reskale reads the allowed conditions for the specific category rather than offering a global list.

Titles

Hard cap of 80 characters. Anything longer is rejected outright rather than truncated.

Business policies

If your eBay account uses business policies for payment, shipping and returns, Reskale references them by profile rather than re-specifying the terms on every listing.

This is the better path: your policies stay managed in one place on eBay, and changing a policy there applies to listings without touching Reskale.

Sales and fees

Orders sync automatically. Fees come from eBay's Sell Finances API, which is the authoritative source for what eBay actually took — including final value fees, ad fees and adjustments that a listing-level estimate would miss.

Fees flow into Sales and Bookkeeping.

Offers

eBay Best Offer appears in Offers. Accept, decline and counter from Reskale.

Seller-initiated offers to watchers are eBay's own Best Offer mechanism — covered in buyer discounts.

Messages

eBay buyer messages sync into Messages.

Shipping and tracking

Tracking numbers sync from eBay's fulfillment data and appear in Shipments.

Buy labels in eBay's own flow. Reskale reads the tracking back; it does not purchase postage.

Returns

eBay returns are read from your seller returns page rather than the Fulfillment API — the API does not expose the same set, and the page is what actually reflects your open cases.

The Search screen shows what is listed on eBay right now and what sellers are asking. eBay does not share sold prices with apps, so for what items actually sold for, use eBay's Sold filter or Product Research in Seller Hub — see Search for how.

Known quirks

  • Ended and relisted items get new IDs. eBay does not preserve a listing ID across a relist, so a relisted item is a new listing as far as any tool is concerned.
  • SKU changes fork history. Changing an item's custom label on eBay can make it look like a different item.
  • Category retirement. eBay retires categories periodically. A listing that worked last year can fail today because its category no longer exists; re-selecting the category fixes it.

Troubleshooting

Error messages and fixes: crosspost error messages.

Something here wrong or out of date? Tell us.

eBay — Reskale Docs