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
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/ebay/live/streams
/ebay/seller/{seller}
/ebay/item/{item_id}
/ebay/search
Endpoint catalog
/ebay/item/{item_id}Returns normalized details for a public eBay item listing.
MCP tool ebay_item
/ebay/live/streamsReturns currently live and upcoming eBay Live streams for a category channel.
MCP tool ebay_live_streams
/ebay/live/streams/{id}Returns normalized detail for a single eBay Live stream/event, including each host's feedback summary for the last 365 days.
MCP tool ebay_live_stream
/ebay/live/streams/{id}/itemsReturns the currently featured/auction items for an eBay Live stream, including live bidding state.
MCP tool ebay_live_stream_items
/ebay/live/streams/batchReturns normalized summaries for multiple eBay Live streams/events in one call, up to 9 ids per request.
MCP tool ebay_live_streams_batch
/ebay/searchReturns normalized eBay search results.
MCP tool ebay_search
/ebay/seller/{seller}Returns normalized details for a public eBay seller profile.
MCP tool ebay_seller
/ebay/seller/{seller}/aboutReturns normalized seller about information from the public 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 normalized seller feedback summary, detailed ratings, and recent review cards from the public eBay seller feedback tab.
MCP tool ebay_seller_feedback
/ebay/seller/{seller}/shopReturns normalized listings from the public eBay seller shop tab, with pagination backed by the store odtRefresh response.
MCP tool ebay_seller_shop
Related APIs
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.
Marketplaces & Retail
Turn public Shopify storefront JSON and sitemap surfaces into structured data for catalog monitoring, merchandising research, product discovery, and storefront intelligence 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.
FAQ
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.