# Is it ok to specify post/patch requests with meta information?

**URL:** <https://discuss.jsonapi.org/t/is-it-ok-to-specify-post-patch-requests-with-meta-information/2089>\
**Category:** Uncategorized\
**Created:** [November 22, 2020, 9:16pm UTC](https://discuss.jsonapi.org/t/is-it-ok-to-specify-post-patch-requests-with-meta-information/2089 "2020-11-22T21:16:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Insolita](https://avatars.discourse-cdn.com/v4/letter/i/ba8739/32.png) [@Insolita](https://discuss.jsonapi.org/u/Insolita)\
**Post date:** [November 22, 2020, 9:16pm UTC](https://discuss.jsonapi.org/t/is-it-ok-to-specify-post-patch-requests-with-meta-information/2089/1 "2020-11-22T21:16:42Z")

</div>

Please, clarify for me:  
The spec declare that:

> document **MUST** contain at least one of the following top-level members:
> 
> - `data` : the document’s “primary data”
> - `errors` : an array of [error objects]
> - `meta` : a [meta object] that contains non-standard meta-information.

I don’t found any mentions that it is only for responses.

> Creating Resources  
> The request **MUST** include a single [resource object] as primary data. The [resource object] **MUST** contain at least a `type` member.

These lines don’t say that request must contain only a single resource object

So is it will be ok to allow send some meta for post/patch requests?

```auto
POST /photos HTTP/1.1
Content-Type: application/vnd.api+json
Accept: application/vnd.api+json

{
  "data": {
    "type": "photos",
    "attributes": {
      "title": "Ember Hamster",
      "src": "http://example.com/images/productivity.png"
    },
    "meta": {
       "transform": false,
       "makeThumb: true
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![fdrake](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/fdrake/32/654_2.png) [@fdrake](https://discuss.jsonapi.org/u/fdrake)\
**Post date:** [November 23, 2020, 10:43pm UTC](https://discuss.jsonapi.org/t/is-it-ok-to-specify-post-patch-requests-with-meta-information/2089/2 "2020-11-23T22:43:51Z")

</div>

The example **meta** structure you present is part of the resource object, not a top-level **meta** object.

I haven’t seen anything in the specification that prevents a PATCH or POST request from including either a top-level or resource-level **meta** portion.

-Fred