Tackling OpenAPI Drift
summary
A case study of Acme FS shows API drift affecting 30% of endpoints in common workflows and costing a lost deal; the team combines Postman collections with a validating proxy (Prism) and a CI pipeline that merges OpenAPI files with the Redly CLI, filters unused components, and runs an add-props tool to set additionalProperties=false. That process fixes core-journey drift in five days, raising conformance from 70% to 100% and enabling the next POC to succeed.
AI-written summary · about
chapters (7)
- 0:00OpenAPI drift challenges
- 2:09API drift industry issue
- 6:07Acme FS case study
- 9:39Countermeasures considered
- 17:46Provider driven contract testing
- 21:47Lessons from Acme FS
- 24:16Summary
related talks
44mIntroduction to API Drift
45mAgile API Development, Bringing Testing and Development Together
33mCollaboration & Productivity-Missing Links in API Development
35mOpensource API Tools to agile your apifirst strategy.
47mContract-Driven API Development with OpenAPI Specification
24mFixing API Chaos: A Practical, Open Method to Structure API Work
28mAPI First to the Extreme - Federated API Design via Inner Sourcing
19mAvoiding the 8 Wastes of Lean API Development with OpenAPI & APIOps.