Agile API Development, Bringing Testing and Development Together
summary
Panelists give concrete practices: shift to design-first with OpenAPI (mandatory spec repo, code generation, mock servers) cuts integration wait from weeks to minutes; CI pipelines auto-sync OpenAPI to Postman collections auto-generated and run tests via Newman CLI and Rest Assured for isolation vs live data. Governance uses linting and Optic governance to block breaking changes. PayPal reports 10+ public collections and being the number one fintech collection; enterprise-scale context cites ~200 markets, ~400M customers and 35M merchants.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:35Presentation
- 5:09Team Structure
- 10:11Developer Journey
- 13:36API Development Process
- 15:34API Design First
- 19:10API Metrics
- 20:56First API Call
- 24:58How to Communicate API Changes
- 27:18How Southwest Austin Communicates API Changes
- 31:09Common API Pitfalls
- 34:49Southwest
- 40:02AI
- 43:19Rapid Fire
related talks
23mSolving Challenges in API Testing to Achieve More Agile Development
26mCollaborate Like You Mean it: The End of Siloed API Development
24mBuilding APIs Together: How to Embrace a Multi-Player Strategy.
49mBuilding Software Better: API Lifecycle Management for Developers
23mWhat Makes an Agile API?
21mAPI Design in FinTech: Challenges and Opportunities for next-gen APIs.
38mAPI Mastery: from the Design to Development
22mRevolutionizing API development: Collaborative workflows with Postman