Understanding the root causes of API drift

Many APIs stray from their definitions. My latest feature on Nordic APIs explores the root causes behind API drift.

A recent report found 75% of APIs stray from their OpenAPI specifications. That surprised me and inspired me to ask: why is drift so common?

There are a ton of answers to why drift is endemic. Intentional documentation and spec-first cultures are rare. APIs keep multiplying yet API governance is still in its infancy. Others attribute it to a lack of comprehensive testing and tools to produce quality descriptions. Or, a lack of discipline in general.

Today on Nordic APIs, I dive deeper into API drift to understand some of the root causes and to see how drift impacts developer experience and the business at large. We also put together some solid tips on ways engineering leaders can mitigate drift.

All in all, it seems like solving the drift problem will require tools to detect drift, conformance testing, as well as spreading more knowledge-sharing and clarifying responsibilities. 

Thank you to APIContext for igniting some interesting discussion and to everyone who participated in this story!