Leave a Reply

Your email address will not be published. Required fields are marked *

5 Comments

  1. I might suggest leaving /v2/ active for a period of time that allows downstream clients to make the requisite changes in their workflows, and migrate to /v3/. 6 months is common, 9 days is a little rough. Is it different in publishing workflows? Otherwise, great use of semver, and putting version number in the URI.

      1. Hi Zach, I checked with the tech team and the redirects for back-compatible routes will stay in place, yes. Unfortunately, we can’t maintain a back-compatible version of the applications API, because posts to the v2 API without the oa_start date will be invalid from the moment the code gets deployed