The story of Fyndiq's API
summary
Fyndiq launches in summer 2010 and adds an API about a year later, turning a JavaScript quick‑snippet into a REST JSON API that scales traffic and product count; integrations in summer 2011 trigger rapid growth to ~900 merchants and ~120,000 products and monthly sales spikes. The API exposes just two resources: product and order, which keeps integration simple. Mistakes: building the API separate from core causes duplicated validation and naming mismatches; lessons are to make internal tools use the same API, provide modules for Magento/PrestaShop, and version via tokens.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:14about fyndiq
- 3:25do we really need an api?
- 4:19maybe start smaller
- 5:11minimize integration cost!
- 7:01fyndiq's rest api
- 8:16api delivers
- 9:00architecture: what we did
- 11:09architecture: how you should do it
- 12:10make your api a system foundation
- 12:20api should explain business flows
- 14:26be open with your api
- 15:57best in class: siftscience
- 16:54versioning and communication
related talks
26mAPI Monetization: How Fintechs use API Interconnectivity to Drive Revenue
26mDelivering connected digital experiences with APIs
36mAPI-First Practices in Fashion Tech
28mFrom API Products to Platform Thinking: A Strategy Guide
23mKeynote 1
12mAPI Economy and Crucial APIs to Know About
16mRevolutionizing API Integration: Fiserv's Developer Studio Journey
26mAsk your Developer: the rise of the API company