Öffentliche Shopify-Store-JSON- und Sitemap-Schnittstellen in strukturierte Daten für Katalogmonitoring, Sortimentsforschung, Produktentdeckung und Store-Intelligence-Workflows verwandeln.
Strukturierter Output
Mit Crawloras Shopify-Store-Scraping-API im unterstützten Umfang öffentliches Store-JSON, Produkte, Kollektionen, Seiten, Empfehlungen, Predictive Search und Sitemap-Einträge sammeln, ohne Shopify-spezifische Request-Verarbeitung, URL-Normalisierung, Parser, Abrechnung oder Entwicklerdokumentation selbst zu pflegen.
E-Commerce-Workflow
Shopify-Store-Daten unterstützen öffentliche Katalogentdeckung, Produktmonitoring, Kollektionsforschung, Suchvorschlagsanalyse, Seitenentdeckung und Sitemap-Audits für Teams, die reproduzierbare strukturierte Datensätze statt manuellem Store-Browsing brauchen.
Shopify-Store-IntelligenceRequest-Schema
Diese Parameter stammen aus dem aktiven Get Shopify store metadata-Katalogeintrag.
| Parameter | Typ | Erforderlich | Beschreibung | Beispiel |
|---|---|---|---|---|
| url | string | Ja | Shopify storefront URL | https://www.allbirds.com |
Beispiel-JSON
Dieses Beispiel wird aus dem aktiven Endpunktkatalog gerendert, damit die Seite mit Docs und Playground synchron bleibt.
{
"code": 200,
"msg": "OK",
"data": {
"requested_url": "https://www.allbirds.com",
"source_url": "https://www.allbirds.com",
"domain": "www.allbirds.com",
"source_domain": "www.allbirds.com",
"name": "Allbirds",
"currency": "USD",
"country": "US",
"published_products_count": 638
}
}Endpunktkatalog
/shopify/storeResolves a public Shopify storefront and returns its metadata.
Hinweise zur Response
- Returns the requested storefront URL plus the resolved source URL used for JSON requests. - Includes `myshopify_domain`, store name, currency, country, and published product/collection counts when `/meta.json` exposes them. - Blocked pages, malformed JSON, missing Shopify roots, and unavailable fallback domains return upstream errors. - For some storefronts, `transport_mode` is `ssr_embedded`; it is omitted entirely for other stores. Responses for these stores may have fewer populated fields (for example `myshopify_domain` and the store-metadata fields are typically unavailable). `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP-Tool shopify_store
/shopify/productsReturns products from a public Shopify storefront. Valid empty result pages return `200` with an empty products array. `sortBy` and dynamic facet-filter query params (e.g. `fit`, `canonicalColour`) only take effect for headless storefronts (`transport_mode: "ssr_embedded"`) and return an invalid-param error if supplied against a classic store, since classic Shopify storefronts have no server-side sort or filter support. `sort_by`, `min_price`, `max_price`, `product_type`, `in_stock_only`, and `option_`-prefixed params (e.g. `option_size=Small,Medium`) drive a separate, independent mechanism -- Shopify's own native Storefront Filtering collection-page feature (`transport_mode: "storefront_filtered"`) -- which works for both classic and headless stores; supplying any of these takes precedence over sortBy/dynamic facet filters.
Hinweise zur Response
- Valid empty result pages return `200` with an empty `products` array. - Product prices are normalized to decimal currency units. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - For some storefronts, the response includes `transport_mode: "ssr_embedded"`, `total_items`, and `total_pages` (the storefront's own result-count/page-count metadata), and each product may include additive fields only available from this source: `colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, and per-variant `inventory_quantity`. `limit` is still honored as an upper bound on returned items, but the underlying page size is fixed by the storefront (commonly 60) and cannot be requested larger than that. `transport_mode`, `total_items`, and `total_pages` are omitted entirely for other stores. - When `transport_mode` is `ssr_embedded`, the response may also include `facets` and `facets_stats`, mirroring the storefront's own filter sidebar for that listing: `facets` maps a facet field name exactly as the storefront names it (for example `fit`, `activities`, `canonicalColour`, `sizeInStock`) to its value-to-count buckets, and `facets_stats` gives `min`/`max`/`avg` for numeric-range fields such as `price` and `discountPercentage`. Both are omitted when the storefront's payload did not include facet data, and always omitted for other stores. - **`sortBy` and facet filters apply to `ssr_embedded` stores only.** Rather than silently accepting and ignoring `sortBy` or a facet filter against other stores (which would look like it worked but wouldn't), this endpoint rejects the request with a `400` invalid-param error whenever `sortBy` or any facet-filter query param is supplied and the resolved store is not `transport_mode: "ssr_embedded"`. - When a sort and/or filters were applied to an `ssr_embedded` store, the response echoes back what was actually honored: `sort` (one of the enum values below) and `filters` (a map of facet field name to the array of values that were requested for it, after comma-splitting). Both are omitted when no sort/filter was supplied. - `hitsPerPage` (the storefront's own listing page size, commonly 60) is unaffected by sort/filters; `limit` continues to apply as an upper bound on the returned page. - **Storefront Filtering** (`sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`option_*`) is Shopify's own native collection-page filtering/sorting feature, distinct from the `sortBy`/dynamic-facet-filter pair above. It works for all stores. When any of these params is supplied, the response has `transport_mode: "storefront_filtered"` and echoes back the effective `sort_by`, `min_price`, `max_price`, `product_type`, `in_stock_only`, and `variant_options` that were applied. `facets`/`facets_stats` are populated from the storefront's own filter sidebar when present: `facets` maps a lowercased variant option name (e.g. `size`, `color`) or `product_type` to its value-to-count buckets, and `facets_stats.price` gives the Price slider's own `min`/`max` bounds. `total_pages` is populated only when the collection page itself renders numbered pagination links; a single-page result leaves it unset. Not every Shopify store has this feature enabled — a store without it returns the unfiltered/unsorted collection page, which this endpoint cannot distinguish from "the filter matched everything" without upstream signal. `sortBy` allowed values: `sortLTH`, `sortHTL`, `newest`. `sort_by` allowed values: `manual`, `best-selling`, `title-ascending`, `title-descending`, `price-ascending`, `price-descending`, `created-ascending`, `created-descending`. `transport_mode` allowed values: `ssr_embedded`, `storefront_filtered` (omitted entirely for the classic transport).
MCP-Tool shopify_products
/shopify/products/{handle}Returns one product from any Shopify storefront, given the store URL and the product handle: title, description, product type, tags, price and compare-at price, availability, options, images, and each variant with its own price, availability and barcode. Prices are in decimal currency units; an unknown handle returns `404`.
Hinweise zur Response
- Product prices are returned in decimal currency units rather than cent values. - Missing product handles return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing product fields return upstream errors. - For some storefronts, the response includes `transport_mode: "ssr_embedded"`, and the product may include additive fields only available from this source: `colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, and per-variant `inventory_quantity`. `transport_mode` is omitted entirely for other stores. A product for which no detail data is available returns an upstream error. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP-Tool shopify_product
/shopify/products/{handle}/recommendationsReturns recommended products from Shopify's product recommendations.
Hinweise zur Response
- Missing product handles return `404` when Shopify returns not found while resolving the seed product. - Valid empty recommendation arrays return `200` with an empty `products` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - For some storefronts, the response includes `transport_mode: "ssr_embedded"`, and each product may include the same additive fields documented for `/shopify/products`: `colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, and per-variant `inventory_quantity`. `transport_mode` is omitted entirely for other stores. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP-Tool shopify_product_recommendations
/shopify/collectionsReturns collections from a public Shopify storefront. Valid empty result pages return `200` with an empty collections array.
Hinweise zur Response
- Valid empty result pages return `200` with an empty `collections` array. - Blocked pages, malformed JSON, and missing `collections` roots return upstream errors. - For some storefronts, the response includes `transport_mode: "ssr_embedded"`, and `title` is a best-effort derivation from the handle (hyphens become spaces, each word title-cased) — **not** the storefront's real display name. `products_count` and other fields not available for these storefronts are omitted, never fabricated. `transport_mode` is omitted entirely for other stores. - In this fallback mode, `handle` is derived from the last path segment of the collection URL and is not guaranteed unique: some storefronts nest gender/audience-scoped sub-collections under the same final segment (for example `/collections/all-products/womens` and `/collections/legacy/womens` both derive `handle: "womens"`). Use the item's own `url` to identify a specific nested collection rather than assuming `handle` alone round-trips through `GET /shopify/collections/{handle}/products`. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP-Tool shopify_collections
/shopify/collections/{handle}/productsReturns products from a Shopify collection. `sortBy` and dynamic facet-filter query params (e.g. `fit`, `canonicalColour`) only take effect for headless storefronts (`transport_mode: "ssr_embedded"`) and return an invalid-param error if supplied against a classic store, since classic Shopify storefronts have no server-side sort or filter support. `sort_by`, `min_price`, `max_price`, `product_type`, `in_stock_only`, and `option_`-prefixed params (e.g. `option_size=Small,Medium`) drive a separate, independent mechanism -- Shopify's own native Storefront Filtering collection-page feature (`transport_mode: "storefront_filtered"`) -- which works for both classic and headless stores; supplying any of these takes precedence over sortBy/dynamic facet filters.
Hinweise zur Response
- Valid empty result pages return `200` with an empty `products` array. - Missing collections return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - For some storefronts, the response includes `transport_mode: "ssr_embedded"`, `total_items`, and `total_pages` (the storefront's own result-count/page-count metadata), and each product may include additive fields only available from this source: `colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, and per-variant `inventory_quantity`. `limit` is still honored as an upper bound on returned items, but the underlying page size is fixed by the storefront (commonly 60) and cannot be requested larger than that. `transport_mode`, `total_items`, and `total_pages` are omitted entirely for other stores. - When `transport_mode` is `ssr_embedded`, the response may also include `facets` and `facets_stats`, mirroring the collection page's own filter sidebar: `facets` maps a facet field name exactly as the storefront names it (for example `fit`, `activities`, `canonicalColour`, `sizeInStock`) to its value-to-count buckets, and `facets_stats` gives `min`/`max`/`avg` for numeric-range fields such as `price` and `discountPercentage`. Both are omitted when the storefront's payload did not include facet data, and always omitted for other stores. - **`sortBy` and facet filters apply to `ssr_embedded` stores only.** Rather than silently accepting and ignoring `sortBy` or a facet filter against other stores (which would look like it worked but wouldn't), this endpoint rejects the request with a `400` invalid-param error whenever `sortBy` or any facet-filter query param is supplied and the resolved store is not `transport_mode: "ssr_embedded"`. - When a sort and/or filters were applied to an `ssr_embedded` store, the response echoes back what was actually honored: `sort` (one of the enum values below) and `filters` (a map of facet field name to the array of values that were requested for it, after comma-splitting). Both are omitted when no sort/filter was supplied. - `hitsPerPage` (the storefront's own listing page size, commonly 60) is unaffected by sort/filters; `limit` continues to apply as an upper bound on the returned page. - **Storefront Filtering** (`sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`option_*`) is Shopify's own native collection-page filtering/sorting feature, distinct from the `sortBy`/dynamic-facet-filter pair above. It works for all stores. When any of these params is supplied, the response has `transport_mode: "storefront_filtered"` and echoes back the effective `sort_by`, `min_price`, `max_price`, `product_type`, `in_stock_only`, and `variant_options` that were applied. `facets`/`facets_stats` are populated from the collection page's own filter sidebar when present: `facets` maps a lowercased variant option name (e.g. `size`, `color`) or `product_type` to its value-to-count buckets, and `facets_stats.price` gives the Price slider's own `min`/`max` bounds. `total_pages` is populated only when the collection page itself renders numbered pagination links; a single-page result leaves it unset. Not every Shopify store has this feature enabled — a store without it returns the unfiltered/unsorted collection page, which this endpoint cannot distinguish from "the filter matched everything" without upstream signal. `sortBy` allowed values: `sortLTH`, `sortHTL`, `newest`. `sort_by` allowed values: `manual`, `best-selling`, `title-ascending`, `title-descending`, `price-ascending`, `price-descending`, `created-ascending`, `created-descending`. `transport_mode` allowed values: `ssr_embedded`, `storefront_filtered` (omitted entirely for the classic transport).
MCP-Tool shopify_collection_products
/shopify/search/suggestReturns predictive search suggestions from any Shopify storefront for a query: matching products, collections and suggested queries. Choose which with `types` (default all three) and cap results per type with `limit` (default 10, max 20). Products carry price, availability, images and options; collections carry title, handle, description and product count.
Hinweise zur Response
- Products and collections use the same shapes as the Shopify product and collection endpoints. - Query suggestions include text and a storefront search URL when Shopify provides one. - Valid empty suggestion arrays return `200` with empty arrays. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors.
MCP-Tool shopify_search_suggest
/shopify/pagesLists static pages from a Shopify storefront given by the required `url`, paged with `page` (from 1) and `limit` (default 50, max 250). Each has `handle`, `title`, `url`, plain-text `content` and dates. If `transport_mode` is `ssr_embedded`, items hold only `handle`, `url` and `updated_at`.
Hinweise zur Response
- Page content is cleaned text from Shopify `body_html`; raw HTML is not returned. - Valid empty page arrays return `200` with an empty `pages` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - For some storefronts, the response includes `transport_mode: "ssr_embedded"`, and each item only carries `handle`, `url`, and `updated_at` — no `title`, `id`, or `content`. Call `GET /shopify/pages/{handle}` per handle to get full content. `transport_mode` is omitted entirely for other stores. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP-Tool shopify_pages
/shopify/pages/{handle}Returns one static page from any public Shopify storefront, by path `handle` and the required `url` of the store. The response has the page's title, URL, times and its `content` as plain text. Unknown handles return 404. Localhost, private-network and credentialed URLs are rejected.
Hinweise zur Response
- Page content is cleaned text from Shopify `body_html`; raw HTML is not returned. - Missing page handles return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - For some storefronts, the response includes `transport_mode: "ssr_embedded"`; `content` is plain text rendered from the page's rich-text blocks (marks/formatting are dropped, non-rich-text blocks such as banners are skipped), and `id` is omitted because it is not a Shopify numeric id. `transport_mode` is omitted entirely for other stores. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP-Tool shopify_page
/shopify/sitemapsLists the child sitemaps in a Shopify storefront's sitemap index, for the required `url`. Each has a `loc` and a `type` (`products`, `collections`, `pages`, `blogs`, `agentic_discovery` or `other`) inferred from its URL. Localhost, private-network and credentialed URLs are rejected.
Hinweise zur Response
- Sitemap `type` is inferred from the child sitemap URL. - Inferred sitemap types are `products`, `collections`, `pages`, `blogs`, `agentic_discovery`, and `other`. - Blocked pages, malformed XML, and missing sitemap entries return upstream errors.
MCP-Tool shopify_sitemaps
/shopify/sitemap/urlsLists URL entries from a Shopify storefront's sitemaps, for the required `url`. `type` filters (`all` by default, `products`, `collections`, `pages`, `blogs`, `agentic_discovery`, `other`) and `limit` caps entries (default 50, max 250). Each has `loc`, `type`, `handle`, `lastmod`, `changefreq` and optional `images`.
Hinweise zur Response
- The service fetches matching child sitemaps from `/sitemap.xml` until `limit` URL entries is reached. - URL entries include `loc`, inferred `type`, `handle`, `lastmod`, `changefreq`, and optional `images`. - Blocked pages, malformed XML, and missing sitemap entries return upstream errors.
MCP-Tool shopify_sitemap_urls
Managed Execution
Crawlora kapselt unterstützte öffentliche Shopify-Store-JSON- und Sitemap-Abläufe als API-Key-geschützte Endpunkte mit normalisierten Antworten, dokumentierten Fehlern, Playground-Beispielen und Credit-basierter Nutzungsabrechnung.
Endpunkt-spezifische Request-Verarbeitung für Store-, Produkt-, Kollektions-, Seiten-, Empfehlungs-, Suchvorschlags- und Sitemap-Abläufe
URL-Validierung, die localhost, private Netzwerke, link-local und URLs mit Credentials ablehnt
Normalisierte Produkt-, Kollektions-, Seiten-, Empfehlungs- und Sitemap-Felder im verfügbaren Umfang
Quell-URL-Auflösung für Stores, die öffentliche Daten über eine entdeckte myshopify.com-Domain bereitstellen
Dokumentiertes Verhalten bei Upstream-Ausfällen wie Blockierung, Fehlformat, Nicht-gefunden oder fehlendem Root-Pfad
Docs- und Playground-Seiten werden aus dem aktuell aktiven Endpunktkatalog generiert
Selbst bauen oder kaufen
Nutze diesen Vergleich, um zu entscheiden, ob du Scraping-Infrastruktur intern pflegst oder einen Managed-Endpunkt aufrufst.
| Anforderung | Eigenbau | Crawlora |
|---|---|---|
| Endpunktabdeckung | Eigene Crawler für Store-Metadaten, Produkte, Kollektionen, Seiten, Empfehlungen und Suchvorschläge pflegen. | Dokumentierte Shopify-Store-Endpunktfamilie über eine Crawlora-API-Oberfläche nutzen. |
| URL- und Quellbehandlung | Nicht vertrauenswürdige Store-URLs selbst validieren und Fallback-Logik für öffentliche Quelldomains selbst implementieren. | Crawloras Validierung und endpunkt-spezifische Quell-URL-Behandlung nutzen. |
| Schema-Normalisierung | Produkt-, Kollektions-, Seiten- und Empfehlungsmodelle selbst entwerfen. | Normalisierte JSON-Beispiele und -Schema in Docs und Playground erhalten. |
| Nutzungsabrechnung | Eigenes Metering- und pro-Ablauf-Preismodell bauen. | Credit-basierte Endpunkt-Gewichtung und API-Key-Nutzungstracking verwenden. |
Crawlora ist nicht Shopifys offizielle Admin API, Storefront API, Checkout API oder Partner API. Crawlora bietet strukturierte Web-Extraktion öffentlicher Daten für unterstützte öffentliche Shopify-Store-Seiten, -JSON und -Sitemap-Abläufe. Wenn dein Use Case konto-gebundene Commerce-Daten, Bestellungen, Checkout, Kundendatensätze, Bestandsverwaltung, Händlerverwaltung oder offizielle App-Integrationen benötigt, nutze Shopifys offizielle API. Kund:innen müssen selbst sicherstellen, dass ihre Nutzung geltendem Recht, Rechten Dritter, Plattformbedingungen, Händlerbedingungen und den Crawlora-Bedingungen entspricht.
Verwandte APIs
Verbinde diesen Endpunkt mit angrenzenden Crawlora-Seiten für Suche, Monitoring, Docs und Preise.
Öffentliche Shop.app-Produkt-, Store-, Review-, Kategorie-, Vorschlags- und Variantendaten-Workflows recherchieren.
ÖffnenAmazon-Produkt- und Suchergebnismonitoring in E-Commerce-Marktplatz-Workflows einbinden.
ÖffneneBay-Produkt-, Such- und Verkäuferdaten für Resale- und Marktplatzforschung sammeln.
ÖffnenÖffentliche Shopify-Katalog-, Seiten-, Suchvorschlags- und Sitemap-Workflows planen.
ÖffnenShopify-Store-Daten mit breiteren E-Commerce-Produkt-Intelligence-Workflows kombinieren.
ÖffnenCredit-basierte Nutzung für Shopify und weitere Marktplatz-Endpunkte ansehen.
ÖffnenSo scrapst du Shopify
Crawloras Shopify-Endpunkte sind GET-Requests, die die url eines beliebigen öffentlichen Stores akzeptieren und Shopifys credential-freie öffentliche Schnittstellen auslesen: /shopify/store löst den Store auf und liefert Metadaten, /shopify/products und /shopify/collections lesen die öffentlichen products.json- und collections.json-Schnittstellen (mit page und limit), /shopify/collections/{handle}/products iteriert über eine Kollektion, /shopify/products/{handle} liefert Produktdetails über den .js-Endpunkt des Handles, /shopify/products/{handle}/recommendations liest die Empfehlungs-Ajax-Schnittstelle (intent related oder complementary), /shopify/search/suggest liest die Predictive Search, /shopify/pages und /shopify/pages/{handle} lesen statische Seiten als bereinigten Text, /shopify/sitemaps und /shopify/sitemap/urls iterieren über den Sitemap-Index. Bei Headless-Stores ohne klassische Schnittstelle greift ein Fallback auf die im Store selbst eingebetteten Suchdaten zurück, der zusätzlich facets-, sortBy- und Facettenfilter-Parameter liefert.
GET /shopify/store?url=<Store-URL> liefert normalisierte Store-Metadaten aus dem credential-freien Store-JSON. Blockiert eine Custom-Domain products.json, kann der Dienst auf die öffentliche myshopify.com-Domain des Stores zurückfallen.
GET /shopify/products?url=<store>&page=1&limit=<n> liefert den öffentlichen Produkt-Feed, /shopify/collections die Kollektionsliste, /shopify/collections/{handle}/products die Produkte einer Kollektion. Eine leere Seite liefert Status 200 mit leerem Array — so erkennst du das Ende.
GET /shopify/products/{handle}?url=<store> liefert vollständige Produktdetails, GET /shopify/products/{handle}/recommendations (intent=related oder complementary) liefert verwandte Empfehlungen des Stores; der handle wird automatisch zur Shopify-Produkt-id aufgelöst.
GET /shopify/sitemaps?url=<store> listet Sub-Sitemaps mit abgeleitetem Typ, /shopify/sitemap/urls?type=products iteriert deren Einträge, /shopify/search/suggest?q=<term> liest Predictive Search, /shopify/pages sowie /shopify/pages/{handle} liefern statische Seiten als bereinigten Text.
For allbirds.com on 2026-10-30 collections, the mens collection's products and pages each returned exactly 40 rows at limit=40, so page 1 is a full page for all three. Rows carry handle, url and timestamps, and the store_url you pass is echoed back.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Shopify-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Shopify ab:
Compare competing retail assortments through Crawlora catalogs. Use to find observed gaps in categories, brands, product attributes, variants, and…
npx skills add github.com/Crawlora-org/crawlora-skills --skill retail-assortment-gap-analysisResearches independent Shopify-powered storefronts — products, collections, pages, sitemaps, search suggestions, and product recommendations — using…
npx skills add github.com/Crawlora-org/crawlora-skills --skill shopify-researchResearch products, prices, sellers, and reviews across major online marketplaces and retailers, including African Jumia storefronts. Use when the…
npx skills add github.com/Crawlora-org/crawlora-skills --skill product-price-researchFAQ
Antworten für Entwickler, die Crawlora für unterstützte öffentliche Suchergebnisseiten evaluieren.
Ja. Crawlora bietet Shopify-Endpunkte für unterstützte öffentliche Store-Metadaten, Produkte, Produktdetails, Empfehlungen, Kollektionen, Kollektionsprodukte, Seiten, Predictive-Search-Vorschläge, Sitemaps und Sitemap-URLs.
Nein. Crawlora ist nicht Shopifys offizielle Admin API, Storefront API, Checkout API, Partner API und auch keine Händler-App-Integration. Sie bietet öffentliche Web-Datenextraktion für unterstützte Shopify-Store-Seiten.
Der aktuelle Katalog umfasst Store-Metadaten, öffentliche Produkte, Produktdetails, Empfehlungen, Kollektionen, Kollektionsprodukte, öffentliche Seiten, Predictive-Search-Vorschläge, Sub-Sitemaps und im unterstützten Umfang mengenbegrenzte Sitemap-URL-Einträge.
Nein. Crawloras Shopify-Endpunkte zielen ausschließlich auf öffentliche Store-Daten im unterstützten Umfang. Für konto-gebundene Commerce-, Bestell-, Checkout-, Kunden- oder Bestandsverwaltungs-Workflows nutze Shopifys offizielle API.
Ja. Soweit öffentliche Store-Daten verfügbar sind, unterstützen Shopifys Produkt-, Produktdetail-, Kollektions- und Kollektionsprodukt-Endpunkte verantwortungsvolles Katalogmonitoring.
Ja. Soweit verfügbar, können Shopify-Sitemap-Endpunkte Sub-Sitemap-Einträge sowie mengenbegrenzte URL-Zeilen für abgeleitete Sitemap-Typen wie Produkte, Kollektionen, Seiten, Blogs und Agent-Discoverability auflisten.
Übergib die url des Stores an Crawloras /shopify/store-Endpunkt, um ihn aufzulösen, dann rufe GET /shopify/products, /shopify/collections und /shopify/collections/{handle}/products auf, um den Katalog zu durchlaufen, und /shopify/products/{handle} für Details. Keine Shopify-Credentials nötig — diese Endpunkte lesen Shopifys öffentliches Store-JSON.
Meist ja. Blockiert eine Custom-Domain diese Schnittstelle, kann der Dienst auf die öffentliche myshopify.com-Domain zurückfallen; bei Headless-Stores ganz ohne diese Schnittstelle werden die im Store eingebetteten Suchdaten ausgelesen, was zusätzlich facets-, sortBy- und Facettenfilter-Parameter offenlegt.
Nur bei Headless-Stores, die über den eingebetteten Such-Fallback bedient werden — dort werden sortBy und Facettenfilter-Query-Parameter an den eigenen Suchindex des Stores weitergereicht. Klassische Stores mit öffentlicher products.json haben keine serverseitige Sortierung oder Filterung; dort liefert der Endpunkt /shopify/collections/{handle}/products einen typisierten 400-Fehler, statt diese Parameter still zu ignorieren.
Übergib an /shopify/products/{handle}/recommendations die Store-url sowie intent=related oder intent=complementary. Nach Auflösung des handle zur Produkt-id liest der Endpunkt Shopifys credential-freie Empfehlungs-Ajax-Schnittstelle.
Diese Endpunkte lesen Shopifys öffentlich ohne Credentials zugängliches Store-JSON und Sitemaps. Das Sammeln dieser Daten für Recherche, Monitoring und Sortimentsanalyse ist im Rahmen der Store-Bedingungen, Ratenlimits und geltenden Rechts in der Regel zulässig.
Nicht für allgemeine Entwickler. Shopifys eigene Admin API liefert nur die Daten des Stores, der das jeweilige Access-Token ausgestellt hat — sie kann nicht den Katalog eines anderen Händlers lesen. Shopifys neuere store-übergreifende Catalog API, die Produkt- und Preis-Feeds über viele Stores hinweg normalisiert, ist nur auf Einladung und wird pro Partner geprüft (Perplexity war die erste Integration) — es gibt keine Self-Service-Anmeldung. Crawloras Endpunkte lesen stattdessen direkt das öffentliche products.json, collections.json und die Suchschnittstellen jedes einzelnen Stores, sodass jeder öffentliche Shopify-Store ohne Partner-Prüfung abgefragt werden kann.
Unternehmensabdeckung
Shopify Inc. · SHOP
Shopify wird von Shopify Inc. (SHOP) betrieben. Crawloras SEC-Endpunkte nutzen dieselbe CIK dieses Unternehmens, sodass Filings, Finanzdaten, Insider-Transaktionen und 13F-Beteiligungen mit demselben API-Key wie die Shopify-Endpunkte oben abrufbar sind.
Weitere Shopify Inc.-Plattformen im Katalog
Guides
Read Crawlora guides and comparisons that use the Shopify API.
Teste Shopify-Store-Metadaten im Playground, sieh dir das aktuelle Response-Schema in den Docs an und vergleiche die Credit-basierte Nutzung auf der Preisseite.