Hey Product Hunt 👋 I built Ecommerce Data API because every Amazon research project I started died in the same place: the plumbing. Getting product details was one vendor with one auth scheme and one response shape. Sales estimates were another. Keyword data was a third, and it returned nested JSON that looked nothing like the first two. Before writing a single line of actual research logic, I'd burned a week on adapters, retries, and normalizing the same concepts across four dashboards. So I stopped building features and built the layer underneath them. Ecommerce Data API puts product details, sales estimates, reviews, keyword reverse-lookup, category demand, traffic sources, and trademark checks behind one endpoint family, one auth header, and one response shape. You learn the API once. Two things I'm particularly happy about: → A remote MCP server, so you can point Claude or Cursor at your Amazon data and just ask questions. No glue code, no CSV exports. → Instant test requests in the dashboard. You can fire a real call and see the actual payload before you commit to a subscription — I was tired of docs that describe a response you never quite get. It's aimed at sellers doing product research, analysts building market reports, and developers wiring automation into their own tools. Would love to hear what data you'd reach for first — and what's missing. I'll be around all day.

Ecommerce Data API

Amazon product research data, one unified API

Amazon product research data, one unified API