# Content-type requirements has vague wording

**URL:** <https://discuss.jsonapi.org/t/content-type-requirements-has-vague-wording/945>\
**Category:** Uncategorized\
**Created:** [April 3, 2017, 9:39pm UTC](https://discuss.jsonapi.org/t/content-type-requirements-has-vague-wording/945 "2017-04-03T21:39:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lgh](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/lgh/32/391_2.png) [@lgh](https://discuss.jsonapi.org/u/lgh)\
**Post date:** [April 3, 2017, 9:39pm UTC](https://discuss.jsonapi.org/t/content-type-requirements-has-vague-wording/945/1 "2017-04-03T21:39:54Z")

</div>

The wording in the “Content Negotiation” section of the documentation seems vague to me. I feel that I know what it means, but I want to clarify and if anyone agrees that it’s vague I may open a pull request.

Under “Client Responsibilities” it reads:

> Clients MUST send all JSON API data in request documents with the header Content-Type: application/vnd.api+json without any media type parameters.

This could mean two distinct things. The first is that it could mean that all requests MUST have the Content-Type application/vnd.api+json and also MUST NOT have media type parameters. The other meaning is that any request THAT HAVE the Content-Type application/vnd.api+json MUST ALSO NOT HAVE media type parameters.

I assume it means the first, but it is very easy to intemperate the meaning as the second. There are a few places where unclear statements such as this are made.

Am I correct in the interpretation? Should it be rewritten to be more clear?

---

<div class="post-metadata">

**Author:** ![michaelhibay](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/michaelhibay/32/405_2.png) [@michaelhibay](https://discuss.jsonapi.org/u/michaelhibay)\
**Post date:** [April 4, 2017, 8:39pm UTC](https://discuss.jsonapi.org/t/content-type-requirements-has-vague-wording/945/2 "2017-04-04T20:39:58Z")

</div>

I’m not seeing any difference with your distinction. JsonAPI requests must be application/vnd.api+json with no additional mediatype parameters e.g. version in “application/vnd.api+json;version=1.1”.

Your question is worded as an identity function, and I don’t see where the misunderstanding of any distinction between the two statements stems. All requests to the JsonAPI specification service are required to be in this format.