lifecycle
lifecycle copied to clipboard
postman-open-technologies
What is API-first?
This is the discussion around defining the "What is API-First" blueprint. You can chime in on the ideation here, and see the current version of the blueprint here.
Some relevant content already created:
- What Is an API-First Company?
- Why Should You Be an API-First Company?
- How Do You Become an API-First Company?
Some external links to content:
- Enabling Application Development Velocity in an API-first World
- The 5 principles of API-first development. And what does API-first even mean?
- How Far API-First Companies Have Come
- Exploring the API-First Design Pattern
- What Is API First?
- You Are API-First
- API-First [Business]
- API-First [Design || Code]
- Helping Developers Work Smarter With Our API Marketplace
- API-First Approach is Key to Integrating Systems, says Neptune Software
- Innovating with MACH Part 2 – The Business Value of API-First
Additional links:
- Is API First Still Relevant?
- Three Principles of API First Design
- API First or Events First: Is it a Binary Choice?
API first, part one: how do we put “API First” first? — this blog post is well-organized and thorough. The other 3 posts in the series are great as well, but this one in particular has a table that breaks down what API-first means at different organizational levels, which I found really helpful.
API-FIRST: LEGOS FOR BUSINESS - To ensure we’re speaking the same language: I think of a company as “API-First” if the service offered is comprehensively accessible via a read-and-write API. API-First does not mean “API Only”; instead it means that the API will always be a first-class citizen and is the primary means of interaction with the service offered