# Json API response format for non-resource data, like oAuth token

**URL:** <https://discuss.jsonapi.org/t/json-api-response-format-for-non-resource-data-like-oauth-token/74>\
**Category:** Uncategorized\
**Created:** [July 28, 2015, 9:00pm UTC](https://discuss.jsonapi.org/t/json-api-response-format-for-non-resource-data-like-oauth-token/74 "2015-07-28T21:00:08Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![uberclops](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/uberclops/32/67_2.png) [@uberclops](https://discuss.jsonapi.org/u/uberclops)\
**Post date:** [September 14, 2015, 8:10am UTC](https://discuss.jsonapi.org/t/json-api-response-format-for-non-resource-data-like-oauth-token/74/7 "2015-09-14T08:10:43Z")

</div>

Is there specific reason you want to use JSON-API for the auth component of your app? For any authorization calls I generally use a standard JSON content-type since they don’t form any sort of domain object.

---

_[View the full topic](https://discuss.jsonapi.org/t/json-api-response-format-for-non-resource-data-like-oauth-token/74)._