API Versioning

We want to make it easy for you to track the continuing development of the API. Like most software, we maintain a version number of the API which makes it easy to tell when there have been additions or changes to the API.

The API Versioning scheme we use is as follows:

Fragment	Example Value/s	Meaning
First element	3.1.2	The major version of the API. A change to this denotes a significant change to the core API. We have only done this twice - in the move from Version 1 to Version 2 (in 2017), and now to Version 3.
Second element	3.1.2	A change to this denotes a significant addition or change to the API - typically a new API end point.
Third element	3.1.2	A change to this denotes a minor addition or change to the API - perhaps a bug fix or a new response JSON key has been added.

API Version number is for structure and functionality only

Note that these API version numbers only concern the structure and functionality of the API, they have no bearing on the Detect End Point or the Version Number reporting which are typically updated and expanded daily.

The version number of the API will only increase when there are changes or additions to the API itself.

View the WhatIsMyBrowser.com API Version History.