Scrape category pages on lego.com

Measured on Crawlbase

Success rate over every request from every account in August 2026: 94.9%. Patterns, countries and failures come from the request log since 14 Aug 2026; 0.0% of successful calls used the JavaScript token and the median answer took 2.8s.

Among the 20 ecommerce sites in the Cookbook, lego.com sits at 12 of 20 by success rate; the category median is 96.3%. Its median answer of 2.8s sits at the category median of 2.9s. 9 of the 20 accept the plain token, this one among them.

The call

Category and listing pages are the shape the accounts fetch most here, with the country and token that succeed most often. Replace the placeholder path with a real section URL from the site.

curl "https://api.crawlbase.com/?token=YOUR_TOKEN&country=DE&url=https%3A%2F%2Fwww.lego.com%2Fde-de%2Fcategories%2Fexample-page"

from crawlbase import CrawlingAPI
api = CrawlingAPI({'token': 'YOUR_TOKEN'})

r = api.get('https://www.lego.com/de-de/categories/example-page', {'country': 'DE'})
html = r['body']

const { CrawlingAPI } = require('crawlbase');
const api = new CrawlingAPI({ token: 'YOUR_TOKEN' });

const r = await api.get('https://www.lego.com/de-de/categories/example-page', { country: 'DE' });

Parameters that matter

URL patterns accounts fetch

Fields you get

A listing page carries the items of one section, each with a title, a link and often a price, plus the pagination. The detail lives on the item page; fetch it only for the items you need.

What breaks, and the fix

Of the failures since 14 Aug 2026, the site answered:

Run it on a schedule

Walk the listings on a cadence to find new items, then push the item URLs to the Crawler with a callback; it paces the calls and retries what the site refuses. The median answer on this site is 2.8s.

Questions