What is wrong with API wrappers and how can we do better
summary
Claims a small framework that generates wrappers and uses requests to make real API calls and handles pagination automatically. Demonstration shows live Facebook calls, posting succeeds, and wrappers expose endpoints for interactive exploration. Tapioca enforces a uniform interface, has HATEOAS/hypermedia support, and cuts code size (Tapioca Facebook ~250 lines vs facepy ~1000; Tapioca Twitter ~150 vs python-twitter ~6000). Author reports one hour to write Parse.com wrapper.
AI-written summary · about
chapters (5)
related talks
28mHarnessing the APIs you didn't know existed
47mBuilding APIs your users will want to use
27mAPI development for data analysts/scientists with FastApi
18mSimplifying Consuming APIs for SDK Haters
29mSuccess of your framework depends on your API
01h 00mDesigning Programmer-Friendly APIs
10mShapir: Standardizing and Democratizing Access to Web APIs
34mThe API Evolution