Skip to main content
Glade API gives you the data layer for Amazon product research. Whether you’re validating a new product idea, tracking competitors, or building a product catalog, this guide shows you how to combine Glade’s endpoints to get the insight you need.

​
Searching for products

GET /api/amazon/search returns ranked product results for a search phrase. Pass searchTerm, then add optional filters to narrow the result.
Supported query parameters: The response includes these fields under data.amazonProductSearchResults:
  • productResults.results[] — the ranked product list. Each item contains title, asin, price, rating, ratingsTotal, isPrime, sponsored, and coupon.
  • productResults.pageInfo — pagination metadata: currentPage, totalPages, and hasNextPage.
Use hasNextPage to drive a loop when you need to collect results beyond the first page.

​
Fetching full product details

Search results give you enough to triage a product, but for deep research you need the full record. After collecting ASINs from search, call GET /api/amazon/product for each one to retrieve the complete data set. Available fields on a full product record:

Identity & listing

title, subtitle, brand, asin, url, isNew

Pricing & availability

price, isInStock, isPrime, coupon, seller

Media

mainImageUrl, imageUrls[]

Content & specs

featureBullets[], technicalSpecifications, categories, rating, ratingsTotal
The following TypeScript example wraps the product endpoint in a typed helper:
On a plan that includes GraphQL, you can request a subset of fields from one operation to reduce response payload size.

​
Analyzing best sellers

Best-seller rankings tell you which products have the highest sustained sales velocity in a category. Glade API exposes two endpoints to make use of this data. List best sellers in a category:
Each product in the response includes a bestSellersRank value. Lower ranks (closer to #1) indicate higher sales volume. Track rank movement over time to spot rising products before they become dominant. Browse all available best-seller categories:
Use GET /api/amazon/bestseller-categories to discover valid categoryId values for the marketplace you’re researching. Categories are hierarchical — you can drill down from broad departments to specific niches.

​
Converting between ASINs and GTINs

ASINs are Amazon-specific identifiers, but the wider retail world uses GTINs (Global Trade Item Numbers), which include UPCs and EANs. Glade API lets you translate between the two when you need to cross-reference Amazon data with external databases.
Common use cases for ASIN/GTIN conversion:
  • Catalog enrichment — you have a retailer database keyed by UPC and want to add Amazon pricing, ratings, or review data.
  • Competitor mapping — you know a competitor’s barcode from a physical product and want to find their Amazon listing.
  • Inventory reconciliation — you manage warehouse stock by GTIN and need to match items to their corresponding Amazon listings for repricing or listing management.

​
Sales estimates

Before entering a category or launching a competing product, you need a consistent demand signal. GET /api/amazon/product/sales returns a current-rank unit-sales run-rate projection at three time horizons:
These values are scaled from the same point-in-time rank input. They are not independent historical windows, so the weekly field cannot establish a seasonal surge and the monthly field does not smooth 30 days of observations. Check status, scope, dataFetchedAt, methodology, and periodSemantics before using the projection. Group sibling ASINs only when familyDeduplicationKey is present. The operation does not currently return historical revenue, independent calibration results, or confidence intervals. See the sales-estimates reference for the full response and limitations.
Use the projection as one labeled input to product research. Preserve its model version and retrieval time, avoid double-counting known sibling variations, and do not present it as actual seller revenue.