Handle two versions #16
Description
This is pretty important and the largest open ticket I believe.
We have to refactor the site somewhat so users can pick between which version of the API they want to use. We also have to label V3 as "beta" so that its API is not locked in yet (too early for us).
The main source of this issue is that /subscriptions cannot be viewed as both versions at once. So in order to support docs for both new and old we have to make our site capable of swapping docs based on version.
A massive short-cut to this would be documenting only V3 and linking V2 users to a legacy route that has the old docs.