BigCommerce API Documentation

First request

Endpoint

GET /bigcommerce/search

Cost

3 credits/request

curl "https://api.crawlora.net/api/v1/bigcommerce/search?page=1&q=lavender&url=https%3A%2F%2Fwww.bulkapothecary.com" \
  -H "x-api-key: $CRAWLORA_API_KEY"

How to use BigCommerce endpoints

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.

1. Step 1

   Point it at a storefront 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.

2. Step 2

   Search a storefront

   /bigcommerce/search takes the storefront url plus a required q query and an optional page, returning normalized product-search cards.

3. Step 3

   Browse a category

   /bigcommerce/category takes a full category-page URL copied from the storefront plus an optional page, returning the same normalized product cards with pagination.

4. Step 4

   Get product detail

   Pass a full public product-page URL to /bigcommerce/product for normalized identity, pricing, availability, brand, description and images.

5. Step 5

   Handle stores that are not eligible

   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.

Other Marketplaces & Retail APIs