Let's talk about challenges when interacting with web APIs again. In this episode I focus on the contract, in other words, the structure of the data that is going back and forth between an API and the client consuming it.

How can the consumer be sure the structure of this data is as they expect, and nothing (suddenly) breaks?

This is particularly a challenge when the client consuming the API is a separate application, because then the client has a "copy" of the API structure in their code, in the form of type definitions, tests, mocks, etc.

---

About Bouwe's Briefs: Short podcasts where I ramble about the things I find interesting in software development, content creation and careers.

To learn more about me, visit my blog at https://bouwe.io, follow me on Twitter https://twitter.com/bouwe, or check out my other podcast Curious Coders Chronicles at https://open.spotify.com/show/2s3E6ilQeGBUwwe2TwnDO9?si=f343468fe1ec4599