What is this website?
Ecommerce Data API is a site that turns ecommerce research lookups into APIs. Its public catalog currently focuses on Amazon. Product, keyword, market, and traffic data use separate v1 paths, and the account can also search global trademarks and recognize Chinese and Latin text in images. The site includes leaderboards and a sales estimator. Field-level data requires registration and an API key, and calls draw from one shared balance. A program can call the REST API directly, or data can be pulled from the local command line inside Codex, Claude Code, or Cursor. The homepage states that this Amazon API catalog is still under development.
Core features
- Read a product title, price, rating, review count, and variations by ASIN.
- Discover search terms, reverse-lookup traffic keywords, and check ABA rank trends.
- Measure category size, brand concentration, price bands, and demand trends.
- Look up related products and keyword traffic flows to judge competitive relationships.
- Search trademark lists, details, registration status, and covering offices.
- Recognize Chinese and Latin text from an image URL, Base64 payload, or uploaded file.
Common use cases
- Product researchers compare a competitor's price, reviews, and variations with ASIN details and sales trends before locking a product.
- During a stocking window, operators place keyword ranks next to ABA trends to separate a one-week spike from sustained demand.
- Developers connect product or keyword endpoints to their own dashboards and scheduled jobs, then request data in bulk with a marketplace parameter.
- Brand owners check a name's registration status, and which countries or offices the data covers, before listing.
Who is it for?
- Developers and data teams who need Amazon research data inside their own systems.
- People who pull data in Codex, Claude Code, or Cursor through the local ecomdata CLI and Skill.
- Cross-border sellers who accept per-call pricing and use the API for product and keyword decisions.
- People who want to finish research by clicking through a visual interface and do not plan to call an API: the public leaderboards do not cover day-to-day lookups.
- People who need their own store orders, inventory, or advertising account: this is research data, not a seller backend.
How does it compare with similar tools?
When the job is to write a program that fetches Amazon research data, check whether the service puts products, keywords, markets, traffic, and trademarks on one balance and one set of v1 paths, and whether it provides OpenAPI and Postman examples. When the need is a store's own orders and advertising data, use the platform's official seller APIs rather than this kind of third-party research data. The docs state that Agent access goes through a local CLI and Skill and does not install a public MCP. Leaderboards and the sales estimator can show an overview first, while fields still follow the matching endpoint docs. The homepage also says the catalog is still in development, so marketplaces and fields can change.
FAQ
Q: Can Ecommerce Data API be called for free without a limit?
A: No. The pricing page offers monthly subscriptions and one-time call packs, and public endpoints share one balance. Subscription calls are granted monthly and reset at the end of the month. Call packs stay valid for 60 days. A successfully billed request deducts 1 call by default. If an endpoint states otherwise, follow its documentation.
Q: Are REST calls and Agent calls two different datasets?
A: No. The docs state that both modes share the API key, quota, and the current 45 v1 endpoints. The Agent calls those REST endpoints through the local ecomdata CLI and Skill, and it does not install a separate public MCP.
Q: Can a key be replaced after it leaks?
A: Yes. The account dashboard can create and revoke keys, and the full key is shown only once. Usage is recorded on the server by endpoint, status, latency, and billing unit for quota control and reports.
Q: Can sales-related figures be treated directly as official settled sales?
A: They should not be treated as the same figure. Product endpoints include research fields such as sales trends, and the site also has a sales estimator. Whether those numbers match platform settled sales depends on the data-definition page and the specific field documentation.
