Version your API's

Hello,

I've been a user of a mobile app, MBooru, which recently broke, on inspection this appears to be because the URL formatting has changed in the API and the URL's are being constructed wrongly in the app.

Now, the creator of MBooru has not been active in a year or so and I can't see him being active any time soon so effectively this has broken the one way I enjoy using and left me with no good alternative which completely sucks.

Now, I'm a developer, and I would consider making a replacement for Mbooru, but what's the point in investing my time if you'll just break the API a year down the line? There becomes a need to supply support more often than is realistically available to a hobbyist developer.

So, my request to you is to version your API. All you do is take whatever the url the API is now, and put it under /v1/... and if you want to make a change in the future to your REST API that changes what is returned, you put this under /v2/ and most importantly you keep /v1/ running without any changes so that our app's don't break and we can update them when we get the time.

Thank you

~Roboko

Danbooru used to be versioned until the devs realized that the website software is more of a rolling release model and decided to switch to labeling each version of the software currently used by its git commit hash. I see what you mean though and I think versioning should be applied to the API to let third party developers know if anything has significantly changed.