Optimize API endpoints.#475
Closed
lye wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Over the years the API has been a growing success, as indicated by the following chart which measures popularity over time:
But with success comes change and I'm proud to announce that starting this Sunday, April 2, 2017 at 6PM PST (I'll VPN in), the API is transitioning all endpoints to optimized versions. We expect these new endpoints to solve our popularity problem via both being more compact and wildly easy to use. Application developers now can connect to the API using up to an order of magnitude fewer keystrokes, which we consider a massive win.
As noted, this is a breaking change. The
/v2path will be turned off in favor of/✌️.It should be noted that not all endpoints yet have a transition plan; these will be removed as they were found to be unnecessary (and or we couldn't come up with suitable emoji for them). Suggestions on that front are welcome!
You can preview how the new and improved API will look by following this url.