GTM Tech Stack

November 9, 2026

Amazon search API · keyword results as JSON with SearchApi

Visit SearchApi

SearchApi’s Amazon Search API turns a keyword into Amazon results as JSON. See what one call returns, what it leaves out, and a sample monthly bill.

The short answer

An API is a way for your code to ask a service for data and get it back. Pick SearchApi’s Amazon Search API if your code needs to send a keyword and get Amazon’s search results back as JSON, a plain text format that code can read. SearchApi is a third-party company, and it is not part of Amazon.

Pick a scraper API if your job is full product pages, every seller offer or review text for thousands of products. A scraper API is a tool that fetches whole web pages for you and pulls the data out of them. A search API only returns the results list.

SearchApi sells monthly plans by number of searches. Its Developer plan is $40 a month for 10,000 searches, and it bills only searches that come back with a 200 status code, the code for a successful request. A request is one call your code makes to the API.

What one Amazon search call returns

A SERP is a search engine results page, the list you see after you type a search. A search API returns that list as data. In SearchApi, you set engine=amazon_search and put your keyword in q. The docs list optional settings for the Amazon country site, sort order, price range and page number.

The example response in the docs lists each result under organic_results. Each result shows its position, the ASIN, the title, brand, rating, review count, price and a link. An ASIN is Amazon’s ID number for one product. The example also shows a count of other offers for the product and the lowest of those prices. Treat the example as the shape of a response, and check a real response for the fields you need before you build on them.

Handsketch of a keyword going into a box labelled engine amazon_search, with an arrow to a list of product cards, each card showing ASIN, title, price and rating
One keyword goes in, and a list of product cards comes back as JSON.

Search results are not the whole product page

A search result shows what the Amazon results page shows. That is enough to track where products rank for a keyword and what they cost. It does not give you the full product description, the list of every seller, or the text of reviews.

SearchApi’s docs list separate Amazon Product and Amazon Offers APIs for product details and seller offers. Each one is another request on your plan, so count those calls in your budget. The Amazon Search docs do not cover review text, so check which tool covers it before you plan a reviews project.

Handsketch of a search results card with an arrow to a second box labelled product call and a third box labelled offers call, with a note saying each call is another request
Product details and seller offers each take another request.

A sample monthly bill

SearchApi counts plan usage in credits, the units a plan gives you to spend on searches. The bill below counts each Amazon request as one search on the plan. Run a few test calls and check your account’s usage to confirm how your plan counts them before you rely on the bill.

The math: you track 100 keywords once a day, first results page only, for 30 days. 100 × 30 = 3,000 searches. You also pull product details for 20 products once a day, which is 20 × 30 = 600 more requests. 3,000 + 600 = 3,600 requests, which fits inside the Developer plan’s 10,000 searches for $40 a month.

SearchApi’s pricing also says you can use up to 20% of your plan’s credits in any one hour. If you run a big batch, spread it across several hours so it stays under that limit.

Handsketch of a plan card reading Developer, $40 a month, 10,000 searches, with 3,000 keyword searches and 600 product calls stacked inside it and a sticky note saying test the count first
The sample bill fits inside the Developer plan if each call counts once.

When a scraper API fits better

Some jobs need many pages per product, full reviews, or data for whole categories every day. Those jobs fit a scraper API better, because a search API returns one results list per call. If your project starts with keywords and ranks, start with the search API, and add a scraper later only for the gaps.

Handsketch of a fork with one path labelled keyword ranks and prices leading to a search API, and another path labelled full pages and reviews leading to a scraper API
Keyword ranks and prices fit a search API, and full pages fit a scraper API.

What to do this week

Sign up for SearchApi’s 100 free requests. Run amazon_search on five of your real keywords, then check which fields come back and how many requests your account used. Then multiply by your daily keyword count to see which plan you need.

Try SearchApi

Next · SearchApi review covers the tool as a whole · Web search APIs compares search APIs by what they return.

Sources · SearchApi Amazon Search API documentation, viewed November 9, 2026 · SearchApi pricing, viewed November 9, 2026

Open the live tool this note is about.