Tyk enables full version life-cycle management for your APIs, it includes the ability to define different configurations for different versions of an API and have Tyk manage route and middleware configurations on the same listen path of any given API. By default, Tyk expects to find version information in a header key, a query parameter or the first part of a URL.
Versioning can either be enabled or disabled, if an API is not versioned, a “Default” version is created which can store any path-related data and settings. Versions are set by a unique version name that matches the version tag you use to identify the version in a request, this can either be as a header field or as a parameter.
All versions have an expiry date, set this to empty for the version to never expire.
The versions fields define the value that Tyk expects to find either in the versions headers or query parameter, so if your version name is
v1 then tyk will look for a header key that matches
v1 exactly on the key that you specify (default
The target override field will replace the target path that was set in the base configuration for the version. This is not compatible with Service Discovery or Load Balanced settings.