Catalog enrichment API
A catalog enrichment API fills the gaps in your PIM, product catalog or marketplace feed with clean, structured product content. ShopAPIS powers it by matching your SKUs on GTIN/UPC/EAN and returning title, description, images[], and attributes{} parsed from live marketplace listings across 70+ marketplaces in 30+ countries. You send an identifier or product URL; ShopAPIS returns the enriched record ready to write back to your catalog.
Catalog enrichment is identifier-in, attributes-out — you give a GTIN or UPC and get back the title, copy, images and spec attributes a complete product page needs. That is what turns a bare SKU row into a sellable listing.
Fields that power enrichment
| Field | What it fills |
|---|---|
title | A clean, normalized product name for catalog and search. |
description | Long-form marketing and spec copy. |
images[] | High-resolution image URLs for the gallery and feed. |
attributes{} | Structured specs — color, size, material, dimensions, model. |
gtin / upc / ean | The identifier used to match and de-duplicate across sources. |
brand / category | Taxonomy and brand fields for PIM organization. |
These are part of the 40+ field object documented on the product data API pillar, so enrichment, pricing and reviews share one schema.
GTIN/UPC matching
ShopAPIS resolves your catalog against marketplace listings primarily on global identifiers — GTIN, UPC, EAN, and where available ASIN — so the title and images you get back belong to the exact product, not a near-match. When an identifier is missing, title-and-brand fuzzy matching fills the gap, with a confidence score returned so you can gate auto-writes to your PIM.
Why an API beats DIY
Enriching a catalog by hand — copy-pasting titles, downloading images, retyping specs — does not scale past a few hundred SKUs, and breaks every time a manufacturer revises a spec. Scraping it yourself means parsing dozens of marketplace templates and surviving anti-bot stacks tuned for an internet where bots are roughly 51% of traffic (Imperva 2025 Bad Bot Report) , which drives high block rates, then writing identifier-matching logic per source. ShopAPIS returns the enriched record on one schema, GTIN-matched and de-duplicated, so your data team writes to the PIM instead of maintaining crawlers. The scraping internals are on the marketplace scraping API pillar.
Sample request and response
GET /v1/enrich?gtin=0888462079525&fields=title,description,images,attributes
Authorization: Bearer YOUR_API_KEY{
"gtin": "0888462079525",
"match_confidence": 0.98,
"title": "Apple iPad (10th generation) Wi-Fi 64GB - Blue",
"brand": "Apple",
"category": "Tablets",
"description": "10.9-inch Liquid Retina display, A14 Bionic chip, USB-C...",
"images": [
"https://cdn.shopapis.com/img/ipad10-front.jpg",
"https://cdn.shopapis.com/img/ipad10-back.jpg"
],
"attributes": {
"color": "Blue",
"storage": "64GB",
"connectivity": "Wi-Fi",
"screen_size_in": 10.9
},
"fetched_at": "2026-06-05T08:30:00Z"
}Use cases
- PIM enrichment — auto-fill missing titles, copy, images and specs on identifier match.
- Feed completion — meet marketplace listing-quality requirements for new SKUs.
- De-duplication — collapse duplicate catalog rows onto a single GTIN.
- Assortment expansion — pair with competitive intelligence to onboard competitor SKUs fast.
Marketplaces commonly used for enrichment
Related solutions
Enrich your first SKUs free in the dashboard — match on GTIN and write straight back to your PIM.