E-commerce data API
An e-commerce data API is a web service that returns structured product data — price, currency, availability, seller, ratings, reviews, variants, images and identifiers — from online marketplaces as clean JSON, instead of raw HTML you have to scrape and parse yourself. ShopAPIS is a B2B e-commerce data API that returns 40+ fields per product across 70+ marketplaces in 30+ countries, normalized to one schema so a query against Amazon and a query against Alibaba come back in the same shape.
One request in, normalized product JSON out. You send an identifier (ASIN, SKU, GTIN/EAN, or product URL) and a marketplace; ShopAPIS returns the live product object — no proxies, no headless browsers, no per-site parser to maintain.
What an e-commerce data API returns
An e-commerce data API turns a marketplace product page into a typed record. Where a browser shows pixels and a scraper sees brittle HTML, the API gives you fields you can store, diff and join. ShopAPIS normalizes every marketplace to a shared schema with 40+ fields per product, including:
- Pricing — current price, currency, list/strike price, discount, Buy-Box price, price history.
- Availability — in-stock flag, stock level where exposed, shipping cost and estimated delivery.
- Catalog — title, brand, category path, description, bullet features, up to dozens of images.
- Social proof — average rating, review count, and review/Q&A text where available.
- Variants — size/color/configuration options with per-variant price, stock and SKU.
- Seller — store name, seller ID, fulfillment type (e.g. FBA), ratings.
- Identifiers — ASIN, SKU, GTIN, EAN, UPC, MPN, and the canonical product URL.
Identifiers: how products are addressed
Every product is addressable by an identifier, and ShopAPIS speaks all of the common ones. Marketplaces disagree on which to use, so the API accepts whichever you have and resolves the rest:
- ASIN — Amazon’s 10-character product ID, unique per marketplace domain.
- SKU — a seller’s internal stock-keeping unit; useful for your own catalog joins.
- GTIN / EAN / UPC — the GS1 global trade item numbers printed as barcodes; the universal cross-marketplace key.
- MPN — manufacturer part number, for matching the same product across stores.
Resolving GTIN/EAN to a marketplace listing is what makes catalog matching and competitor mapping possible — see catalog enrichment.
Sample response
{
"marketplace": "amazon",
"country": "US",
"identifiers": { "asin": "B0CHWRXH8B", "gtin": "0194253433814", "mpn": "MTUW3LL/A" },
"title": "Apple AirPods Pro (2nd Generation) with USB-C",
"brand": "Apple",
"price": { "current": 189.99, "list": 249.00, "currency": "USD", "discount_pct": 24 },
"availability": { "in_stock": true, "stock": 38, "ships_from": "Amazon.com" },
"seller": { "name": "Amazon.com", "id": "ATVPDKIKX0DER", "fulfillment": "FBA", "buybox_won": true },
"rating": 4.7,
"review_count": 51894,
"category": ["Electronics", "Headphones", "Earbud Headphones"],
"variants": [{ "sku": "MTJV3", "title": "USB-C", "price": 189.99, "in_stock": true }],
"images": ["https://m.media-amazon.com/images/I/61SUj2aKoEL._AC_SL1500_.jpg"],
"url": "https://www.amazon.com/dp/B0CHWRXH8B",
"fetched_at": "2026-06-05T11:42:03Z"
}Why this beats DIY scraping
Building your own scraper is one parser per site, forever — buying an e-commerce data API is one schema for all of them. Marketplaces rotate page layouts, throttle by IP and ship aggressive anti-bot stacks; a DIY pipeline spends most of its engineering budget on proxies, CAPTCHA solving and breakage triage rather than on the data product itself. The marketplaces hardest to parse — Amazon (Akamai + CAPTCHA), the China majors (GeeTest v4, device fingerprinting), Temu/Shein (no API, aggressive defenses) — are exactly the ones a data API earns its keep on. ShopAPIS absorbs the marketplace scraping layer so your team works with fields, not HTML.