include.image_alt

Attempting to define API governance

By Arnaud Lauret

In the collective unconscious, API governance often rhymes with API police. Reducing API governance to the need for order caused by the chaos of an organization’s myriad APIs is too reductive, and it risks not looking at the problem at hand from the right angle. Why not define API governance relatively to IT governance, corporate governance, and governance to better understand what it is?

include.image_alt
OpenAPI Specification Reference Series - Part 2

What is the info property in OpenAPI?

By Arnaud Lauret

The info property of an OpenAPI document contains metadata that provides an overview of an API, but what does it represent exactly? How did it evolve across the OpenAPI Specification versions? And how to can it be used and misused? This is the second post in the OpenAPI Specification Reference series.

include.image_alt

Le Clash REST vs GraphQL

By Nicolas Barrasson & Jonathan Jalouzot & Arnaud Lauret

L’idée folle de l’équipe Microsoft User Group France pour API Days Paris 2021: un clash REST (représenté par votre serviteur) vs GraphQL (représenté par Jonathan Jalouzot, tenancier du Meetup GraphQL Paris) arbitré par Nicolas Barrasson.

include.image_alt

Talking about The Design of Web APIs with Erik Wilde

By Erik Wilde & Arnaud Lauret

Had a great time chatting with Erik Wilde about the motivation for writing The Design of Web APIs book, and why it specifically focuses on the design aspect of the API lifecycle (and also why it is not titled The Implementation of Web APIs).

include.image_alt
Arnaud Lauret's

API Stylebook

I started this project with a simple API Design Guidelines list in mind and ended with a fully analyzed collection of API design guidelines. I created it for others but I use it myself too. When I wonder how to handle some API design matters, I select the related topic and read how others handle it. To be honest, it needs some refresh, it is a real pain to update and maintain and could be more user friendly; that’s on my todo list.

include.image_alt
Arnaud Lauret's

OpenAPI Map

I built the OpenAPI map because I was constantly searching for “how do this with the OpenAPI spec” and also “but where is that thing” in the specification. Having the OpenAPI specification represented as a tree given essential information and quick access to source documentation of each element saved me countless time.

include.image_alt
James Higginbotham's

API Developer Weekly Newsletter

Hundreds if not thousand of websites talk about APIs, I rely on James Higginbotham’s newsletter to stay up to date about what is happening in the API space thanks to his weekly selection of great posts.

include.image_alt
Matthew Reinbold's

Net API Notes Newsletter

I always read Matthew Reinbold’s Net API Notes Newsletter with delight. It’s not just a bunch of links; every week Matthew actually writes a letter in which he shares his thoughts accompanied with links to relevant posts of the past week.

include.image_alt
Erik Wilde's

Web Concepts

If you wonder what means a 418 HTTP status code or which RFC defines the txn JWT claim, Web concepts is what you’re looking for. I just stopped doing HTTP/web/RFC related search, I now always check Erik Wilde’s web concepts first and usually find what I’m looking for instantly. Icing on the cake, all data is also available in JSON format.

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