The Language of API Design: Creating your OpenAPI Description
API design is an essential part of the API lifecycle, but what does it really take to design an API? You need a domain model to start from, but what's the best way to continue after that?
In the second part of "The Language of API Design" series, David Biesack (Chief API Officer at Apiture) talks about how to turn a domain model into OpenAPI, how to start working on responses and problem reports, and how to make sure that your API design uses established design practices.
This video is based on David Biesack's "The Language of API Design" series of articles on his "API Design Matters" Substack. For a deeper dive into the topics, here are links to the series and the individual articles:
👉 "The Language of API Design" Series Overview - https://apidesignmatters.substack.com...
👉 Chapter 4: From Domain Model to OpenAPI - https://apidesignmatters.substack.com...
👉 Chapter 5: What Am I Getting Out of This? - https://apidesignmatters.substack.com...
👉 Chapter 6: Your API Has Problems. Deal With It. - https://apidesignmatters.substack.com...
👉 Chapter 7: Don't Repeat Yourself When Designing APIs - https://apidesignmatters.substack.com...
In case you missed the first video, you can find it here:
🎥 The Language of API Design: Creating Your Domain Model - • The Language of API Design: Creating Your ...
Stay tuned for the third video where we will talk about how to dive deeper into the design of API payloads by taking a closer look at JSON schema and some of its features.
#api #apimanagement #apidesign #digitaltransformation #openapi #design