Searching for a LEGO scanner API? Here's the honest answer: brick'em doesn't offer a public API today. What high-volume resellers actually use is the brick'em app plus its export files. You scan minifigures in bulk, the AI identifies and prices them, and a CSV export moves that data into whatever system you run. This page covers what the recognition tech does, how to automate without an API, and how to tell us if you genuinely need direct access.
Is there a public LEGO scanner API?
Not from brick'em, not today. If you've seen pages promising endpoints, rate limits, and developer tiers for LEGO scanning, be skeptical. We build the scanning engine ourselves, and we don't currently expose it as a public API.
That's not a forever answer. Enough resellers have asked that an API stays on our radar. But we'd rather tell you what works right now than sell you documentation for something that doesn't exist.
How the image recognition works
You take a photo of your minifigures, up to 50 in a single shot. The AI matches each figure against a database of 18,900+ minifigures and returns identifications with live BrickLink pricing. The published accuracy benchmark is 98%.
No barcodes, no part number lookups, no typing. The photo is the input. That's the whole point: identification and pricing happen in one step instead of five.
Automating without an API
Most of what people want an API for is getting scan data out of one tool and into another. brick'em handles that with exports:
- Generic CSV for spreadsheets, custom systems, and inventory software
- BrickLink XML for store mass uploads
- eBay Seller Hub draft-listings CSV
- BrickStore, BrickOwl, Shopify, Whatnot, and Facebook formats
The generic CSV is the workhorse for custom setups. It's plain, structured data: identifications, quantities, conditions, prices. If your system can import a CSV, it can consume brick'em scans.
The workflow serious resellers run
Scan a lot in bulk. Review the matches. Export. Import into your own system or straight into a marketplace format. Repeat per lot. It's not a REST endpoint, but it processes hundreds of figures a session without clicking through screens one figure at a time.
Want direct API access?
Tell us. If you're building something real and exports won't cut it, reach out through brickem.io and describe the use case. Actual demand is what moves an API up the roadmap.
Related reading
| What you'd want an API for | How to do it today |
|---|---|
| Bulk identification | Bulk scan, up to 50 figures per photo |
| Pricing data | Live BrickLink prices on every scan |
| Feeding your own system | Generic CSV export |
| Marketplace listings | eBay draft CSV, BrickLink XML, Whatnot CSV |
| Direct endpoint access | Not available yet. Tell us you need it |
FAQ
Does brick'em have a public API?
No. There's no public brick'em API today, and no paid tier that unlocks one. The scanning engine is only available through the brick'em app. If you need direct access for a serious integration, contact us through brickem.io and tell us what you're building.
How do I get scan data into my own system?
Export a generic CSV from brick'em. It contains identifications, conditions, quantities, and prices in plain structured data, and imports into spreadsheets and most inventory software.
How accurate is the recognition?
brick'em's published benchmark is 98% accuracy on minifigure identification. You review matches before saving, so uncertain calls never slip into your inventory unseen.
Will a brick'em API launch in the future?
Possibly. It's a question of demand. If exports genuinely won't cover your workflow, reach out and describe your use case. Real requests from real builders are what move it up the roadmap.
You don't need an API to move fast. Scan up to 50 minifigures per photo, price them with live BrickLink data, and export CSV straight into your workflow. Start your 14-day free trial. Pro is $20/month or $200/year.
