resellerratings.com APIresellerratings.com ↗
Access ResellerRatings.com store data via API: search stores, list categories, retrieve reviews, business highlights, and reviewer profiles.
curl -X GET 'https://api.parse.bot/scraper/dd7777f8-2968-4328-a349-1cdbcaaa1252/search_stores?query=Amazon' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for stores by name or keyword. Returns matching store IDs, facet counts by category, and total results found.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g. 'Amazon', 'Best Buy', 'Newegg') |
{
"type": "object",
"fields": {
"results": "object containing search response with code, data (records array, facets, found count, metadata)"
},
"sample": {
"data": {
"results": {
"code": 200,
"data": {
"found": 376,
"facets": {
"categoryliterals": {
"shopping": 48,
"computers & electronics": 101
}
},
"records": [
{
"id": 22850,
"description": "sign up to amazon prime for unlimited free delivery.",
"reviewcount": 0,
"overallscore": 0
}
]
}
}
},
"status": "success"
}
}About the resellerratings.com API
The ResellerRatings API exposes 7 endpoints covering store search, category browsing, paginated customer reviews, and seller business details from ResellerRatings.com. The get_store_details endpoint alone returns ratings distributions, comparison suggestions, seller metadata, and a first page of reviews in a single call. Use it to build price-comparison tools, reputation monitors, or shopping research applications without scraping the site yourself.
Store Search and Category Navigation
The search_stores endpoint accepts a query string (e.g. 'Amazon', 'Newegg') and returns a data object containing a records array of matching stores, facets broken down by category, and a found count. To explore stores by vertical, list_categories returns all top-level categories with categoryname, seoname, id, and images fields — no parameters required. Pass any seoname value into list_stores_by_category to receive that category's metadata and a children array of subcategories, each with its own seller_count.
Store Details and Reviews
get_store_details accepts a case-sensitive store_slug (matching the seoName field from search results) and returns a storeData block with aggregate ratings, a distribution breakdown across star values, seller_id, seller metadata, and pagination info alongside a first-page reviews array. For paginated access, get_store_reviews takes the same store_slug plus an optional page integer and returns review objects with userName, date, starRating, title, comment, commentId, city, state, country, and social share fields. Slugs are case-sensitive — a mismatch returns a stale_input flag rather than an error.
Business Highlights and Reviewer Profiles
get_store_business_highlights requires the numeric seller_id from get_store_details (at store.storeData.seller_id) and returns a deferredData object with contactInfo, sellerGroups covering shipping methods, refund policies, security certifications, and payment options, plus any sellerPolicies text. get_reviewer_profile accepts a username string as shown on reviews and returns userData with username, reviewCount, join_date, faveStores, worstStores, userAvatar, and a full reviews array. If the username does not exist, the API may return a fallback response rather than a structured error.
- Aggregate star-rating distributions across competing stores using
get_store_detailsratings data - Monitor new customer reviews for a specific seller by polling
get_store_reviewswith incrementalpagevalues - Map retailer coverage across verticals by combining
list_categoriesslugs withlist_stores_by_categoryseller counts - Surface payment methods and refund policies side-by-side using
get_store_business_highlightssellerGroups data - Build a reviewer credibility score by pulling
reviewCountandjoin_datefromget_reviewer_profile - Identify related stores to recommend via the
comparison suggestionsreturned inget_store_details - Enrich an e-commerce product database with verified seller reputation data keyed on store slug
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does ResellerRatings have an official developer API?+
What does `get_store_details` return beyond the store's overall rating?+
distribution object showing review counts at each star level, the numeric seller_id needed for business-highlights lookups, pagination metadata, a reviews array for the first page, and a comparison suggestions list of related stores.How do I find the correct `store_slug` value to pass into review endpoints?+
search_stores with a store name. Each record in the returned records array includes an seoName field — that value is the slug. Slugs are case-sensitive, so copy them exactly. Passing a mismatched slug returns a stale_input flag in the response rather than a 404 error.Does the API expose individual product reviews or only store-level reviews?+
get_store_reviews returns reviews tied to a seller as a whole, with fields like starRating, comment, city, and state. Product-specific review data is not exposed. You can fork this API on Parse and revise it to add a product-review endpoint if that data becomes accessible.Is there a way to filter reviews by date range or star rating?+
get_store_reviews accepts only store_slug and a page integer — no date-range or star-rating filter parameters are available. The API returns reviews in the order the source provides. You can fork this API on Parse and revise it to add filtering logic on top of the paginated results.