The document states that Classic APIs have an API-level configuration (api_definition.definition.enabled) to determine if it's using versioning or not:
There is also some API-level configuration for versioning, which is located in the definition section of the Tyk Classic API definition:
The definition section has the following fields:
...
enabled: toggle to enable or disable versioning
According to the answer in this Tyk StackOverflow question, api_definition.definition.enabled does not apply for Classic APIs
This has caused some confusion for a customer who tried to set api_definition.definition.enabled to true in their Classic API (reference: Zendesk ticket 19811)
As api_definition.definition.enabled should not be used for Classic APIs, this should either be omitted from the document, or should be marked as "not applicable"
Branch/Environment/Version
api_definition.definition.enabled
is populated by default (set tofalse
) when creating Classic APIs using versions aboveRelevant Document
https://site-dev.tykbeta.com/docs/tyk-gateway-api/api-definition-objects/
Describe the request
api_definition.definition.enabled
) to determine if it's using versioning or not:api_definition.definition.enabled
does not apply for Classic APIsapi_definition.definition.enabled
totrue
in their Classic API (reference: Zendesk ticket 19811)api_definition.definition.enabled
should not be used for Classic APIs, this should either be omitted from the document, or should be marked as "not applicable"