Storefront catalog monitoring
Mit BigCommerce-Endpunkten verwandelst du storefront catalog monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn any public BigCommerce Stencil storefront into structured JSON — full-catalog search, paginated category product grids, and per-product detail with pricing, availability, brand, description, and images, from just the storefront URL.
Search a BigCommerce Stencil storefront, browse category product grids, and get full public product detail as structured JSON.
Endpunkt-Familien
3
Dokumentierte Parameter
9
Beispiele
3
Live-Katalog-Snapshot
Aktive Endpunkte
3
Methoden
GET
Pflichtparameter
7
Schema-Referenzen
3
{
"platform": "BigCommerce",
"endpoint": "bigcommerce-search",
"method": "GET",
"path": "/bigcommerce/search",
"auth": "apiKey"
}Use Cases
Search a BigCommerce Stencil storefront, browse category product grids, and get full public product detail as structured JSON.
Mit BigCommerce-Endpunkten verwandelst du storefront catalog monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit BigCommerce-Endpunkten verwandelst du category and search research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit BigCommerce-Endpunkten verwandelst du price and availability tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-BigCommerce-Endpunktkatalog — 3 Endpunkte, 9 dokumentierte Request-Parameter und 3 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
3 documented BigCommerce endpoints, grouped into 3 request families — Category, Product and Search.
9 request parameters are documented across those BigCommerce endpoints, 7 of them required — the full input contract is public before you write any integration code.
3 of the 3 BigCommerce endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
BigCommerce endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the BigCommerce endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/bigcommerce/category
/bigcommerce/product
/bigcommerce/search
Endpunktkatalog
/bigcommerce/searchReturns one product-search page from a public BigCommerce storefront. url must be the public storefront origin; an optional caller path or query is ignored. q is required search text. page is 1-indexed and defaults to 1.
MCP-Tool bigcommerce_search
/bigcommerce/categoryReturns one product-listing page from a public BigCommerce storefront category page. url must be the full public category-page URL. page is 1-indexed and defaults to 1.
MCP-Tool bigcommerce_category
/bigcommerce/productReturns product detail from a public BigCommerce storefront product page. url must be the full public product-page URL for a BigCommerce Stencil storefront.
MCP-Tool bigcommerce_product
Verwandte APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
So scrapst du BigCommerce
Crawlora's BigCommerce endpoints return normalized public storefront data as JSON with one API key — no account or storefront credentials required, just the storefront's own public URL.
Every BigCommerce endpoint is URL-driven rather than store-specific: url is required on all three, so the same API key works against any public Stencil storefront without per-store configuration. That is what makes this platform different from the single-retailer APIs elsewhere in the catalog.
/bigcommerce/search takes the storefront url plus a required q query and an optional page, returning normalized product-search cards.
/bigcommerce/category takes a full category-page URL copied from the storefront plus an optional page, returning the same normalized product cards with pagination.
Pass a full public product-page URL to /bigcommerce/product for normalized identity, pricing, availability, brand, description and images.
Coverage depends on the storefront exposing public Stencil HTML. A store that is password-protected, headless, or on a non-Stencil theme returns an upstream error rather than partial data — worth probing one product URL before pointing a pipeline at a new store.
FAQ
Call /bigcommerce/search or /bigcommerce/category for a paginated product grid, or /bigcommerce/product with a product URL for full detail — all return structured JSON from any public BigCommerce Stencil storefront, no account needed.
It works on public BigCommerce Stencil storefronts. Storefronts without public Stencil HTML, or that are password-protected, return an upstream error.
Yes — /bigcommerce/product returns current pricing and availability; re-run it on a schedule to track changes over time.
No. All three endpoints take the storefront URL as a required parameter, so one API key covers every public Stencil storefront you point it at — there is no per-store setup, key or allowlist. Discover product URLs with the search or category endpoint, then resolve them with the product endpoint.
Any storefront that does not serve public Stencil HTML — password-protected stores, headless builds that render through a separate frontend, and non-Stencil themes. Those return an upstream error rather than partial or guessed data, so probe a single product URL before committing a pipeline to a new store.