Anysite now provides an eBay API — giving you access to listings, sold prices, seller profiles, catalog products, and buyer reviews via simple POST requests, with no OAuth and no eBay developer account required.
eBay's native APIs are fragmented across the Browse API, Finding API, and Trading API, each with a separate auth scheme. Getting developer access requires app registration, approval, and ongoing credential management. Most teams skip eBay data entirely or maintain scrapers that break on every layout change. These nine endpoints remove that friction entirely.
What the eBay endpoints cover
The endpoint family is organized into four groups: listings, catalog products, sellers, and the category tree.
Listings
POST /api/ebay/items retrieves full details for a specific listing by item ID or URL. Response includes title, price, condition, images, buying format (fixed-price, auction, or best-offer), item specifics, quantity, and a seller summary.
POST /api/ebay/items/search searches active eBay listings by keyword. Each result includes title, price, currency, condition, image, buying format, shipping details, sold count, and watcher count. Filters available: condition, buying format, price range, and category ID.
POST /api/ebay/items/sold searches completed and sold listings by keyword — the real transaction price record. Each result includes title, sold price, currency, sold date, condition, buying format, image, and bid count for auctions. This is the endpoint that makes eBay valuable for pricing research: actual clearing prices, not asking prices.
Catalog products
POST /api/ebay/products retrieves catalog product details by ePID or catalog URL. Response includes title, brand, model, MPN, UPC, images, aggregate rating, price range across live listings, listing count, product specs, and category. Useful for PIM enrichment when you know the product but need structured metadata.
POST /api/ebay/products/reviews retrieves buyer reviews for a catalog product by product ID or URL. Per review: rating, title, text, author, date, verified-purchase flag, item condition, selling account, and helpful-vote count.
Sellers
POST /api/ebay/sellers retrieves a seller or store profile by username, store name, or profile URL. Response includes name, feedback count, positive feedback percentage, items sold, followers, location, logo, member-since date, and store description.
POST /api/ebay/sellers/feedback retrieves feedback reviews received by a seller. Per entry: rating, review text, reviewer alias and score, related item, purchase price, and period.
POST /api/ebay/sellers/items retrieves active listings for a seller by username or store URL. Per listing: title, price, currency, list price (if discounted), condition, subtitle, sold count, image, and buying format.
Category tree
POST /api/ebay/categories retrieves the full eBay browse category tree — every department, category, and subcategory with id, name, alias, parent_id, and browse URL. Use it to resolve category IDs for search filtering or to map eBay's taxonomy for classification pipelines.
eBay API use cases: what you can build
Price research and sold-price history
The sold listings endpoint returns actual transaction prices — what items cleared at, not what sellers are asking. Feed /api/ebay/items/sold results into pricing models, reseller dashboards, or inventory valuation tools. Cross-reference with /api/ebay/items/search to compare active asking prices against historical clearing prices for any keyword.
Seller due diligence
Before a bulk purchase or marketplace partnership, assess the counterparty. Combine the seller profile (feedback score, tenure, items sold count, location) with the full feedback history to surface risk signals — negative review patterns, recent score drops, or thin transaction history — without requiring an eBay developer account or any eBay login.
Product catalog enrichment
/api/ebay/products turns an ePID or catalog URL into structured metadata: brand, MPN, UPC, specs, images, and an aggregate rating with listing-count context. Paired with /api/ebay/products/reviews, you get buyer sentiment grounded in verified-purchase signals. Both are useful for PIM workflows where internal data is thin and you need a reliable external source for product attributes.
Marketplace monitoring
Track listing activity and pricing shifts over time by polling /api/ebay/items/search for keywords or /api/ebay/sellers/items for specific sellers. Watcher counts and sold counts in search results give signal on demand. Build alerts when a competitor undercuts price, a high-value item lists below threshold, or a seller's feedback score drops.
eBay API authentication
All nine endpoints use the same POST method with an access-token header — no eBay OAuth, no app credentials, no per-endpoint setup. All endpoints require an Anysite access-token header — no eBay-side OAuth setup needed. One token covers everything.
Pricing
Four endpoints (categories, items, products, sellers) are flat 10 credits per call. The five search/list endpoints are 10 credits per result batch (per 50 results for items/search, items/sold, and sellers/items; per 10 for products/reviews; per 100 for sellers/feedback). Credits are shared across all Anysite endpoints — no separate eBay quota to manage.
| Endpoint | Cost |
|---|---|
/api/ebay/categories | 10 credits |
/api/ebay/items | 10 credits |
/api/ebay/items/search | 10 credits per 50 results |
/api/ebay/items/sold | 10 credits per 50 results |
/api/ebay/products | 10 credits |
/api/ebay/products/reviews | 10 credits per 10 results |
/api/ebay/sellers | 10 credits |
/api/ebay/sellers/feedback | 10 credits per 100 results |
/api/ebay/sellers/items | 10 credits per 50 results |
Use the Anysite pricing calculator to model your exact usage before subscribing.
Get started
Full endpoint documentation, request parameters, and response schemas are at the eBay API endpoint page. Get an access token at anysite.io/pricing and make your first request in minutes.