To empower developers to consume Web APIs to fulfill the use-cases they care about.

A Coruña, Spain
Joined December 2006
User journeys usually start with one or more requests to a REST API followed by events. You think in terms of capabilities, not protocols. Why do we document synchronous and event-driven APIs separately? apichangelog.substack.com/p/…
61
What is the unit of value in APIs? If you were to create an API marketplace, what would you target as the unit of value? Ultimately, consumers want the capabilities provided by the APIs, not the APIs themselves. notes.brunopedro.com/2023/06…
40
Reading isn’t enough when you want to learn something new. To actually learn how to do something, you need to try it. Perhaps you’ll fail a few times, but that’s all part of the learning process. apichangelog.substack.com/p/…
72
Currently #writing about synchronous vs. event-driven API documentation.
70
Sooner or later, every change you introduce to your API will break the integration with at least one consumer. The interface stops being the interface. Hyrum goes further and says the "interface has evaporated." apichangelog.substack.com/p/…
1
2
92
I can see this flow for AI-enabled Product Development producing great results: User Interviews → Problem Discovery → User Story Distillation → SDD → Verification against Acceptance Criteria → Delivery
87
The challenge with agentic workflows and stateless APIs is related to the need to handle user input as a response to a request. The solution seems to be doing “multi round-trip requests” using something called InputRequiredResult. apichangelog.substack.com/p/…
65
Should agents generate integration code once or let AI figure out how to consume APIs whenever they need to? These two choices are, in fact, a false dichotomy. apichangelog.substack.com/p/…
71
Creating a new OpenAPI extension is as easy as starting a property name with the x- string. But what happens when two or more extensions pick the same property name? apichangelog.substack.com/p/…
78
Is feature A sending a command to feature D, or is it simply sharing information about something that happened? brunopedro.com/2022/10/19/ev…
61
More than half of large companies now manage more than 1,000 APIs. If each API has, on average, 10 operations, you end up with an inventory that is almost impossible to manage. apichangelog.substack.com/p/…
1
136
I've been #writing about OpenAPI vendor extensions and ways to prevent collisions.
1
107
What is the relationship between API Governance and quality? The best approach to managing API Governance is not to ask people to follow rules blindly. Instead, it’s better to start from the end goal of having the best possible API quality. brunopedro.com/2024/05/25/ap…
106
"Other than yourself, the developers from your team, and a couple of customers, no one really used your API. When you ask your team why there’s no usage, they can’t explain it." apichangelog.substack.com/p/…
1
1
155
I've been working on a Swagger UI plugin that highlights API changes inline. Instead of having to open a report with all the changes, you can see them while browsing the documentation. github.com/InditexTech/swagg…
2
1
84
"Every API product starts with an idea," I wrote in the book Building an API Product, in 2024. How do you navigate the ideas that help you create API products?
1
54
This is the distribution of API operation categories after analyzing more than 50k OpenAPI documents from public GitHub repositories. I inferred a taxonomy by comparing the morphology of each API operation with a set of pre-established heuristics.
1
2
86