Can Bubble backend workflows return non-200 HTTP status codes?

[jules3]

Hi everyone,

I’m using Bubble’s backend workflows to handle some API requests, and I noticed that the response always comes back with a 200 OK status, even when I want to indicate an error (like a 400 or 401).

Is there a way to change the HTTP status code returned by a backend workflow?
Ideally, I’d like to return proper error codes depending on the situation, instead of just sending an error message in the response body.

Has anyone found a workaround for this, or is this simply not possible in Bubble?

Thanks!

[ademiguel]

Last time I investigated this topic, it wasn’t possible. And I believe it isn’t still.

I recall I ended up setting Xano in the middle, acting as a proxy between my Bubble app and the third-party service, to be able to return the code I needed. A bit convoluted.

Why can't bubble return a custom HTTP status code in API workflows, only 200 (success)?

I’ve been using bubble.io for years, and so far, it’s still not possible to edit the headers of the APIs we create. I wish Bubble would focus more on supporting the API builders on the platform or something similar. I understand that this feature might not be easy to implement (which could explain the long delay), but it’s essential for API construction. For instance, if I want to return an error message today, I can indicate “error” in the request body, but it always ends up with a “200 (succes…

Custom response API workflow

Hi everyone. I’m creating a API Endpoint with backend workflows but I need to do some validations and return which was expected. For example: I’ve built an endpoint that creates new things in my database, however it needs to be validated if this new created thing have a field equals to another already created. Basically if it was a user, would need to validated if there was another user created with that e-mail, and return a custom http code (409 for example) and a message from the server “that…

Modify HTTP Status Response Code

Hey guys, I’m trying to integrate appsumo into bubble. I have created an API workflow that receives data from appsumo and processes it according to action defined in the API Call by appsumo. App sumo wants me to return a different HTTP Status for each kind of action but bubble always returns a “200 OK” status. Is there any way I can change this HTTP Status dynamically or any alternative solution for this?

[jules3]

Guess I’ll just throw in something like: real_code: 401;
Thanks for the info

[austin3]

Technically yes. They will throw an error status code (I can’t remember exactly which one) if the workflow condition isn’t met. Sadly other than that, no.

One way I’ve gotten around this (although it’s a bit wonky) is to have the condition make an API call (via the API connector) to another API workflow. In the second workflow, return the success/failure as a field, and use that field as the condition for the first workflow.

[ademiguel]

I definitively have to try this out.