Ecommerce Data API

What is this website?

Ecommerce Data API is a paid ecommerce research data API. It currently offers 45 v1 endpoints covering Amazon products, keywords, markets, and traffic, plus trademark search and image text recognition. Applications call the REST API with an API key; coding agents can query the same catalog through the CLI, a Skill, or MCP. Subscriptions and call packs share one balance. Sales, traffic, and conversion fields are estimates that can be revised, not official marketplace figures.

Core features

• The product group has 12 endpoints for searching items by marketplace and reading listings, price, BSR, ratings and review counts, offers, variations, history, and competitors.
• The keyword group has 11 endpoints for search-term mining, reverse traffic-term lookup, ABA rank, conversion, and trends over time.
• The market group has 14 endpoints for category size, product and brand concentration, price bands, rating distribution, and demand trends.
• The traffic group has 3 endpoints for related products, traffic sources, and related-traffic stats.
• The trademark set has 4 endpoints for search, details, registration-status stats, and coverage. One image-text endpoint accepts an image URL, Base64, or a file upload.
• Accounts can create and revoke API keys and review remaining balance, billable calls, request status, and latency. Docs include OpenAPI, Postman, and runnable examples. The local ecomdata CLI also includes watch for saving ASIN observations on the machine.

Common use cases

• Someone checking a competitor, after they have an ASIN, pulls title, brand, price, rating, and variations for a chosen Amazon marketplace to confirm it is the item they meant.
• Someone preparing ads or a listing uses reverse keyword lookup and ABA trends to see search terms, organic traffic share, and recent rank movement.
• A seller considering a category reviews concentration, price bands, and demand trends before buying inventory, then compares that with their own inbound timing.
• A data or backend team connects the API to a dashboard or scheduled job, or calls it through OpenAPI, Postman, or a client such as RapidAPI, within the purchased allowance.
• Someone already using Codex, Claude Code, or Cursor installs the CLI and Skill once for one-off questions in plain language. For a daily ASIN list, they use ecomdata watch, which stores observations locally.

Who is it for?

• Developers who need Amazon research data inside their own app, script, or data pipeline.
• Analysts who want occasional product, keyword, or trademark lookups inside a coding agent without writing each request.
• Side projects and small teams with fairly steady monthly volume who can accept charges per successful billable request.
• A poor fit for anyone who would treat sales, traffic, or conversion as audited marketplace numbers for finance or compliance.
• A poor fit for teams that need broad multi-marketplace coverage in one product, or unlimited free scraping. The public catalog focuses on Amazon, with trademarks and OCR alongside it.

How does it compare with similar tools?

Start with who sends the request. For a product feature or a scheduled job, use REST at https://ecommercedataapi.com, public version v1. For plain-language lookups in Codex, Claude Code, or Cursor, the installer sets up a Skill, the ecomdata CLI, and a local stdio MCP server. Clients that support remote MCP can add https://ecommercedataapi.com/mcp and sign in with browser OAuth. Local MCP exposes four generic tools: ecommerce_api_search, ecommerce_api_describe, ecommerce_api_call, and ecommerce_account. The remote server also exposes business endpoints as separate tools.

Billing follows successful requests. The English pricing page lists Starter at 900 calls and $9 per month, Pro at 3,500 calls and $29, and Business at 13,000 calls and $79. Unused subscription calls reset at month end; yearly billing is charged once but calls are still granted monthly. Call packs are one-time purchases valid for 60 days. One balance covers every public endpoint, with no per-seat fee. A successful billable request uses one call by default unless that endpoint's docs say otherwise. For higher volume, the pricing page points people to support@ecommercedataapi.com.

FAQ

Q: What can Ecommerce Data API query today?
A: The public catalog is 45 v1 endpoints: Amazon products, keywords, traffic, and markets, plus global trademarks and image text recognition. Requests need parameters such as marketplace; docs examples include the US, UK, and Japan stores. Fields depend on the response and that endpoint's docs.

Q: Are REST, Agent Skills, and MCP three different datasets?
A: No. The docs say they share one API key, the same credits, and the same REST endpoints. Local MCP talks over stdio and then calls the cloud API. The remote URL is https://ecommercedataapi.com/mcp.

Q: Can sales or traffic figures be used as a sales report?
A: That is not what the site claims. It describes sales, traffic, and conversion fields as research estimates that can be revised, not official figures disclosed by the marketplace.

Q: How are calls consumed, and do unused calls roll over?
A: Each successful billable request currently costs one call by default. Subscription calls are issued monthly and reset at month end. Call packs last 60 days. If the plan choice is unclear, email support@ecommercedataapi.com.