News for hackers. Stuff that matters.
Re:How to Version an API by faitswulff on Thursday June 08, 2017 @06:55PM (#14517813)
Random thought, but would it make sense to give each client a unique base path for URL endpoints and let them instantiate new endpoints with different versions?

Ex:

    mysite.com/api/UUID_for_api_v1/cars/1
and

    mysite.com/api/UUID_for_api_v2/automobiles/1
Re:How to Version an API by caffeinewriter on Thursday June 08, 2017 @07:05PM (#14517877)
I was just thinking about this. Instead of versioning with an `Accept` header, or with a URL version, why not version off of an upgradable API key?
Re:How to Version an API by TimWolla on Thursday June 08, 2017 @07:29PM (#14518005)
Facebook does this partly: Each “Application” has an associated API version which is the earliest API version that can be accessed (and IIRC the one used implicitly when no version is given inside the route).