# Trouble Using WhisperAPI **URL:** \ **Category:** Web API's\ **Tags:** beginner\ **Created:** [January 25, 2023, 10:57pm UTC](https://community.thunkable.com/t/trouble-using-whisperapi/2241275 "2023-01-25T22:57:42Z")\ **Posts on this page:** 1\ **Showing post:** 29
**Author:** ![nathanburley21656](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/nathanburley21656/32/150307_2.png) [@nathanburley21656](https://community.thunkable.com/u/nathanburley21656)\ **Post date:** [January 30, 2023, 7:34pm UTC](https://community.thunkable.com/t/trouble-using-whisperapi/2241275/29 "2023-01-30T19:34:32Z")
OK - so I was pretty sure Authorization through config was working because when I get this wrong I get the error {“detail”:“Not authenticated”}. But, I was worried the Content-Type was playing a part. If I just added a ‘Set WhisperAPI Header to’ for Content-Type it seems to nullify the config API-key setting. So, I tried your way and set them both via the blocks. Sadly, that still gives me an authentication error. Here’s what I ran: ![Thunk18](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/b/9/b97909f94ee4bf9bb0c5ad29ad911bba8a4b6019.jpeg) Note - I added an additional button to just run a pre-created url instead of spamming Cloudinary with new files all the time. I also tried removing the block to add the data sub-property but that gives me the normal ‘url not set’ error. Finally, I also tried the 2 \> “2” (good shout) but again, no dice. One thing which seems really obvious but might not be from the way I’m describing everything: The cURL from the POSTMAN which worked is completely different in terms of format from the thing I’m sending it. As in, the cURL features data encodes like this \> --data-urlencode ‘diarization=false’ The JSON I’m sending it is in key:variable pairs like {“diarization”:“false”}. Is it this? --- _[View the full topic](https://community.thunkable.com/t/trouble-using-whisperapi/2241275)._