B2B Data API
Send us 50 rows of a real supplier file and judge the match quality yourself.
Send us 50 rows of a real supplier file and judge the match quality yourself.
The B2B data API is the same 1.6B+ product index, shaped for business pipelines instead of one-off lookups: match entire supplier catalogs by identifier, validate GTINs at intake, deduplicate product lists, and keep wholesale data enriched continuously through JSON, bulk exports, and webhooks.
TL;DR
- •Built for catalogs, not single lookups: batches, exports, and webhooks are the interface.
- •Match supplier lists to clean records by GTIN, catching duplicates and bad codes at intake.
- •Feeds ERPs, PIMs, and marketplace backends with one consistent JSON shape.
- •Same data as every EcomSource tool, so business and dev teams see one truth.
What is a B2B data API?
A B2B data API supplies product information at the scale and shape business systems need: whole catalogs in, validated and enriched records out. Where a retail lookup answers one shopper question, a B2B data API sits inside intake pipelines, matching what suppliers send against a reference index so downstream systems work from clean, deduplicated, identifier-anchored data.
The problems it removes
Supplier files that disagree: three distributors, three names for the same product. Matching by GTIN collapses them into one record.
Bad codes at intake: mistyped and invalid GTINs are caught by validation before they poison inventory and listings.
Thin records: names, brands, images, categories, and dimensions filled from the index, the workflow our B2B product information guide covers.
Slow onboarding: new supplier catalogs matched in one batch instead of weeks of manual review.
How teams wire it in
Pattern
How it runs
Intake validation
Every inbound supplier row hits the API, invalid or unknown codes are flagged before import
Batch enrichment
Nightly or weekly jobs push the catalog delta and pull enriched records, bulk CSV and JSON exports on the Professional plan
Event-driven sync
Webhooks notify your system when matched records change, so catalogs stay current without polling
Cross-system identity
ERP, PIM, and storefront all key products by GTIN, ending the internal-code translation game
Under the hood it is the same endpoint as the product data API, one POST with any identifier type, so a proof of concept takes minutes: the API documentation has the request in cURL, Node.js, and Python, and the free sandbox covers 10 calls a day.
A supplier onboarding, in numbers
A typical new-distributor file arrives with a few hundred rows: some codes valid, some mistyped, some products entered under names nobody downstream will recognize. Run it through intake matching and the output sorts itself: clean matches import automatically, invalid codes bounce back to the supplier with the row numbers, and ambiguous rows queue for a five-minute human pass. One-off versions of the same job run through the bulk barcode lookup without touching the API at all.
Where it fits next to the other APIs here
Use the product data API framing when a product tool needs records one call at a time. Use this page’s framing, batches, exports, webhooks, when the customer is a catalog operation. The data and the endpoint are shared, the plans differ by volume: sandbox free, $49 per month for 10,000 calls, $149 for 50,000 with bulk exports and webhooks, and custom enterprise volumes with database snapshots above that (pricing page, August 2026). Our guide to building data pipelines around product APIs shows reference architectures.
Prove it on your data
Send 50 rows of your messiest supplier file through the sandbox and judge the match quality on your products, not a demo.
Frequently Asked Questions
What is a B2B data API used for?
Matching, validating, and enriching product catalogs at pipeline scale: supplier list onboarding, GTIN validation at intake, deduplication, and continuous enrichment feeding ERPs, PIMs, and marketplace backends.
How is this different from the product data API?
Same index, same endpoint, different shape of use. The B2B framing centers batches, bulk exports, and webhooks for catalog operations, while the product data API framing centers per-call lookups inside tools.
Can we integrate via REST?
Yes. One POST endpoint, JSON in and out, authenticated with access and secret keys. Bulk exports and webhooks are available on the Professional plan, and the sandbox is free to test with.
How do you handle products you cannot match?
With a structured not-found or ambiguous status per row, never a silent guess, so intake pipelines can route unknowns to review instead of importing noise.
What does it cost at catalog scale?
Standard plans run to 50,000 calls per month at $149; genuine catalog-scale volumes are custom, including full database snapshots (pricing current as of August 2026). Treat any figure beyond the published plans as illustrative until scoped.