Auth token must be marked legacy to use the legacy (v3) API

Previously an authentication token with a date-based default version could be used to access the Legacy (v3) API. Now this is no longer possible. Attempting to access the Legacy (v3) API with a token that uses a date-based version will return a 404 error with a specific message about the token’s version.

See the previous changelog entry deprecation warning for more info.

    Changed
  • Auth token must be marked legacy to use the legacy (v3) API