What is API Microversioning and Why Should API Providers Consider It? #readingTodayThe basic idea behind API microversioning is that even the slightest change to an API would constitute a new microversion number. In the video, the presenters routinely refer to version 2 of an API whose microversions span 2.0 to 2.22. All microversions are kept in production simultaneously, there's one endpoint that services all of them, and the consuming developer specifies which microversion s/he prefers using a field in the HTTP header (what they call a "magic header field"). Additionally, a secondary "versions API" runs sidecar to the primary API -- one that can be interrogated by the developer in order to figure out things like what is the API's current version, what is the range of supported microversions (ie: 2.0 to 2.22), and what other primary versions (ie: 1.0) are still supported.