Listing discovery
Use eBay endpoints to turn listing discovery into repeatable API requests with documented inputs and JSON responses.
Build resale, pricing, and marketplace workflows from structured eBay data.
Fetch eBay product, search, listing, and seller signals through documented API endpoints.
Endpoint families
4
Documented params
25
Examples
10
Live catalog snapshot
Active endpoints
10
Methods
GET, POST
Required params
19
Schema refs
10
{
"platform": "eBay",
"endpoint": "ebay-item",
"method": "GET",
"path": "/ebay/item/{item_id}",
"auth": "apiKey"
}Related use cases
Use cases
Fetch eBay product, search, listing, and seller signals through documented API endpoints.
Use eBay endpoints to turn listing discovery into repeatable API requests with documented inputs and JSON responses.
Use eBay endpoints to turn seller research into repeatable API requests with documented inputs and JSON responses.
Use eBay endpoints to turn price and availability monitoring into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live eBay endpoint catalog — 10 endpoints, 25 documented request parameters, and 10 published response schemas — the same catalog Docs and Playground run against.
10 documented eBay endpoints, grouped into 4 request families — Live, Seller and Item, plus 1 more.
25 request parameters are documented across those eBay endpoints, 19 of them required — the full input contract is public before you write any integration code.
10 of the 10 eBay endpoints ship a recorded example response, and 10 carry a documented response schema — you can code against the real JSON before the first request.
eBay endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
10 hosted MCP tools back the eBay endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/ebay/live/streams
/ebay/seller/{seller}
/ebay/item/{item_id}
/ebay/search
Endpoint catalog
/ebay/item/{item_id}Returns the details of one eBay listing by `item_id`: title, link, images, price and price text, condition, availability, item specifics, description, location and shipping. It also carries the seller's name, store, feedback score, followers and items sold, along with the listing's rating and rating count.
MCP tool ebay_item
/ebay/live/streamsLists live and upcoming eBay Live streams for one category channel, set with `category` (default `explore`; other values are channel ids such as `IPqZx79LNuwFcSVt` for Sports Singles). Each stream has its title, state, start time, watch count, hosts, tags and preview media. Host feedback is not included. Page on with `next_request_number` and `session_id`, passed back as `request_number` and `session_id`.
MCP tool ebay_live_streams
/ebay/live/streams/{id}Returns one eBay Live stream or event by `id`, taken from the `streams[].id` of the stream list. The response has title, description, state, start and end times, viewer, watch and like counts, tags, channels and the live, preview and replay URLs. Each host carries a 365-day feedback summary and four average ratings. An unknown id returns `404`.
MCP tool ebay_live_stream
/ebay/live/streams/{id}/itemsLists the items currently featured in an eBay Live stream, identified by the required event `id`. Each item has its listing id, title, price and currency, bid count, sale type, leader and winner usernames, and `auction_status` (`READY`, `LIVE` or `ENDED`). A stream with no featured items, or an unknown id, returns an empty `items` array.
MCP tool ebay_live_stream_items
/ebay/live/streams/batchReturns summaries for several eBay Live streams in one call. `ids` is required and takes up to 9 stream ids, comma-separated or repeated. Each stream has its title, state, watch count, hosts, tags and preview media, without the per-host feedback summary. Ids that do not resolve are silently omitted, and the order may differ from the request.
MCP tool ebay_live_streams_batch
/ebay/searchSearches eBay listings by keyword from a JSON body, with page, page size (60, 120 or 240) and a listing-status filter (`active`, `sold`, `completed` or `sold_completed`). Each result has the item id, title, link, image, price or price range, bid count, seller and rating, location, shipping information, and sold and watcher counts.
MCP tool ebay_search
/ebay/seller/{seller}Returns the public profile of an eBay seller by the required `seller` username: display name, store name and URL, profile URL, description, location, member-since date, positive feedback percentage, feedback count, items sold, followers, and detailed seller ratings. Feedback details are included when eBay provides them.
MCP tool ebay_seller
/ebay/seller/{seller}/aboutReturns seller about information from the eBay store about tab, including seller stats, top-rated status, optional location/member-since fields, and cleaned store categories.
MCP tool ebay_seller_about
/ebay/seller/{seller}/feedbackReturns the feedback eBay shows for a seller, identified by the required `seller` username. The response has the total feedback count, positive feedback percentage, overall rating summary, detailed seller ratings, and review cards with buyer, comment, rating, period and verified-purchase flag. Page with `page` (default 1) and `per_page` (24, 48 or 72; default 48), using `has_more` and `next_page`.
MCP tool ebay_seller_feedback
/ebay/seller/{seller}/shopLists the items in an eBay seller's shop, identified by the required `seller` username, one page at a time with `page` (default 1). Each result has its item id, title, link, image, price or price range, shipping note, location, bid count and watcher count. The response gives the `total` and a `has_more` flag.
MCP tool ebay_seller_shop
Related APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
Company coverage
eBay Inc. · EBAY
eBay is operated by eBay Inc. (EBAY). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the eBay endpoints above.
SEC filings & financials API →How to scrape eBay
eBay listings and seller signals power resale and pricing workflows. Crawlora's eBay endpoints return item, search, and seller data as structured JSON.
A single item, a search results page, or a seller's store and feedback.
Pass the item ID, search query, or seller name to Crawlora's eBay endpoint.
Receive title, price, condition, shipping, sold status, seller, and feedback as clean JSON.
Re-run on a schedule to track price changes, sell-through, and competitor listings.
客户端库
为你的语言安装 eBay 专用客户端。每个包都覆盖本页的 eBay 端点，并使用你的 API 密钥调用 Crawlora 托管 API。
npm install @crawlora-org/ebaynpmgo get github.com/Crawlora-org/crawlora-ebaypkg.go.devgem install crawlora-ebayRubyGemsnet.crawlora:crawlora-ebayMaven Centralcomposer require crawlora/ebayPackagistcargo add crawlora-ebaycrates.ioFAQ
Send an eBay item ID, search query, or seller name to Crawlora's eBay endpoint and get structured JSON — title, price, condition, shipping, seller, feedback — without writing parsers. Collect public data and respect eBay's terms.
Yes — Crawlora returns seller profile and feedback data plus listing details. It collects only publicly visible marketplace data, not private account information.
Collecting publicly accessible listing and seller data is generally permissible if you respect eBay's terms of use, robots directives, rate limits, and applicable law. This is for public data you're authorized to collect.
eBay's official Marketplace Insights API for sold data requires Business-level account approval and only returns the last 90 days — multi-year history is limited to eBay's own paid Terapeak tool inside Seller Hub. Crawlora reads eBay's public listing and sold-item pages directly, with no approval process and no 90-day window.