Internal/private APIs and money Series - Part 1
When internal API platform billing model collides with API-First strategy
By Arnaud Lauret, April 20, 2022
An internal API-first strategy will inevitably raise budgets questions; you must be aware of that. One of them is who will pay for the brand new API platform and how? The success of an internal API-first strategy may depend on the billing model of the API platform.
What is an API platform and what skills are needed to build it
By Arnaud Lauret, April 13, 2022
LEGO is looking for an associate API Engineer for their API platform. LEGO+APIs! That looks awesome! But what is an API platform and what skills do you need to build it? Does the LEGO job offer list them all? Do you have them all? This post answers those questions and may help you apply to such offers or post the appropriate job offers to build your own API platform.
Postman Tips and Tricks Series
How to use Bootstrap in Postman Visualizer
By Arnaud Lauret, April 11, 2022
Postman Visualizer is perfect to tinker with data returned by an API and learn how it works. I found using HandlebarJS HTML templates quite convenient. But I was mindblown when I realized I could take advantage of Bootstrap to generate outstanding visualization without much effort. Let’s see that with The 5th Edition Dungeons and Dragons API in its GraphQL version.
Choosing a public API style when a private API style already exists
By Arnaud Lauret, April 6, 2022
“What will be the style of our public/partner APIs? Should we reuse our existing private APIs style? Should we restart from scratch and use a totally different style?” This discussion happens quite often in organizations starting their public API journey (and if it did not happen, it must happen.) This discussion can have important consequences that must be carefully evaluated.
Twitter API v2 Tips and Tricks Series
What can we learn from tweets lookup error responses of Twitter v2 API?
By Arnaud Lauret, April 5, 2022
What can we learn from tweets lookup error responses of Twitter v2 API? We can learn how to use the tweets lookup operations parameters without reading much of the documentation. We may also learn a few API design, implementation, and documentation principles in the making. And icing on the cake, the technique shown in this post can be applied on any API.
3 dimensions to consider for a successful API-First strategy Series - Part 3
Don't organize APIs against ownership
By Arnaud Lauret, March 30, 2022
It doesn’t matter how APIs are organized, in layers, by business domain or any other dimension if you don’t take care of the most important one. The one dimension that rules them all: ownership. This post is the third and last of the “3 dimensions to consider for a successful API-First strategy” series.
Postman Tips and Tricks Series
We always forget to select a Postman environment
By Arnaud Lauret, March 26, 2022
When using Postman, it’s a best practice to store API token values in environment secret variables. Environment variables can also be used to store other variables uses in scripts. But when opening a collection, we often forget to select an environment and spend a few seconds if not minutes or more trying to figure out what the problem is with a request. Just to realize in the end that we just forgot to select an environment. How can this be avoided?
3 dimensions to consider for a successful API-First strategy Series - Part 2
Organize APIs around business domains and capabilities, not tools
By Arnaud Lauret, March 23, 2022
People don’t want drills, they want to make holes. APIs are interfaces exposed by pieces of software, our modern tools. But it would be a terrible idea to think of APIs just as interfaces to tools. APIs must be organized around our business domains and capabilities. This post is the second of the “3 dimensions to consider for a successful API-First strategy” series.
3 dimensions to consider for a successful API-First strategy Series - Part 1
Organizing APIs in System, Business, and Experience Layers
By Arnaud Lauret, March 16, 2022
Either for historical, organizational, or technical reasons, not all APIs are at the same level, especially in organizations that do not start their API-First journey from scratch. APIs can be organized into three different layers: system APIs, business APIs, and experience APIs. This post is the first of the “3 dimensions to consider for a successful API-First strategy” series.
Building a healthy and profitable relationship between tools and specifications
By Arnaud Lauret, March 9, 2022
We may never have a clear answer to the question “what comes first? Tools or Specifications?”. What is sure is people create tools or specifications based on their needs. Those tools and specifications, like OpenAPI, AsyncAPI, or JSON Schema, are tightly intricated. What could be done to build a healthy and profitable relationship?