Building APIs Together: How to Embrace a Multi-Player Strategy.
summary
Argues that collaborative API development is essential, not optional, and shows concrete results: adding a run-in-Postman button and importable collections helps onboard 700 apps to an ecosystem; Postman reports 35 million developers and cites a State of the API survey of 40,000 developers finding 61% of APIs are internal. Describes implemented features — Collections, public/private/partner Workspaces, version history, a Package Library for reusable scripts, mocks and CI tests, plus Postspot AI with over a million users — and claims these reduce duplication, speed delivery and catch bugs earlier.
AI-written summary · about
chapters (7)
- 0:00Collaborative API development
- 4:42APIs need collaboration
- 7:51Multi-player API development
- 10:21Benefits of collaborative APIs
- 15:15Multi-player API workflows
- 20:34Scripts and AI in APIs
- 23:07Conclusion
related talks
26mCollaborate Like You Mean it: The End of Siloed API Development
35mThe Future of APIs: Postman's Founder Speaks
22mRevolutionizing API development: Collaborative workflows with Postman
25mPostman Session: Supercharge API Collaboration With Postman
23mAPIs at Scale for a Great Developer Experience
35mMastering API Ops: Build Scalable Applications
30mDevelopers Are Pioneers Not Unicorns
34mAPIs Are Eating the Universe