Building an API platform One brick at a time
summary
LEGO builds an internal auth API called LEGO ID to let external partners link child accounts without sharing passwords, using an iframe on Chima Online and a global user ID to connect Warner Brothers accounts; the integration relies on third-party cookies and avoids OAuth2 because of browser/IE7 constraints and perceived immaturity, forces heavy moderation and COPPA-compliant parental consent workflows, and keeps APIs private for brand protection and readiness rather than offering a public brick database.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:57Lego Fun Snacks
- 3:44How we collect data
- 5:19Trust
- 9:35Liquor ID
- 10:53New Theme
- 12:23Warner Brothers
- 14:44IFrame
- 18:09Chart
- 21:33Mobile Apps
- 23:08Top Secret Projects
related talks
59mBecoming API- & Cloud-First at the LEGO Group
29mBrick by Brick What Lego Taught Me About Great APIs
34mBrick by Brick What Lego Taught Me About Great APIs
40mSticky API: Connect Bricks and enter a global IT-ecosystem
21mCrossing the Chasm With an API
23mThe Web3 Mullet: Web2 UX in Front, Blockchain Logic in Back
20mBuilding a secure API: Overview of techniques and technologies needed to launch a secure API
43mAPIs Are the Backbone of Every Company