πŸ›’

eBay Product Listings & Seller Data APIs

Search active eBay listings, look up items by ID, scan seller storefronts and check deals and public seller feedback across 13 marketplace domains.

Open the standalone eBay demo. It sends a request only when you choose Send.

Search active eBay listings

Replace <API_KEY> with your authorized platform API key from the dashboard. The request URL contains your key; keep it out of shared links, screenshots and logs.

This is a template rather than a ready-made example, because the search request takes a JSON body. Enter your own keywords in query and optionally pick a marketplace domain. Opening the page, expanding panels or copying the template sends no data request.

Search needs one required field, query: choose a keyword, and optionally an eBay domain such as com, co.uk or de. No sign-in, cookie, session or earlier lookup ID is needed. Opening the page or copying the template sends nothing; a data request is sent only when you submit it, and each submitted request uses credits from your API key.

Base URL https://api.opendata-api.com

curl -X POST 'https://api.opendata-api.com/api/project/ebay/search?key=<API_KEY>' \ -H 'Content-Type: application/json' \ -d '{"query":"<query>"}'
Marketplace, item IDs and batch costs
  • Keep domain with every saved result: it sets the site and currency, and the 13 listed sites have their own category IDs and location options. UK local pickup needs domain co.uk plus a postcode.
  • Results describe active listings at request time. Prices are asking prices, not sold prices, and shipping and sold-count values are display text. Seller fields can be null: keep them unknown and never add overlapping feedback windows.
  • items-batch bills one lookup per item ID, so a batch saves waiting time, not cost; compare meta.requested with meta.upstream_calls. The documentation gives both 40 and 15 as the per-request limit, so use chunks of 15 until you confirm 40. Report not_found IDs separately from request errors.

Read the response before trusting the data

Check the HTTP status first, then the gateway's code, message and data. Gateway code 200 indicates business success; HTTP 200 alone does not. Inside data, confirm ok is true before reading meta and data. Listings are active asking prices rather than sold prices, and seller or item fields can be null.

Choose the eBay lookup you need
Find listings, categories and deals

Resolve a category name to its numeric ID with categories, search active listings by keyword with search (query is its only required field), or read the current deals grid with deals, which needs no query. Result cards carry item IDs for later lookups.

Look up items by ID

item-detail takes an item_id (the digits after /itm/ in a listing address) or a full listing url and returns one full record. items-batch needs item_ids, a comma-separated list of known IDs, and is billed per ID; IDs it cannot resolve come back in not_found. Do not guess IDs from titles.

Review a seller and their storefront

seller-items lists a seller's active listings and seller-profile returns feedback and rating data. Both require an explicit seller username, which you can read from a listing card or item record. Feedback is a public summary rather than a safety guarantee, and a storefront scan is paged, so one page is not the full inventory.

Category Lookup

POST /api/project/ebay/categories

Look up eBay category IDs by name and list top-level departments for a marketplace domain.

Full docs β†’
Details

Returns the eBay category tree for one marketplace domain as structured JSON. Send an optional query to filter categories by a case-insensitive name or slug substring, so a plain-language name such as cell phones resolves to the numeric category_id that the search operation's category parameter expects; leave query empty to receive the full top-level tree. domain selects one of 13 verified eBay sites (com, co.uk, de, com.au, ca, fr, it, es, nl, at, ch, ie, pl) and max_results limits how many categories come back, up to 240. The response uses an ok/meta/data envelope: data.categories[] holds category_id, name and slug, and data.groups[] holds the top-level department names. Observed in a live probe (query cell phones, domain com, max_results 5): one category was returned (category_id 15032, name Cell Phones & Accessories, slug Cell-Phones-Smart-Watches-Accessories) together with 18 department names such as Electronics, Collectibles & Art and Home & Garden, and meta reported domain com, query cell phones and record_count 1.

Send a request only when you choose to 0 required, 3 optional
ParameterInValue
body
body
Optional filters and paging (1)
ParameterInValue
body

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X POST 'https://api.opendata-api.com/api/project/ebay/categories?key=<API_KEY>'

Deals & Discounts

POST /api/project/ebay/deals

Fetch the current eBay Daily Deals grid with sale price, was-price and shipping for a marketplace domain.

Full docs β†’
Details

Returns the promoted discounts currently shown on the eBay Daily Deals page for one marketplace domain, with no search query required. The optional domain parameter selects one of 13 verified eBay sites (com, co.uk, de, com.au, ca, fr, it, es, nl, at, ch, ie, pl) and sets currency and local listings; the optional max_results parameter sets how many deal cards are returned, up to 240. The response uses an ok/meta/data envelope and data.results[] holds one card per deal with item_id, title, price{value, currency, raw}, was_price{value, currency, raw}, shipping, deal_badge, image and url. Observed in a live probe (domain com, max_results 5): five cards priced in USD; four carried a was_price object, one had was_price null, shipping was either the text Free shipping or null, and deal_badge was null on every card, so treat was_price, shipping and deal_badge as optional. meta.record_count reported 5 and meta.domain reported com.

Send a request only when you choose to 0 required, 2 optional
ParameterInValue
body
body

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X POST 'https://api.opendata-api.com/api/project/ebay/deals?key=<API_KEY>'

Item Details

POST /api/project/ebay/item-detail

Get full eBay listing details by item ID or listing URL, including price, seller, shipping, returns and item specifics.

Full docs β†’
Details

Returns the full detail record for a single eBay listing, identified by item_id (the digits after /itm/ in the listing URL) or by the complete listing url; provide one of the two. domain selects one of 13 verified eBay sites (com, co.uk, de, com.au, ca, fr, it, es, nl, at, ch, ie, pl), and include_description set to true inlines the full seller description text at the cost of one extra request. The response uses an ok/meta/data envelope and data.item carries the listing. Observed in a live probe (item_id 287070621317, domain com): item_id, title, url, price{value, currency, raw}, list_price, condition, availability, brand, model, mpn, images[] (url, width, height and sometimes a description), item_specifics{} with 22 entries, seller{name, feedback_pct, feedback_count}, shipping{country, currency, rate}, return_policy{days, method}, best_offer, quantity_available, quantity_sold, watchers, end_time, attributes{dimensions, weight} and description_url. In that sample seller.feedback_pct, seller.feedback_count, category_path and both attributes values were null. Documented but not exercised by the probe listing: bids, current_bid and time_left for auctions, variations[]{dimension, values[]{value, out_of_stock}} for multi-variation listings, and a description field when include_description is set.

Send a request only when you choose to 0 required, 4 optional
ParameterInValue
body
body
body
Optional filters and paging (1)
ParameterInValue
body

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X POST 'https://api.opendata-api.com/api/project/ebay/item-detail?key=<API_KEY>'
POST /api/project/ebay/items-batch

Fetch full eBay listing records for many item IDs in one call, with unresolved IDs reported in not_found and billing counted per ID.

Full docs β†’
Details

Looks up several eBay listings at once by item number and returns, for each one, the same full record as the single-item detail operation. Send item_ids as a comma-separated string of the digits that follow /itm/ in a listing URL, and optionally choose domain (13 verified sites such as com, co.uk, de, com.au and ca) to set the marketplace and currency. The operation overview states up to 40 IDs per request, while the item_ids parameter note says up to 15 per call, so chunk at 15 if you want to stay inside the stricter figure. The response uses an ok/meta/data envelope. data.items[] holds item_id, title, url, price{value,currency,raw}, list_price, condition, availability, brand, model, mpn, images[], category_path, item_specifics{}, seller{name,feedback_pct,feedback_count}, shipping{rate,currency,country}, return_policy{days,method}, best_offer, end_time, watchers, quantity_available and quantity_sold, plus auction fields such as bids and current_bid on auction listings. data.not_found[] lists IDs that were ended, removed or invalid instead of dropping them silently, and meta.requested and meta.upstream_calls report how many IDs were sent and billed. Billing is per item ID, not per request: eBay has no batched item endpoint, so N IDs cost the same as N single lookups, and the saving is wall-clock time (the operation notes measure 25.6 s sequential versus 4.1 s for 8 IDs). Observed in a live probe (item_ids 287070621317,301782776848, domain com): HTTP 200 with ok true, meta.requested 2, meta.upstream_calls 2, two active InStock records, an empty not_found and data.unavailable null. In that probe the first record had null seller.feedback_pct, seller.feedback_count, category_path and return_policy, so treat those fields as optional, while the second record returned return_policy {days 30, method ReturnByMail} and a three-level category path. The 40-ID ceiling, the auction fields and a non-empty not_found array come from the operation notes and documented example, not from the probe.

Send a request only when you choose to 1 required, 1 optional
ParameterInValue
body
body

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X POST 'https://api.opendata-api.com/api/project/ebay/items-batch?key=<API_KEY>' \ -H 'Content-Type: application/json' \ -d '{"item_ids":"<item_ids>"}'

Seller Storefront

POST /api/project/ebay/seller-items

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

Full docs β†’
Details

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.

Send a request only when you choose to 1 required, 14 optional
ParameterInValue
body
body
body
body
Optional filters and paging (11)
ParameterInValue
body
body
body
body
body
body
body
body
body
body
body

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X POST 'https://api.opendata-api.com/api/project/ebay/seller-items?key=<API_KEY>' \ -H 'Content-Type: application/json' \ -d '{"seller":"<seller>"}'

Seller Reputation

POST /api/project/ebay/seller-profile

Look up an eBay seller's feedback score, positive-feedback rates, rating breakdown and top-rated or business status by username.

Full docs β†’
Details

Returns the public reputation of one eBay seller as structured JSON. 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. domain optionally selects the eBay site (13 verified sites; other eBay country sites such as com.sg or com.hk are also accepted according to the operation notes). No eBay account or seller authorization is needed on your side; the data comes from publicly visible seller information. The response is an ok/meta/data envelope and data.seller_profile is documented to hold store_name, feedback_score, feedback_positive_pct, positive_pct_12mo, items_sold_display, followers_display, member_since, location, business_seller, top_rated and feedback_ratings, an object with positive, neutral and negative entries that each carry m1, m6 and m12 counts. Observed in a live probe (seller musicmagpie, domain co.uk): HTTP 200, ok true, meta present and data.seller_profile an object containing seller, feedback_score, positive_pct_12mo, feedback_ratings and detailed_seller_ratings among other fields. The stored source example is not probe-verified and its meta reports domain com; it shows feedback_score as a large integer, feedback_positive_pct and positive_pct_12mo as percentages such as 99.1, items_sold_display and followers_display as abbreviated display strings such as "51.1M" and "487K" rather than numbers, member_since as a display date such as "Feb-02-11", location as a country name, business_seller and top_rated as booleans, and detailed_seller_ratings as scores on a five-point scale for Accurate description, Communication, Reasonable shipping cost and Shipping speed. The sample has a seller field and no store_name, so do not assume store_name is always present. The sample meta also carries record_count and a feedback_upstream_error flag (false in the sample), which is worth logging. Only one seller (musicmagpie) was probed; behavior for unknown seller names was not exercised.

Send a request only when you choose to 1 required, 1 optional
ParameterInValue
body
body

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X POST 'https://api.opendata-api.com/api/project/ebay/seller-profile?key=<API_KEY>' \ -H 'Content-Type: application/json' \ -d '{"seller":"<seller>"}'

Listing, item and seller capabilities

Pull structured eBay marketplace data as JSON from ebay.com, ebay.co.uk, ebay.de and other eBay domains, with no eBay developer account, OAuth tokens or HTML parsing on your side.

  • Listing search: keyword queries with condition, price range, buy-it-now, auction, best-offer, free-shipping, returns, location and pickup filters, sorted and paged
  • Item detail: the full record for one listing by item ID or listing URL, with price, seller, shipping, returns, item specifics and variation fields
  • Batch item lookup: several item IDs in one request, with unresolved IDs reported in a separate not_found list
  • Seller storefront: every active listing of a seller by username, with search-style filters, sorting and paging
  • Seller profile: feedback score, positive-feedback rates, rating counts by time window and top-rated or business flags
  • Daily deals: the current deals grid with sale price, was-price and shipping label
  • Category lookup: resolve a category name to its numeric ID, plus the top-level departments of a marketplace

RESTful JSON API for price monitoring, competitor storefront tracking, deal feeds, sourcing research and catalog enrichment. Results describe active listings and public seller information; they are not sold-price history.

Guides