include.image_alt

How public web APIs raise software bar

By Arnaud Lauret, February 26, 2018

While answering some question on my Design of Web APIs book’s forum, I wrote:

Now that I have seen brilliant Web APIs that can be used so easily because of their design but also the overall experience some can provide (the famous “DX”) I have become far more demanding and challenging with software in general

Yes. Public web APIs definitely raise software bar. The whole software industry should take example on them …

include.image_alt

The story behind The Design of Web APIs book

By Arnaud Lauret, February 10, 2018

I’m thrilled to announce that I’m writing a book about API design: The Design of Everyday APIs (edit: the book has been renamed The Design of Web APIs since this post has been written). 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 fcclauret discount code to get 37% off). 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.

include.image_alt

API Styleguide, the Lord of API Designs

By Arnaud Lauret, November 12, 2017

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.

include.image_alt

...And GraphQL for all?

By Arnaud Lauret, September 29, 2017
GraphQL is new. GraphQL is cool. Look! Github dumped REST for it! We MUST do it too! Well, why not. GraphQL could be a great tool, but like any tool, you don't choose it "just because".You choose it because it solves a problem in a given context. You choose it knowing its strengths and weaknesses. During this session, while discovering what is GraphQL we will see what REST API providers should think about before blindly dumping REST for it
include.image_alt

Deliveroo API Design Guidelines added to the API Stylebook

By Arnaud Lauret, April 25, 2017

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.

include.image_alt

API Design Tips And Tricks - Getting, creating, updating or deleting multiple resources in one API call

By Arnaud Lauret, April 22, 2017

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.

include.image_alt

OpenAPI Visual Documentation updated with 3.0.0-rc0

By Arnaud Lauret, March 19, 2017

The OpenAPI Visual Documentation has been updated. The new version 3.0.0-rc0 of the OpenAPI specification has been added. The addition brings a fully detailed change log of what has change from version 2.

include.image_alt

Google API Design Guide added to the API Stylebook

By Arnaud Lauret, March 5, 2017

I’ve just added the Google API Design Guide to the API Stylebook.

This guide is slightly different from the other ones because it deals with REST and RPC API design focusing on gRPC APIs using Protocol Buffers v3.

To discover this API design guide and a short review, let’s go to the API Stylebook blog.

include.image_alt
Writing OpenAPI (Swagger) Specification Tutorial Series - Part 9

Extending the OpenAPI specification

By Arnaud Lauret, February 19, 2017

This is the end, my OpenAPI friends, the end. The end? Not really. This last part of the OpenAPI tutorial is a new beginning. With previous parts we have learned to master the OpenAPI specification but there’s a last thing to learn to unleash its full power: extensions. This format is easily extensible, it allows to add custom data within an API description. But for what purposes? Let’s have a glimpse of these extensions endless possibilities.

include.image_alt

...And GraphQL for all? A few things to think about before blindly dumping REST for GraphQL

By Arnaud Lauret, January 22, 2017

GraphQL is new. GraphQL is cool. Look! Github dumped REST for it! We MUST do it too!
Well, why not. GraphQL could be a great tool, but like any tool, you don’t choose it just because. You choose it because it solves a problem in a given context. You choose it knowing its strengths and weaknesses.

While discovering what is GraphQL we will see what REST API providers should think about before blindly dumping REST for it. From design and implementation to pricing model and analytics down to developers experience and implementations, choosing an API design style will have impact on the whole API lifecycle. Therefore, this choice must be an enligthned one and not based on simple beliefs.

By continuing to use this web site you agree with the API Handyman website privacy policy (effective date , June 28, 2020).