I’m thrilled to announce that I’m writing a book about API design: The Design of Everyday APIs. This book is published by Manning Publications and the first two chapters are now available on the Manning Early Access Program or MEAP (affiliate link, use mllauretlt discount code to get 50% off until the 21th of February). This book is for everyone who wants to learn API design. But, what’s the story behind this book about API design? To answer this question, let’s talk about my other passion: guitar.
Join Frodo, Gollum and Gandalf on an epic API design adventure. In this session, based on my own experience defining and sharing API design common practices in my company and based on the API styles guides that I have collected on apistylebook.com, we will discover why we desperately need API style guides and how they can or cannot help us create a smooth API surface for a company.
My talk …And GraphQL for all? A few things to think about before blindly dumping REST for GraphQL which I gave at API Days Paris 2016 last December was recorded and the video is now available on InfoQ.
You can also read my write up here on the blog.
I’ve added the Deliveroo API Design Guidelines to the API Stylebook.
These guidelines are definitely a MUST read for any API designer.
To discover this API design guide and a short review, let’s go to the API Stylebook blog.
API Design Tips And Tricks - Getting, creating, updating or deleting multiple resources in one API call
Getting, creating, updating or deleting multiple resources in a single API call is a common need in REST APIs. But how to achieve that in a consistent way accomodating how we work with a single resource and REST principles? This is what we’ll see in this post.