I’ve just tried a POST to that api and I get a 502 “bad gateway” error. If I do a GET I get the same 403 error. Is there documentation for this API?
Hi @rico.trevisan. Thanks for answering.
Be sure you are using a POST method and use the Body I updated above. and don’t forget the header Content-Type : application/json
Try again and let me know.
No documentation, this is a custom API developed on AWS that works pretty well on Insomnia.
It is important to add that when using the API connector and making a call, I do see the call received in the API side (as I am the owner and admin) and the good answer sent back to Bubble, but it seems Bubble can not parse it or there is a security control validation under the hood that throw the 403 error. Is this a wanted behaviour @emmanuel ? Thanks for answering.
It looks like AWS requires authorization when you are calling it from the Bubble side.
Did you try to generate and use a simple x-api-key? You shouldn’t have issues in that case.
I will try but when using a “none or self-handled” authentication, I am supposed to be able to call my API and get the answer. That said, I see the call request and the call answer in Cloud watch on AWS as normal, without errors. So, it seems to be a Bubble side limitation.
Yup. It looks like an issue caused by the Bubble.
Please submit a bug report with the step-by-step instructions.
Also, don’t forget to attach this screenshot.
Finally, we managed by avoiding the 301 redirect response from API service. It seems that Bubble does not support this behavior. We change it for a 200 response and that worked!. It could be helpful if this could be the answer instead of “Missing Authentication Token”, which is not the case.