100 free credits. No credit card required.Start building
Logo
Amazon logoAmazon API

Get Amazon product and review data with one API

Fetch Amazon search, product detail, reviews, sellers, and shop pages as structured JSON with one SocialCrawl API key. Shared commerce schema. Reads are priced in credits.

Amazon logo
/v1/amazon

8 active endpoints. 1 and 5 credit tiers.

  • GET /v1/amazon/shop
  • GET /v1/amazon/product-search
  • GET /v1/amazon/product
  • GET /v1/amazon/reviews
  • GET /v1/amazon/sellers
  • GET /v1/amazon/best-sellers
  • GET /v1/amazon/deals
  • GET /v1/amazon/seller

What Amazon endpoints does SocialCrawl ship?

Eight live read endpoints for Amazon commerce. Shop pages, keyword search, ASIN product detail, reviews, seller offers, Best Sellers, deals, and seller profiles. Data API only. No buy, cart, or seller account tools.

Shop page

1 credit
/v1/amazon/shop

Product cards from an Amazon shop or storefront URL. Names, prices, ratings, images.

url

/v1/amazon/product-search

Keyword search across an Amazon marketplace. Product list with ASINs to deepen. Optional country and depth.

query, country, depth

/v1/amazon/product

Full product detail for one ASIN. Title, price, rating, images, attributes. Advanced tier (5 credits).

asin, country

/v1/amazon/reviews

Customer reviews for an ASIN. Rating, text, author, date. Advanced tier (5 credits).

asin, country

/v1/amazon/sellers

Seller and offer rows for a product ASIN. Price competition across the buy box surface.

asin, country

Best Sellers

1 credit
/v1/amazon/best-sellers

Ranked Best Seller listings for a category slug. Optional type for New Releases or Movers and Shakers.

category, country, type, page

/v1/amazon/deals

Amazon deals currently on the deals page. Deal price, list price, savings, and ASIN.

country

/v1/amazon/seller

One Amazon seller by seller id. Name, store URL, rating, and ratings count.

seller_id, country

Amazon API8 endpoints supported
View docs

Returns the products featured on an Amazon shop or storefront page: product name, price, rating, and image for each item.

Use it when you have a storefront page URL and want what that seller puts on it, rather than searching the whole catalogue.

1 credit

GET/v1/amazon/shop?url=https%3A%2F%2Fwww.amazon.com%2Fshop%2Fsydneydelrey

url · Full URL of the Amazon shop or storefront page

$ curl https://www.socialcrawl.dev/v1/amazon/shop?url=https%3A%2F%2Fwww.amazon.com%2Fshop%2Fsydneydelrey \
    -H "x-api-key: sc_YOUR_API_KEY"
idle
// Running this live needs your own API key. Hit "Try it" to see an example response

How the Amazon API works

Amazon is a normal SocialCrawl commerce surface. You call GET /v1/amazon/… with an API key, spend credits on live misses, and get a single JSON envelope back.

Authenticate every call

Send your key in the x-api-key header. No Amazon OAuth app for public reads. The same key works across SocialCrawl platforms.

GET with query params

All Amazon routes are GET. Pass asin, query, url, country, depth as query strings. We validate formats before charging.

Pay in credits, not seats

Shop, search, and sellers cost 1 credit. Product and reviews cost 5 credits. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.

The usual integration chain

Most products search first, then deepen only the ASINs that matter for detail, reviews, and sellers.

01Search
GET /v1/amazon/product-search?query=…

ProductList with ASINs, titles, prices

Resolve candidates before you spend advanced credits on detail.

02Product
GET /v1/amazon/product?asin=…

Full Product for one ASIN

Search cards are not a full PDP.

03Reviews
GET /v1/amazon/reviews?asin=…

ReviewList for the ASIN

VoC text lives on reviews, not product.

04Sellers
GET /v1/amazon/sellers?asin=…

SellerList of offers for the ASIN

Price and seller competition is a separate read.

request
GET /v1/amazon/product-search
  ?query=wireless+earbuds
  &country=US
  &depth=20
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

GET /v1/amazon/product?asin=B0FQFB8FMG&country=US
GET /v1/amazon/reviews?asin=B0FQFB8FMG&country=US
response envelope
{
  "success": true,
  "data": {
    "product": {
      "id": "B0FQFB8FMG",
      "title": "Example wireless earbuds",
      "price": { "current": 29.99, "currency": "USD" },
      "rating": 4.5,
      "url": "https://www.amazon.com/dp/B0FQFB8FMG"
    }
  },
  "credits_used": 5,
  "credits_remaining": 9995,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match other SocialCrawl commerce platforms. Parse once, reuse across Amazon, Walmart, and Target.

Productproduct

id (ASIN), title, price, rating, images, attributes, url, country context

ProductList / Postproduct-search, shop

items or shop cards with title, price, rating, ASIN or product url

ReviewListreviews

items[] with author, content.text, rating, published_at

SellerListsellers

offer rows: seller, price, condition, fulfillment hints

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint. Amazon is not a sidecar.

  1. 01

    Edge receives the call

    Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).

  2. 02

    Validate, then debit

    Registry lookup finds amazon/product-search (or product, reviews, sellers). Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before upstream work.

  3. 03

    Cache or fetch

    A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: product, reviews, search, and sellers run as live merchant reads; shop resolves from the storefront URL. Retries on 5xx/network with a circuit breaker if the source is unhealthy.

  4. 04

    Normalize and return

    Upstream JSON is mapped to commerce archetypes (Product, ProductList, ReviewList, SellerList, App, PlaceList as applicable), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.

Billing rules that matter in production

  • Shop / product-search / sellers live miss: 1 credit
  • Product by ASIN: 5 credits
  • Reviews by ASIN: 5 credits
  • Cache hit: 0 credits
  • Empty / hard fail: auto-refund
  • Bad params: 400, never charged
  • No credits: 402, never charged
  • country selects the Amazon marketplace
  • No cart, buy, or seller-write routes

How we get the data

Amazon is public marketplace data. We normalize it into the SocialCrawl commerce schema so your code does not learn a second merchant SDK.

What Amazon is for this API

Public product search, PDP detail, reviews, seller offers, and influencer shop pages. Read-only. No purchase or Seller Central access.

How SocialCrawl reaches it

Product, reviews, search, and sellers are read live from Amazon's public marketplace surface. Shop pages resolve from the storefront URL you pass. One SocialCrawl key covers all of them.

What leaves our edge

A unified JSON envelope with Product, ProductList, ReviewList, and SellerList archetypes shared across commerce platforms.

What we do not ship live

No cart, checkout, inventory, or advertising write APIs. No private Seller Central metrics.

field map sketch
ASIN / marketplace rowproduct.*title, price, rating, images
review payloadReviewList items[]stars, body, author, date
offer matrixSellerListsellers competing on the ASIN

What this API is used for

The jobs this API is most often used for.

8active Amazon endpoints in the registry
1 / 5credit ladder for shop/search vs product/reviews

ASIN research, review mining, and offer monitoring

Callers search by keyword, resolve ASINs, then fan out to product, reviews, and sellers. ASIN product and reviews at a flat 5 credits, sellers and search at 1, one key across SocialCrawl.

Search and detail are typically a few seconds on live miss. Cold marketplace queries can run longer.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Category managers

Python, notebooks, BI

product-search by keyword, then product and sellers for shortlists of ASINs.

Voice-of-customer teams

Node, warehouses

Pull reviews by ASIN for brand and competitor language. Advanced tier, cache friendly on repeats.

Pricing ops

Go, workers

sellers plus product for offer and list-price checks on a fixed ASIN set.

Call it in two lines

Search and sellers are 1 credit. Product and reviews are 5. Cache hits are free.

curl "https://www.socialcrawl.dev/v1/amazon/product-search?query=wireless+earbuds&country=US&depth=20" \
  -H "x-api-key: sc_your_api_key_here"
curl "https://www.socialcrawl.dev/v1/amazon/product?asin=B0FQFB8FMG&country=US" \
  -H "x-api-key: sc_your_api_key_here"
Amazon logoAmazon on SocialCrawl

Same key as the rest of the catalog

Endpoints

What data does the Amazon API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

Comparison

How does SocialCrawl compare to Amazon PA-API for Amazon data?

Same Amazon data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Authentication

SocialCrawl
One x-api-key header; works the moment you sign up
Amazon PA-API
Requires an Amazon Associates account with qualifying affiliate sales

Setup

SocialCrawl
One GET request; no SDK or request signing required
Amazon PA-API
Signed requests via AWS-style credentials and the PA-API SDK

Rate limits / quotas

SocialCrawl
Flat credit pricing regardless of sales volume
Amazon PA-API
Request quota scales with the affiliate revenue you generate

Response schema

SocialCrawl
Unified commerce schema shared with Google Shopping and Trustpilot
Amazon PA-API
PA-API-specific resources model built around affiliate use cases

Data coverage

SocialCrawl
Shop pages, product search, detail, full review text, and seller profiles
Amazon PA-API
Strong product catalog data, but no customer review text and no influencer shops

Pricing

SocialCrawl
Standard calls cost 1 credit, advanced 5; 100 free credits at signup
Amazon PA-API
Free, but access lapses if your affiliate sales drop
FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

Contact us
How do I scrape Amazon influencer shops with an API?
SocialCrawl provides 8 Amazon endpoints: influencer shops, product search, product detail, reviews, and sellers. For shops, send a GET request to /v1/amazon/shop with the shop URL and receive shop info, products, prices, ASINs, and images in a unified JSON response.
What data does the SocialCrawl Amazon API return?
The endpoint returns the shop name and bio, the influencer's name and avatar, and a products array, each item with title, price, ASIN, image URL, and Amazon product URL. All fields follow our unified schema shared across 51 platforms.
How much does the SocialCrawl Amazon Shop API cost?
Each Amazon shop request costs 1 credit on the standard tier. New accounts get 100 free credits with no credit card required, so you can pull around 100 shops before paying anything.
Is scraping Amazon shop pages legal?
SocialCrawl reads only publicly accessible Amazon shop pages, the same content anyone can see by visiting the URL. You are responsible for making sure your use case complies with Amazon's terms of service and applicable data protection laws. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.
Can I use the Amazon API in production?
Yes. The endpoint is built for production workloads with consistent response times, upstream retry handling, and a unified schema that stays stable when Amazon changes their page layout.
What is the best Amazon scraper API?
SocialCrawl's Amazon API gives you 8 endpoints: influencer shops, product search, product detail, reviews, and sellers, in one unified schema, with no Associates account, proxy pool, or CAPTCHA handling. Standard calls cost 1 credit, advanced 5, and new accounts start with 100 free credits, no credit card required.
Is there an Amazon data API?
Yes. Amazon runs official APIs, the Selling Partner API for your own seller account and the Product Advertising API for Associates, but both are gated behind account approval and qualifying sales, and the PA-API returns no customer review text. SocialCrawl reads public Amazon data without those gates: 8 endpoints cover influencer shop pages, keyword product search, full product detail, product reviews, and seller profiles in the commerce schema shared with Google Shopping and Trustpilot. Standard calls cost 1 credit, advanced 5, and signup includes 100 free credits.
Amazon scraping API vs the official Amazon API: what's the difference?
With SocialCrawl there is no app review or approval queue. Sign up and call Amazon endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Read the Amazon API reference in the docs

🤖 AI agent or LLM? Read this page as markdown