DocumentationDashboard

Amazon

Amazon cookies

Every other endpoint on the platform runs on our own infrastructure. Amazon reviews are the exception: the pager behind them answers a signed-in browser session and nothing else, so amazon/product-reviews takes a cookies parameter — a session you supply, sent with the request.

Why yours and not ours

Amazon mints a CSRF token per session and refuses a review request that does not carry both it and the cookies it was minted for. One shared session would mean one Amazon account rate-limiting every customer on the platform — and it would only ever see the reviews that account can see, in its marketplace and its language. The cookies you send go to Amazon and nowhere else; nothing here ever stores or echoes them back.

Copying the cookie header

  1. Sign in to the marketplace you want reviews from. Each one is a separate session — amazon.com.tr cookies do not work on amazon.com.
  2. Open any product's review page (“See all reviews”).
  3. Open DevTools with F12 (or ⌥⌘I on a Mac) and switch to the Network tab.
  4. Reload the page. Click the first request in the list — the document one, named after the page itself.
  5. Scroll to Request Headers and find the line beginning cookie:. Right-click → Copy value, or select the whole line by hand.
  6. Pass it as cookies — in the playground, or on your own call.

What you copy looks like this — one long line of name=value pairs separated by semicolons:

session-id=258-1598376-4724304; i18n-prefs=TRY; ubid-acbtr=258-0290756-3019815;
at-acbtr=Atza|…; sess-at-acbtr=…; session-token=…; csm-hit=…
curl -G https://data-api.roketfy.com/v1/amazon/product-reviews \
  -H "Authorization: Bearer <your-api-key>" \
  --data-urlencode "asin=B0CHX1W1XY" \
  --data-urlencode "domain=amazon.com.tr" \
  --data-urlencode "cookies=session-id=…; at-acbtr=…"

When they stop working

  • Amazon sessions expire, and signing out of the browser you copied them from ends them early. The endpoint reports it plainly rather than answering an empty page: it says the review page carried no CSRF token, which means the cookies were rejected.
  • Copy a fresh header the same way and send it on the next call.
  • Cookies are per marketplace. Reviews for a .com.tr listing need a .com.tr session.

What it costs

Ten credits a page. One call fetches the review page — rendered, with your cookies attached — for the CSRF token and the review count; the second posts to Amazon's own pager for the reviews themselves. The rendered fetch is what carries the cost: the page assembles itself in the browser, so it has to be run, not just downloaded. As everywhere else, a failed call is not charged.