ResellerRatings APIresellerratings.com ↗
Access ResellerRatings.com data via API: search stores, retrieve reviews, ratings distributions, business highlights, and reviewer profiles across thousands of retailers.
What is the ResellerRatings API?
The ResellerRatings API exposes 7 endpoints covering store search, category browsing, detailed store profiles, paginated customer reviews, business highlights, and reviewer profiles from ResellerRatings.com. The get_store_details endpoint alone returns over a dozen fields including lifetime, yearly, and six-month star-rating distributions alongside comparison suggestions and the first page of reviews in a single call.
curl -X GET 'https://api.parse.bot/scraper/dd7777f8-2968-4328-a349-1cdbcaaa1252/search_stores?query=Amazon' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace resellerratings-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: ResellerRatings SDK — search stores, browse categories, read reviews and highlights."""
from parse_apis.resellerratings_api import ResellerRatings, Store, Category, Review, Highlight, StoreNotFound
rr = ResellerRatings()
# Search for stores by keyword
for result in rr.stores.search(query="electronics", limit=5):
print(result.id, result.description)
# Get full store details by slug
store = rr.stores.get(slug="Amazon")
print(store.name, store.rating, store.review_count)
# Browse paginated reviews for the store
for review in store.reviews.list(limit=3):
print(review.title, review.star_rating, review.user_name, review.date)
# Get business highlights (shipping, payments, policies)
hl = store.highlights()
print(hl.seller_groups, hl.categories)
# List all categories and drill into one
cat = rr.categories.list(limit=1).first()
if cat:
detail = rr.category(seo_name=cat.seo_name).details()
print(detail.name, detail.seller_count)
for sub in detail.children:
print(sub.name, sub.seller_count)
# Look up a reviewer profile with typed-error handling
try:
reviewer = rr.reviewers.get(username="mark653912336")
print(reviewer.user_name, reviewer.review_count, reviewer.join_date)
except StoreNotFound as exc:
print(f"not found: {exc}")
print("exercised: stores.search / stores.get / reviews.list / highlights / categories.list / category.details / reviewers.get")
Full-text search across all stores on ResellerRatings. Returns matching store records with numeric IDs, category facet counts, and total results found. Each record includes the store's numeric ID usable for further lookups.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword to match against store names and descriptions. |
{
"type": "object",
"fields": {
"found": "integer total number of matching stores",
"facets": "object mapping category names to result counts",
"records": "array of store search result objects each with id and description"
},
"sample": {
"data": {
"found": 376,
"facets": {
"categoryliterals": {
"shopping": 48,
"computers & electronics": 101
}
},
"records": [
{
"id": 22850,
"description": "sign up to amazon prime..."
},
{
"id": 2077,
"description": ""
}
]
},
"status": "success"
}
}About the ResellerRatings API
Store Search and Category Navigation
The search_stores endpoint accepts a query string and returns matching stores with numeric IDs, a found count, and a facets object that maps category names to per-category result counts — useful for building category-aware search interfaces. list_categories needs no parameters and returns every top-level category with its seoname, id, and image paths. To drill into a category, pass the seoname value to list_stores_by_category, which returns the parent category's seller_count and a children array of subcategories with their own seo_name and seller_count fields.
Store Details and Reviews
get_store_details is the core endpoint. Provide a case-sensitive store_slug (the seoName from search or category results) and get back the store's rating, reviewCount, distribution object (lifetime/year/sixmonth breakdowns), a paginate object with totalPages and totalResults, and a compare_suggested array of similar stores. For paginated review access, get_store_reviews takes the same store_slug plus an optional page parameter and returns 15 reviews per page ordered by date descending. Each review object includes userName, date, starRating, title, comment, commentId, and location fields (city, state, country).
Business Highlights and Reviewer Profiles
get_store_business_highlights takes the seller_id (the databaseId from get_store_details) and returns structured data on shipping methods, payment options, refund policies, security certifications, contact information, and category rankings grouped under sellerGroups and sellerPolicies. The get_reviewer_profile endpoint accepts a username found in any review object and returns that reviewer's join_date, reviewCount, userAvatar, faveStores array, worstStores array, and full review history — useful for credibility scoring or filtering reviews by reviewer activity.
The ResellerRatings API is a managed, monitored endpoint for resellerratings.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when resellerratings.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official resellerratings.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate competitor store ratings and review distributions for e-commerce benchmarking dashboards.
- Build a retailer comparison tool using
compare_suggestedanddistributiondata fromget_store_details. - Monitor customer sentiment trends by fetching paginated reviews via
get_store_reviewsand trackingstarRatingchanges over time. - Enrich a business directory with shipping options, payment methods, and refund policies from
get_store_business_highlights. - Filter out low-credibility reviews by cross-referencing
reviewCountandjoin_datefromget_reviewer_profile. - Populate a category navigation tree using
list_categoriescombined withlist_stores_by_categorysubcategory data. - Surface reviewer reputation signals — favorite stores, worst-rated stores, total review history — alongside individual review content.
| 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 | 100 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 the `distribution` field in `get_store_details` contain?+
distribution object contains three nested breakdowns — lifetime, year, and sixmonth — each showing how reviews are distributed across star ratings for the corresponding time window. This lets you compare a store's all-time reputation against its recent performance without making separate calls.Does the API return review responses from store owners or merchant replies?+
get_store_reviews and get_store_details include the customer-side fields (comment, starRating, title, userName, location) but do not include merchant reply text. You can fork this API on Parse and revise it to add a dedicated endpoint that pulls merchant responses if they appear on individual review pages.How does pagination work for store reviews?+
get_store_reviews returns 15 reviews per page ordered by date descending. The page parameter is 1-based and optional (defaults to the first page). To know the total number of pages, call get_store_details first and read paginate.totalPages and paginate.totalResults before iterating pages with get_store_reviews.Does the API expose individual product reviews, not just store-level reviews?+
reviews arrays in get_store_reviews and get_store_details reflect customer experiences with a retailer as a whole, not with specific products. You can fork this API on Parse and revise it to target product-specific review pages if ResellerRatings surfaces them separately.