# 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:** [Abril 19, 2016, 3:06am 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:** 10

<div class="post-metadata">

**Author:** ![citadelgrad](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/citadelgrad/32/121003_2.png) [@citadelgrad](https://meta.discourse.org/u/citadelgrad)\
**Post date:** [Maio 19, 2017, 8:33pm UTC](https://meta.discourse.org/t/put-requests-to-suspend-account-using-different-content-type-on-1-5/42789/10 "2017-05-19T20:33:44Z")

</div>

> [@blake](#):
>
> I personally just care that we return the correct status codes (which we do) so I don’t think this is really a bug.

I’ve done a fair amount of work over the years with Discourse’s API and it’s always felt really inconsistent. I’m not trying to be critical, but your attitude seems pretty dismissive of something that is clearly inconsistent. I detailed in the first post that all requests that I reviewed returned one way, and after the upgrade to 1.5.1 the API started returning a different content-type in this one particular case. You can chalk this up as not a big deal, but APIs being consistent and reliable is important. If you want to continue to have software that people want use and integrate with you should care about the details.

---

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