209,670 served today 37 platforms
Point it at any store.
Get the whole catalog.
There is no single target site here: you supply the domain. One key reads any Shopify storefront on the web — the store profile, every product with every variant's price, sale price, SKU and stock, the collections they sit in, and the reviews customers left on them — as structured JSON. No Partner account, no app installed on the merchant's store, no per-store access token.
Trusted by developers shipping real products.
Request
$ curl -X POST \ https://api.fetchlayer.dev/shopify-stores/products \ -H "Authorization: Bearer ss-your-key" \ -H "Content-Type: application/json" \ -d '{"store":"allbirds.com","limit":250}'
Response
{
"products": [{
"handle": "mens-tree-runner-nz-natural-white",
"title": "Men's Tree Runner NZ - Natural White",
"vendor": "Allbirds",
"priceMin": "100.00",
"onSale": false,
"variants": [{ "sku": "A11914M080",
"price": "100.00", "available": true }]
}],
"nextCursor": "cGFnZT0y",
"notes": []
} Built for feedback workflows
Fetch the public signal. Use it wherever your team works.
Detection before you spend
Point /detect-store at a domain and it tells you whether it is Shopify, how confident that verdict is, which signals fired, and which of products, collections and metadata this store leaves published — before you spend a single request walking a catalogue that is switched off.
Themed and headless stores alike
Every classic storefront answers the same endpoints no matter how heavily it is themed or which custom domain it sits on. A headless store is read at the myshopify domain its own markup gives away, so a custom front end is no obstacle.
Variant-level catalogue
Not just titles and prices: every variant with its price, compare-at price, SKU, barcode, option values, weight, taxability and availability, plus the full description, the option matrix and every image with its dimensions.
Stock where the store publishes it
Stores that track inventory return inventoryQuantity per variant on /product-detail — the field that turns a catalogue snapshot into a restock and stock-out signal you can watch over time.
The store’s own merchandising
Collections show you how a merchant groups their catalogue, with titles, descriptions, images and product counts. Ask for one and it returns that collection’s products in full, in the same shape as a catalogue walk.
Partial answers announce themselves
Every response carries a notes array reporting truncated walks, upstream limits and fields this particular store does not publish. An empty notes means complete; entries in it tell you exactly what is missing and why.
AI-ready JSON
Hand product titles, descriptions, tags, prices and variants to an LLM or an MCP agent to cluster a catalogue, diff two stores, or write the sourcing brief — no HTML parsing, no per-store wrapper code.
Price a competitor’s whole catalogue with AI—then export it to CSV.
Prefer not to write code? Give FetchLayer Research Chat a store domain, ask what it sells and what it charges, and turn the entire catalogue into a structured file for your pricing model, sourcing shortlist, or category review.
- ✓Ask questions in plain English
- ✓Analyze themes, sentiment, and pain points
- ✓Download the structured results as CSV or JSON
No code or setup required · Uses your FetchLayer credits
Pull this store’s full catalogue, break it down by product type and price band, flag everything currently discounted, then export it as CSV.
I walked all 412 products, grouped them into nine product types, and marked the 38 items currently sitting below their compare-at price. The variant-level breakdown with SKUs and availability is ready to download.
shopify-store-catalog.csv
1,284 variants · 14 columns · ready to download
Solutions
Build the workflow around the feedback.
See what they advertise
Pair a competitor’s catalogue with the ads they are running to see which products they are actually pushing.
Explore →Read the reception
On-store reviews come from the merchant’s own app. Trustpilot shows what buyers say off the store, in the same JSON shape.
Explore →Find the demand
Search public discussions for the products, price objections, and gaps a catalogue should answer.
Explore →From raw feedback to action
One request is the start of the workflow.
Store the structured response, run it on a schedule, pass it to an LLM, or feed it into the system your team already uses. FetchLayer handles retrieval so you can focus on the outcome.
- 01
Qualify the domain
Run /detect-store over the domains you care about. Keep the confirmed hits, note the permanent myshopify domain, and see which data each store publishes.
- 02
Walk the catalogue
Pull products page by page with a cursor, drop into /product-detail for stock, and read collections to see how the merchant groups what they sell.
- 03
Turn stores into intelligence
Diff prices week over week, build a sourcing shortlist, watch for new SKUs and restocks, or hand the JSON to an agent to write the category review.
One command.
Your agent does the rest.
Use the Shopify endpoint directly from your MCP-compatible agent. Ask it to retrieve public feedback, identify patterns, and turn the result into a useful brief without writing integration glue.
1 Run one command, then sign in
$ npx fetchlayer
◇ Agents
│ Claude Code and Codex
◇ Signed in as you@company.com
◇ Connected
│ ✓ Claude Code ✓ Codex
It opens a sign-in page in your browser. New here? Signing in creates your free account.
2 Ask
›Check whether these twelve domains are Shopify stores, then pull the full catalogue and current prices for every one that is.
fetchlayer.shopify_detect_store
Confirmed nine of twelve are Shopify — two are headless and read at their myshopify domains. Walked all nine catalogues: 3,180 products, 11,942 variants with prices and SKUs, and 214 items currently discounted.
No key to copy and nothing to install. New accounts are free, with no credit card.
Use cases
What teams build with Shopify store data.
Same API, endless applications. Here is what teams ship with public storefront data.
Competitor catalogue intelligence
Read any Shopify storefront’s catalogue — every product, variant, price, SKU and collection — from just its domain.
AI agent context
Give Claude, Codex, or your MCP agent structured products, variants and prices instead of a per-store scraper.
Price & stock monitoring
Poll a store on a schedule to catch price changes, sale cycles, restocks and stock-outs as they happen.
Assortment research
Compare how rival merchants group, describe and tag their catalogues to find the gaps in your own range.
Catalogue exports
Turn a whole storefront into a clean CSV of products, variants, prices and images for sourcing or resale.
Market research
Detect which domains in a category run Shopify, then read a hundred of them to size the market properly.
Compare approaches
Spend time on the insight, not the collection layer.
| What you need | FetchLayer | Official API | Build it yourself |
|---|---|---|---|
| Read a store you do not own | ✓ | Merchant must install your app | You build it |
| Works on themed & headless stores | ✓ | n/a | You detect it |
| Variant prices, SKUs & stock | ✓ | With granted scopes | You parse it |
| One key for every storefront | ✓ | Token per store | You manage it |
| Ready for AI and MCP workflows | ✓ | Your integration | Your integration |
FetchLayer provides access to publicly available data. It is not affiliated with, endorsed by, or sponsored by the platform.
Start free. Scale when ready.
Try it free, buy credits as you go, or take a monthly plan when your volume is steady.
Free
30 requests- Every platform and endpoint
- REST and MCP
- No credit card
You pay
$0
- 30 req × $0
- $0
- credit card
- none
Pay as you go
never expire- No monthly commitment
- Same access as subscribers
- ∞ req/min, ∞ API keys
You pay
$1.99per 1,000
- 1,000 req × $1.99/1k
- $1.99
- monthly fee
- $0
- expires
- never
Monthly plan
Starter15,000
- ∞ req/min, ∞ API keys
You pay
$25per month
- 15,000 req × $1.67/1k
- $25/mo
- on credits × $1.99/1k
- $29.85
- you save
- $4.85/mo
- One page fetched costs one credit.
- A request that returns no usable data costs 0 credits.
Not sure which volume fits?
15 minutes with the founder. Tell us the workload, we tell you what it needs.
Guaranteed throughput on the platform you run on
A dedicated platform from $400/mo, plus $500 for each ~21 req/s. Every other platform on the same key. 99.95% uptime, 24-hour support on Slack or Telegram.
API reference
Every parameter, documented.
All requests are POST with a JSON body and Bearer auth header.
POST /shopify-stores/detect-store 3 params
Confirm a domain is a Shopify store and find the real store behind it — with the signals behind the verdict, the permanent myshopify domain, and which data surfaces that store leaves published. A non-Shopify domain is a normal 200, so this is safe to run down a list.
store* string format string timeoutMs number POST /shopify-stores/store-profile 2 params
What a store publishes about itself: name, description, currency and money format, locale, country, city and province, the countries it ships to, the card brands it accepts, product and collection totals, the theme in use, the logo, and every social profile it links to.
store* string format string POST /shopify-stores/products 4 params
The full product catalogue: every product with its description, tags, images, and option matrix, and every variant with price, compare-at price, SKU, barcode, options, weight, and availability. Walk several pages in one request, or resume from a cursor.
store* string limit number pages number cursor string POST /shopify-stores/product-detail 2 params
One product in full, from its URL or its handle: the complete description, every image with dimensions and alt text, and every variant with price, SKU, barcode, and stock. The only endpoint that returns per-variant inventory.
product* string store string POST /shopify-stores/collections 5 params
How the store organises its catalogue, or one of those groups read in full. Without a collection, returns every collection with its title, description, image, and product count; with one, returns that collection's products in the same shape as /products.
store* string collection string limit number pages number cursor string POST /shopify-stores/review-providers 1 param
Find which review app a store uses — Judge.me, Yotpo, Loox, Okendo, Stamped or REVIEWS.io — and whether it serves store-wide reviews, product reviews or both.
store* string POST /shopify-stores/product-reviews 6 params
One product's reviews from the store's review app: average rating, review count and star distribution, then each review with its rating, text, author, verified-buyer flag, photos, the merchant's reply and helpful votes. Filter by stars, sort, and page with a cursor.
store* string product* string sort string rating number limit number cursor string POST /shopify-stores/store-reviews 4 params
Reviews across the whole store, with the store-wide rating summary, each carrying the product it was left on. Same review shape as /product-reviews.
store* string sort string limit number cursor string POST /shopify-stores/media 2 params
Stream a product image file through the API, using a url taken from any image on a product. Only store image hosts are accepted, and HTTP Range requests are supported. A GET with query parameters rather than a JSON body.
url* string filename string POST /shopify-stores/resolve-url 1 param
Parse any store URL into the fields the other endpoints take — product, collection, or store, plus the domain, the canonical store URL, the handle, the selected variant, and the permanent myshopify domain. Touches no store, and never consumes a credit.
url* string All 10 endpoints, each with its own reference page
- POST
/detect-storeCheck whether a domain is Shopify - POST
/store-profileGet a store's profile - POST
/productsList a store's products - POST
/product-detailGet one product in full - POST
/collectionsList collections, or one collection's products - POST
/review-providersFind the review service a store uses - POST
/product-reviewsGet a product's reviews - POST
/store-reviewsGet a store's reviews - GET
/mediaDownload a product image - POST
/resolve-urlParse a store URL
Fields marked * are required. Full API reference →
Guides
Shopify guides from our blog.
FAQ
Common questions.
Which stores can I read — only my own?
Any of them. That is the whole point of this API: you supply the domain, and every endpoint takes it as an argument. There is no OAuth handshake with the merchant, no app to install on their store, and no per-store access token. One FetchLayer key reads your competitor’s catalogue, a supplier’s, and a thousand domains you are qualifying in bulk. FetchLayer is not affiliated with, endorsed by, or sponsored by Shopify.
How do I know a domain is even a Shopify store?
Send it to /detect-store. It returns isShopify with a confidence of confirmed, likely, or no, the individual signals behind that verdict, the store name and currency, the permanent myshopify domain, and which of products, collections, and store metadata that particular store leaves published. A domain that is not Shopify comes back as a normal 200 with isShopify false — not an error — so you can run it down a list of a thousand domains and keep the hits.
Does it work on stores that do not look like Shopify?
Usually, yes. Every classic storefront answers the same set of endpoints no matter how heavily it has been themed or which custom domain it sits on, and a headless store — a custom front end with Shopify behind it — is read at the myshopify domain its own markup gives away. /detect-store returns that permanent domain, and you pass it back as the store.
What do I actually get for each product?
Title, handle, vendor, product type, tags, the description in plain text and as HTML, publish and update timestamps, every image with its dimensions and alt text, the full option matrix, and every variant with price, compare-at price, SKU, barcode, option values, weight, taxability, and availability — plus the product’s price range, currency, and whether anything on it is discounted. A product with more than 250 variants comes back flagged rather than silently shortened.
Can I see stock levels?
For stores that track inventory and publish it, yes — inventoryQuantity comes back per variant on /product-detail. A catalogue walk returns availability but not units on hand, which is deliberate: stock is the one field worth a request of its own, and pulling it product by product is what makes a stock-out or restock detectable over time.
Are product reviews included?
Yes, from the store’s review app. Shopify has no reviews of its own, so a store adds them through an app, and FetchLayer reads the six most common: Judge.me, Yotpo, Loox, Okendo, Stamped and REVIEWS.io. /review-providers tells you which one a store uses, /product-reviews returns one product’s reviews with its average rating and star distribution, and /store-reviews returns reviews across the whole store. Every service comes back in the same shape — rating, title, text, author, verified-buyer flag, date, photos, the merchant’s reply and helpful votes — and a field a service does not publish is null rather than missing. A store on a review app outside those six returns a 404.
Why does every response carry a notes array?
Because a partial answer should say so. notes is where a walk that stopped early, an upstream limit, or a field this particular store does not publish gets reported. An empty notes means the result is as complete as the store publishes; entries in it tell you exactly what is missing and why. Read it before treating a catalogue as final.
Can I download the product images?
Yes. Every image on a product carries a downloadUrl, and GET /shopify-stores/media streams the actual bytes through FetchLayer with HTTP Range support. Only store image hosts are accepted, and the request carries your Bearer key in a header — so an image URL cannot be shared without also sharing the key.
How does billing work?
One API request equals one credit, the same as every other FetchLayer platform. Each page walked counts as one request, so pages: 10 bills as ten. Each page of reviews a review request returns counts as one request too; the lookups behind a rating breakdown are free. Parsing a URL with /resolve-url touches no store and is free. Streaming an image bills as a normal request.
Start pulling Shopify store data today.
Get a free API key, make your first request, and put public feedback to work in your own product or research workflow.
Used by developers at
Individual developers or teams — not official partnerships