Postman Collections as Part of Your Developer Experience panel
summary
Teams convert OpenAPI into runnable Postman Collections, add pre-request scripts for auth, and use test scripts to chain responses so multi-step workflows run with one click; collections spark internal testing, sales demos and a spike of downloads (28,000 page views) and cut bulk-admin tasks from hours to minutes. Plans include automated OpenAPI → collection pipelines, Run in Postman button integration, using mock servers for safe demos, and tracking time to first call and collection-specific usage.
AI-written summary · about
chapters (14)
- 0:00Introduction to panel
- 1:09Panelist introductions
- 6:20Why start with Postman collections
- 12:27Enhancing collections beyond endpoints
- 19:11Internal and cross-team use
- 25:57Managing community collections
- 31:17Tracking adoption and metrics
- 33:44Authentication and scripting tips
- 40:40Manual vs automated collections
- 43:51Sandboxes and mock servers
- 48:30Future improvements and plans
- 54:10Collaboration and governance
- 57:02Starting with collections early
- 59:58Closing thoughts and Q&A
related talks
22mRevolutionizing API development: Collaborative workflows with Postman
28mOptimizing the developer experience through collaboration
25mPostman Session: Supercharge API Collaboration With Postman
23mPostman Session: Speed Up Your Developer Workflows with Postman
35mMastering API Ops: Build Scalable Applications
34mPostman & Newman for your CICD
16mAutomation API Testing
32m10 things about Postman everyone should know