Status of Versioning - What's the silver bullet?

1

As can be found in the thread over at Clarify the versioning strategy for APIs, this is a highly controversial discussed topic and went on for over a year with no clarity in sight.

Actually, the only confusing part of JSON:API for us was to see that there’s not even a suggestion about versioning, but instead a rather surprisingly “rich” thread about it, and yet no resolution. :upside_down_face:

We went for the double accept header like

Accept: application/vnd.api+json;
Accept: application/vnd.api+json; version=1.0

By my experience that’s accepted as by the specs by any implementation of JSON:API so far. :hugs:

I would like to know if this topic is currently officially addressed internally for a future specification or at least recommendation.

2

While this thread is rather old, my read of this is that it’s out of scope for the spec itself, and the related RFCs regarding content-type negotiation allow you to specify an extension for version if you like. As newer versions of JSON:API have a backwards-compatibility promise, I don’t think this is necessarily something that the spec needs to address. IMO.

1 Like