# Cannot set API header for Content-Type

**URL:** <https://community.thunkable.com/t/cannot-set-api-header-for-content-type/2460425>\
**Category:** Web API's\
**Created:** [June 10, 2023, 11:23pm UTC](https://community.thunkable.com/t/cannot-set-api-header-for-content-type/2460425 "2023-06-10T23:23:09Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![royrosemarin](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@royrosemarin](https://community.thunkable.com/u/royrosemarin)\
**Post date:** [June 11, 2023, 12:13pm UTC](https://community.thunkable.com/t/cannot-set-api-header-for-content-type/2460425/6 "2023-06-11T12:13:18Z")

</div>

OK, I was reading few old posts about flask deployment, and I could see that other users had bugs when testing on the web version of Thunkable (here for example: [[Solved] how can I fix a 403 error using the WEB API - #9 by muneer](https://community.thunkable.com/t/solved-how-can-i-fix-a-403-error-using-the-web-api/2007685/9)). So, I moved to test on my mobile (Android Samsung, but in the post I referenced they also report that it worked on Iphone), and surprisingly - it worked great when I tested on Thunkable mobile app. So, in conclusion, seems like there is a problem when testing/calling API requests as web app. For now, I will call it solved, although I would appreciate if you could help us find a solution to test it also on the web.

---

_[View the full topic](https://community.thunkable.com/t/cannot-set-api-header-for-content-type/2460425)._