2,500 free credits — no credit card required. Start building

SenseCollect logoSenseCollect
  • Sources
  • Solutions
  • Pricing
  • Tools
  • Blog
  • About
DocsGet API key
SourcesSolutionsPricingToolsBlogAboutDocs
Get API keyLog in
Reference · Amazon

Amazon review data errors

Review pulls fail in a small number of predictable ways, and most of them come down to what Amazon itself will show for that ASIN.

Get API keyAll API error codes

4 entries · returned with HTTP 200 · not transport failures

Reviews are collected from the public product page. What the page paginates is what the pull can reach — there is no back channel to reviews Amazon has chosen not to display.

Reviews are billed per review returned, so a short pull is a cheap pull rather than a wasted call.

4 entries
  • Product lookup2
  • Review coverage2

Product lookup

The ASIN did not resolve to a page worth reading.

ASIN not founduser-error

The identifier does not resolve on the marketplace being read.

Cause
ASINs are marketplace-scoped. An identifier valid on amazon.com can be absent from amazon.de, and delisted products stop resolving entirely.
Fix
Confirm the ASIN loads in a browser on the marketplace you are targeting before treating it as a data problem.
zero reviewsdata

The product page carries no reviews to collect.

Cause
Genuinely new or low-volume products, and variant ASINs whose reviews are consolidated onto a parent listing.
Fix
Try the parent ASIN. Amazon groups reviews across variants and the child page can legitimately show none.

Review coverage

Fewer reviews than the product's stated total.

fewer reviews than the count showndata

Amazon paginates a subset of reviews, not the full historical set.

Cause
The total on the product page counts every review ever left. The paginated view exposes a fraction of that, filtered and ordered by Amazon's own ranking.
Fix
Nothing to fix — the reachable set is the reachable set. Budget your limit against what the pagination exposes rather than the headline count.
published_at nulldata

The review carried no parseable date.

Cause
Date formats vary by marketplace and some localised formats do not parse cleanly into ISO.
Fix
Fall back to `raw` for the original string. The unified field is null precisely so you can tell a parse gap from an absent date.

Practices that prevent most of this

Check the parent ASIN first

Variant listings consolidate reviews upward. Pulling a child ASIN is the single most common reason a review call comes back thin.

Fall back to raw

Every record keeps the source payload under `raw`. When a unified field is empty, the original value is usually still there.

More references
API error codesEvery error code the SenseCollect API returns, what causes it, and how to fix it. Eight codes, their HTTP statuses, and the retry rules for each.Google Maps data errorsWhy a Google Maps pull returns fewer rows than expected, and why phone, email, or website comes back empty. Each cause with the parameter that fixes it.TikTok data errorsWhy a TikTok pull returns fewer posts than expected and why metrics or author fields come back empty. Each cause with its fix.
sensecollect/
SenseCollect logo

The local lead data API. One key, one unified schema, priced by the rows you get back.

No subscriptionCredits never expireNo per-call minimumRefund on failed runs

API

DocumentationResponse schemaMCP serverExplorerCatalog (JSON)Error codesChangelog

Sources

MapsAmazon reviewsTikTokAll sources

Guides

Leads by niche & cityLocal business leadsRestaurant leadsNo-website leadsExport Maps dataExport Amazon reviewsAuf Deutsch

Company

PricingComparisonsSolutionsToolsBlogAboutContact

Account

Get API keyLog inAPI keysCredits

© 2026 SenseCollect

Public data only. Review every response before you act on it.