APIfying an ERP
summary
PlanMill describes APIfying a decade-old ERP since 2009 and redoing the API in 2014–15: a public 1.5 release now, full platform 2.0 planned next year, built alongside a new UI in React.js. Design choices include RAML for docs, HMAC and API key auth (not OAuth), JSON plus CSV/PDF exports, batch endpoints and REST hooks, SDK generation via APIMatic. Lessons: fix rate limits, avoid backend leakage, return usable error codes, and support per-field metadata and currency headers for multi-country customers.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:10Customers
- 2:00First API
- 3:55API usability problems
- 5:08New API
- 9:10Architecture Choices
- 16:30Design Discussions
- 16:55Hooks
- 17:22API Wars
- 17:38API Integration
- 18:01UI
- 18:19Security
- 19:04Conclusion
related talks
23mWhat Makes an Agile API?
23mApidays Virtual Helsinki - Harri Koponen, Visma
21mAPI Evolution: Master the Future of Business Integration
25mAPI, the next 10 years: Beyond the Interface
22mAPIs: The Backbone of Retail's Digital Transformation
43mAPIs Are the Backbone of Every Company
25mTransforming the enterprise with APIs
51mERP project for tens of thousands of users: scared but doing it — how?