Brickset LEGO Set Database Scraper

Scrape Brickset, the most comprehensive LEGO set database on the web. Search by keyword, browse by theme and/or release year, and get structured data for 20,000+ LEGO sets: set numbers, piece counts, minifig counts, retail prices (RRP), current aftermarket values (new & used), community ratings, and more.

What data does it extract?

For every LEGO set:

Field	Description
setNumber	Official set number (e.g. 75192-1)
name	Set name (e.g. Millennium Falcon)
theme / subtheme	Theme (e.g. Star Wars) and subtheme (e.g. Ultimate Collector Series)
year	Release year
pieces	Piece count
minifigs	Minifigure count
rrp / rrpUsd	Recommended retail price (raw + parsed USD)
pricePerPiece	Price per piece
currentValueNewUsd	Current aftermarket value, new/sealed
currentValueUsedUsd	Current aftermarket value, used
rating / ratingsCount / reviewsCount	Community rating (0-5) and counts
packaging	Box, polybag, etc.
launchExit	Launch and exit dates
ownedBy / wantedBy	How many collectors own / want the set
image / url	Set image and Brickset page URL

With Scrape Set Detail Pages enabled, each set is enriched with: designer, age range, UPC/EAN barcodes, model & packaging dimensions, multi-currency RRP (GBP/USD/EUR), unique minifig count, theme group, category, and availability (e.g. LEGO exclusive).

Input

{
    "searchQueries": ["millennium falcon"],
    "themes": ["Star Wars", "Icons"],
    "years": [2024],
    "maxItems": 100,
    "scrapeDetails": false
}

• searchQueries — keyword searches (set names, numbers, characters)
• themes — exact Brickset theme names (Star Wars, Technic, Harry Potter, City, Icons, ...)
• years — release years; combine with themes to filter both
• maxItems — cap on total results
• scrapeDetails — visit each set page for extra fields (slower)

Provide any combination — themes only, years only, keywords only, or themes + years together.

Output example

{
    "setNumber": "30680-1",
    "name": "AAT",
    "theme": "Star Wars",
    "subtheme": "Episode I",
    "year": 2024,
    "pieces": 75,
    "minifigs": null,
    "rrp": "$4.99",
    "rrpUsd": 4.99,
    "pricePerPiece": "6.7c",
    "currentValueNewUsd": 4.26,
    "currentValueUsedUsd": 1.17,
    "rating": 3.5,
    "ratingsCount": 356,
    "reviewsCount": 2,
    "packaging": "Polybag",
    "launchExit": "1 Jan 2024 - 31 Dec 2024 (11m 30d)",
    "ownedBy": 11862,
    "wantedBy": 535,
    "image": "https://images.brickset.com/sets/small/30680-1.jpg",
    "url": "https://brickset.com/sets/30680-1/AAT"
}

Use cases

• LEGO investing — compare RRP vs current new/used value to find appreciating sets
• Price tracking — monitor aftermarket values of retired sets
• Collection tools — build apps on top of structured LEGO set data
• Market research — analyze themes, piece counts, and price-per-piece trends by year
• Reselling — check current values and demand (owned/wanted counts) before buying or listing

FAQ

How is this different from a BrickLink scraper? BrickLink is a marketplace (live listings and seller prices). Brickset is the canonical set database — catalog data, retail prices, community ratings, and aggregated current values per set.

Do I need a Brickset API key? No. This actor reads the public website; no account or API key required.

How many results per run? As many as you like — pagination is handled automatically (25 sets per page on Brickset).