# JSON:API and versioning our APIs

**URL:** <https://discuss.jsonapi.org/t/json-api-and-versioning-our-apis/1714>\
**Category:** Uncategorized\
**Created:** [October 7, 2019, 5:15pm UTC](https://discuss.jsonapi.org/t/json-api-and-versioning-our-apis/1714 "2019-10-07T17:15:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![yoelspotts](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/yoelspotts/32/636_2.png) [@yoelspotts](https://discuss.jsonapi.org/u/yoelspotts)\
**Post date:** [October 7, 2019, 5:15pm UTC](https://discuss.jsonapi.org/t/json-api-and-versioning-our-apis/1714/1 "2019-10-07T17:15:29Z")

</div>

I’m getting my feet wet with JSON:API.

An immediate question I have is that in the past, I have found versioning our APIs via media types to be a superior strategy. We have done so with either media type parameters or a specific media type.

However, I notice that the JSON:API spec prohibits including any media type parameters in the request and response.

Is there any way square these two?