Automating API Client Generation
summary
Kaltura encodes the API surface as an XML reflection of internal classes (objects, enums, actions, filters) and runs a parser that emits client libraries in about 15 languages; generators are written in PHP, run in CI, test each build, and publish only libraries that pass. The pipeline also converts XML to a Swagger spec and feeds LucyBot to produce an interactive developer portal and multi-step workflows for complex operations like five-step chunked uploads. Maintenance used to consume ~40% of dev time.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:50The Psychology behind Marketing Your Api as a Product
- 5:24Solution for Keeping Your Api Libraries up to Date
- 7:19Own Xml Schema
- 8:45Introspection Layer
- 9:46Interactive Workflows
- 10:44Create Your Own Client Generators
- 11:05Wrapper Script
- 12:28Figure Out Your Api
- 13:15Create a Definition of Your Api
related talks
18mSimplifying Consuming APIs for SDK Haters
35mOpensource API Tools to agile your apifirst strategy.
25mBuilding an API Client SDK
26mOpenAPI Generator - The Babel Fish of the API World
29mTooling
05mHow to end manual REST-API client coding
33mA self-describing API
49mBuilding Software Better: API Lifecycle Management for Developers