List every active listing in an eBay seller's storefront by username, with search-style filters, sorting and paging.

View all eBay Product Listings & Seller Data endpoints →

Returns every active listing in one seller's eBay storefront as structured JSON, so a competitor's or supplier's whole catalog can be scanned without a keyword. seller is the only required input: the eBay seller username, which is the handle in /usr/{seller} or the 'Sold by' link on a listing (the _ssn value in eBay URLs). Optional inputs reuse the search filters: domain (13 verified sites; other eBay country sites such as com.sg or com.hk are also accepted according to the operation notes), category (a numeric eBay category ID, which the categories operation can look up by name), condition (new, open_box, refurbished, used, for_parts), price_min and price_max in the marketplace currency, the boolean flags best_offer, free_shipping and returns_accepted, location (domestic, us, uk, worldwide, north_america, european_union, whose choices follow the site's own item-location filter and therefore depend on domain), pickup_postcode with pickup_distance (miles, default 25; UK collection in person, needs domain co.uk) and sort (best_match, newly_listed, ending_soonest, price_low, price_high). page and max_results page through the catalog; max_results runs from 1 to 240 per page and larger values are capped at 240. The response is an ok/meta/data envelope: data.seller holds the username, data.results[] holds listing cards with item_id, title, price{value,currency}, condition, buying_format, shipping, location, image and url, and meta.pagination reports the paging state, including has_more. Observed in a live probe (seller musicmagpie, domain co.uk, max_results 5): HTTP 200, ok true, meta.pagination present, data.seller a string and data.results an array of 5 cards. The stored source example is not probe-verified and comes from a different call (its prices are in USD and its links point to ebay.com); it additionally shows price.raw, sold_count text such as "1,062 sold" and catalog_rating{average,review_count} on some cards, shipping as display text such as "+$4.71 delivery", and a condition field that holds the seller's tagline text rather than a condition label, so treat card condition as display text and use the condition filter for filtering. Filters other than domain and max_results were not exercised by the probe, and the page-depth ceiling quoted in the notes was measured on a search query, not on a storefront.

API Features

Whole storefront from one username Send only seller to receive the active listings in that seller's storefront. No keyword is needed, which is what separates this operation from search.
Search-compatible listing cards Each card carries item_id, title, price{value,currency}, condition, buying_format, shipping, location, image and url, the same shape search returns, so one parser can handle both operations.
Filters scoped to one seller category, condition, price_min, price_max, best_offer, free_shipping and returns_accepted narrow the storefront to the product line, price band or buying terms you actually track.
Page-native catalog walking page and max_results (1 to 240) together with meta.pagination.has_more let a simple loop continue until a large seller's catalog is exhausted.
Orderings for price ladders and fresh stock sort accepts best_match, newly_listed, ending_soonest, price_low and price_high, so you can read a seller's cheapest items, priciest items or newest listings first.
Item IDs ready for deeper lookups item_id and url on every card can be passed to items-batch or item-detail, so full specifics are fetched only for the storefront listings that need them.
Demand hints on some cards The stored source example shows sold_count text and a catalog_rating object on some cards. These extras are not guaranteed on every card and were not confirmed by the probe.

Live API Demo

POST /api/project/ebay/seller-items

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X POST 'https://api.opendata-api.com/api/project/ebay/seller-items?key=<API_KEY>' \ -H 'Content-Type: application/json' \ -d '{"seller":"<seller>"}'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What do I send in the seller field?

Send the eBay seller username, the handle you see in /usr/{seller} or in the 'Sold by' link on a listing (eBay's _ssn value). It is the only required field. The probe used musicmagpie.

How is seller-items different from search?

Search needs a keyword and looks across all sellers. seller-items takes a seller username instead and returns that seller's active storefront listings, with the same card shape and the same filters (category, condition, price range, shipping, returns, location, pickup, sort) and the same page and max_results paging.

How do I read a seller's complete catalog?

Set max_results to 240 (the maximum per page; larger values are capped) and increase page from 1, stopping when meta.pagination.has_more is false. The notes measured about 450 pages of depth on a search query; a single storefront is normally far smaller, and that depth was not measured on a storefront.

What does a listing card contain?

The documented fields are item_id, title, price{value,currency}, condition, buying_format, shipping, location, image and url. The probe confirmed an array of 5 cards for max_results 5 but the probe summary does not list per-card fields. The stored source example, which is not probe-verified, also shows price.raw, sold_count (for example "1,062 sold") and catalog_rating{average,review_count} on some cards.

Can I rely on the condition field of a card?

Not as a clean label. In the stored source example the condition field of storefront cards contained the seller's tagline (text such as "Great Prices & Quality from musicMagpie. 13m+ Feedbacks") instead of values like new or used. To get items in a given condition, send the condition parameter (new, open_box, refurbished, used, for_parts) rather than parsing the card text.

Which currency are the prices in and what does domain change?

domain selects the eBay site and, according to the notes, sets the currency and local listings; price_min and price_max are interpreted in that marketplace's currency. The stored source example, which comes from a call that used USD and ebay.com links, shows a UK-based seller's items priced in USD, so check price.currency on each card instead of assuming a currency from the seller's home country.

Does it return sold or ended listings, or seller feedback?

No. It returns active listings only. For a seller's feedback score, positive percentage, top-rated status and rating breakdown call the seller-profile operation with the same username.

How does the pickup filter work here?

pickup_postcode limits results to listings available for collection in person near a UK postcode and requires domain co.uk. pickup_distance sets the radius in miles (default 25); eBay offers 10, 25, 50, 100, 200 and 500, and other values act as the next option up. pickup_distance is only used together with pickup_postcode. The probe did not exercise this filter.

What did the live probe verify?

A call with seller musicmagpie, domain co.uk and max_results 5 returned HTTP 200 with ok true, a meta object containing pagination, data.seller as a string and data.results as an array of 5 listing cards. Other filters, sort orders and deep paging were not exercised by the probe.

Related operations

Guides

View Subscription Plans →