Keynote 1
summary
Customer-facing REST APIs connect Finnlines and Grimaldi Lines booking systems with customer ERPs and cloud packages, exposing schedules, allotments, bookings (trailers, lorries, containers), hazardous-goods data and tracking, built on Finnlines ePass for integration and a Node.js demo app. A centralized API product and user-management system with a permission ledger supports per-user restrictions and environments; production sees 1 million API instances monthly, ~100 API processes and two full-time API engineers. Real-time confirmations enable day-one B2B onboarding and power a self-service check-in kiosk; challenges are backend compatibility, legacy rules and differing mandatory fields.
AI-written summary · about
chapters (11)
- 0:00Customer freight booking APIs
- 2:10Freight customer bookings API
- 5:03API project idea to implementation
- 8:15Permission ledger and API product
- 10:08Data model and user permissions
- 12:53First production release and restrictions
- 14:42Web app demo and API status
- 15:46Business benefits and B2B integration
- 18:13Lessons from API development
- 20:49Future API notifications and Atlas vision
- 22:55Summary
related talks
25mAPIs for Business Scalability
37mAPIs in City Mobility: A Use Case
26mFrom project to reality let's explore some API
20mThe story of Fyndiq's API
22mCommercialising APIs: A Product Owner's perspective.
23mApidays Virtual Helsinki - Harri Koponen, Visma
26mHow APIs Turn Fragmented Journeys into Seamless Experiences
20mAPIfying an ERP