Adopting an API-First Approach: Benefits and Strategies​

Are you API-first? For many organizations, an API-first approach is the key to scaling software development. Learn about four different implementations of API-first and technical workflows for API producers.

0:00 What does API-first mean?
1:06 Contract-first (version of design-first)
2:10 Other API-first workflows
3:25 API-last (e.g. maintaining legacy APIs)
4:15 Code-first (e.g. prototype)
4:35 Requirements-first (version of design-first)
5:00 Design-first approaches
5:55 Benefits of an API-first approach

Four implementations of API-first workflows
- Contract-first
- Requirements-first
- Code-first
- API-last

Additional resources:

The API-First World | A Postman Inc. Graphic Novel

Breaking Changes | podcast with Kin Lane

API-first strategies | Postman State of the API 2022

API-first software development for modern organizations | Better Practices on medium

[ankursinha]

I did not knew this term existed. I have been working on my own projects using the API-First approach and yes, it feels very natural and productive to use this approach. Great presentation.

[tallgray]

This is the first I've heard the term API-First. My use cases have required that I develop, design and provide documentation for session handling and data object exchange. The API calls are to various IT systems like network devices, ITSM, SIEM, DDI. I've found it challenging to find other forward thinkers and planners to engage with in working methodology first. If anyone else has come across similar challenges, I'd like to hear thoughts on how to address it.