Hello guys i solved it asking chat gpt , literally in the shared headers of your api , add “Content-type” and the value you see on the screen (which is the same you get when you´re shown the error" , i made my calls again , and working as normal , so perhaps the bubble team messed up the content-type , they used to handle it for us and now they are no longer doing it
You are supposed to have Content-Type set to application/x-www-form-urlencoded. That’s just normal. Having that doesn’t affect the bug. In fact, your headers should look like this for stripe ( using a test token):
BUT… maybe deleting the call and starting a new one over entirely would help if they have fixed it which I will try next since mine is still returning errors from Stripe (even though 6 other ones that were initialized before work just fine and this one works fine in Postman.)
I just started paying for Bubble too, which sucks. Why is it taking them this long to fix this??
For what it’s worth to provide more info for any Bubble people debugging, I was calling the Anthropic API. It was using a shared content type header set to application/json and wouldn’t work despite being formatted correctly.
1 Like
Please double check your configuration of the API in the Bubble API connecter.
And I think it’s really important to note that the identical configurations work just fine in Postman. Have you verified this too with the Anthropic API?
Were there any querystrings in the api call? My initialisation was failing only on those with Post requests and querystrings for what its worth.
But its working today (fingers 
)
I deleted the call that wouldn’t initialize and created a brand new call with the same settings. It now works for me too.