include.image_alt

5 ways to update a boolean status with a REST API

By Arnaud Lauret

Last week, someone sent me a direct message on Twitter asking the following question: Let’s say you have a resource with an activated boolean property, how would you design the operation(s) allowing to activate or deactivate it? As this is a use case I often encounter during API design reviews or API design workshops, I thought it would be interesting to share my usual answer(s) with everyone.

include.image_alt

Full Life Cycle API Management is not enough, let’s try 8K API Management

By Arnaud Lauret

You didn’t knew that API Management was old and you needed a “Full Life Cycle” API management solution to help you achieve your API strategy? Well, I didn’t. To be honest, though the term is quite old, I didn’t realized until recently that “Full Life Cycle API Management” started to replace simple “API Management”, at least in software vendor communications. But what if I tell you that this “Full Life Cycle” version is already dead? What if I tell you that you need 8K API Management?

include.image_alt

Toro Cloud's Coding Over Cocktails Podcast: The Design of Web APIs

By David Brown & Kevin Montalbo & Arnaud Lauret

I was invited by David Brown and Kevin Montalbo for Toro Cloud’s Coding Over Cocktail podcast. We discussed API consistency, how to make your APIs more discoverable, defining and setting the boundaries between an API gateway and API implementation, and choosing the right API architecture and technology for the right problem.

include.image_alt

Stoplight's API Intersection Podcast: The Ultimate Guide to Style Guides

By Jason Harmon & Adam Duvander & Arnaud Lauret

I was invited to Stoplight’s API Intersection podcast hosted by my two good friends Jason Harmon and Adam Duvander. As it was Stoplight’s “Style Guide September”, we discussed one of my favorite topics, covered quickly in my book The Design of Web APIs, and that I practice everyday helping people to create APIs: API design style guides.

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).