Read Should Every Company Consider Providing an API? on Nordic APIs blog
By Arnaud Lauret, June 10, 2015
My other self Arnaud Lauret writes about APIs too. This week you can read Should Every Company Consider Providing an API? on Nordic APIs blog.
Do you really know why you prefer REST over RPC?
By Arnaud Lauret, May 10, 2015
The data, the hypermedia and the documentation
By Arnaud Lauret, April 24, 2015
When I look at hypermedia media-types and API definition languages I feel that the frontier between data and documentation is becoming thinner as my knowledge of the API world grows and as the API world evolves.
The API crash test project
By Arnaud Lauret, April 5, 2015
As I was writing my HAMM and ways of API smartness posts, I wanted more. As I was discussing with smart people about APIs, I wanted ever more. I want to delve deeply into the API ways.
The ways of the API smartness
By Arnaud Lauret, March 28, 2015
An API must be smart to ensure that consumers will want to use it and remain dumb when they consume it.
Hypermedia API maturity model Series - Part 2
The missing links
By Arnaud Lauret, March 15, 2015
Hypermedia is not only a conceptual and philosophical subject of interesting and animate debates among the API community, it’s also a concrete solution we can use to cover concrete needs. In this second part of hypermedia API maturity model (HAMM) series I will talk about my own experience to expose two missing (in my humble opinon) notions in common implementations and include these missing links in an updated version of the HAMM.
Hypermedia API maturity model Series - Part 1
By Arnaud Lauret, February 28, 2015
When we talk about hypermedia for an API, we’re talking about making it discoverable or browsable. Adding hypermedia to an API potentially brings flexibility, loose coupling, better human readability on the fly and even machine readability on the fly. But nowadays, the hypermedia area for APIs is still a work in progress and it can be implemented in many ways leading to different levels of hypermedia-ness.
The beautiful API and the bestial back-office
By Arnaud Lauret, February 16, 2015
When you design an API (even an internal/private one) upon an existing back office (to plug a mobile application on it for example), you should take care of one thing: an API is a display, not a window. An API’s purpose is to expose your data and data processing but an API is only a representation and you’re under no obligation to directly expose the crude reality.
Why you must design your private API in english
By Arnaud Lauret, February 7, 2015
Why you must design your private API in english.
Pourquoi vous devez concevoir votre API privée en anglais.
Perché è necessario progettare la vostra API privata in inglese.
Por qué debe diseñar su API privada en Inglés.
Deshalb müssen Sie Ihre private API in Englisch entwerfen.
As you might have guess, this post targets people designing APIs in non english speaking countries. When you design an API there are many little things that you risk to forget or not take into account, especially when this API is private/internal, and later you may bitterly regret it. Choosing a language for your API is one of them.
By Arnaud Lauret, February 7, 2015
Welcome to the API Handyman blog!
You can read a more complete presentation of the API Handyman blog here.
The API Handyman blog is about sharing my views and experiences on the API field from both provider and consumer points of view with (I hope) a pragmatic and unvarnished approach. I hope you’ll enjoy reading my posts and I’m looking forward to your feedback and comments.