# PUT requests to Suspend account using different content-type on 1.5

**URL:** https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789
**Category:** Development
**Created:** [2016年四月19日 03:06 UTC](https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789 "2016-04-19T03:06:25Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2017年五月16日 21:44 UTC](https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789/8 "2017-05-16T21:44:07Z")

</div>

@eviltrout / @blake this is actually a bigger API problem:

1. Are we **strictly** a JSON API, meaning do we expect every single endpoint to always return `render json: success_json` vs `render nothing: true` ?

2. If not, should we always be strict about returning json if the request is made to a `.json` resource ? (which means we need a fancy helper for render success)

As to the OP, I think that is legit that a `PUT` to `/suspend.json` should return a JSON payload. But… just cause you send JSON encoded body does not imply that the server must return JSON.

There is an argument for returning 200 with blank body, you are sending an infinitesimally smaller amount of data and a tiny bit less work on the JS side.

I am leaning towards just going with (1) and making every single `PUT` and `POST` JSON by default, and all XHRs JSON by default.

---

_[View the full topic](https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789)._