API Responses how to capture (200,400 codes)

Hey guys,
i need some help in capturing the API responses so i save them in a table that stores a list of API calls made. Does anyone know if this is even available?

This will be helpful in a dash-panel i am building that shows errors in API calls for the user to fix


Ya this needs a bump up if we ever decide to start handling errors right!


Agreed. This request has come up in a few other threads also.

bump up bump up bump up I need this feature

1 Like

Bump – is there a way to capture 400 / 500 errors from an API?

1 Like

any update? how to handle error with status code.
i want to change when error with code 3003, i want to show alert message.

@AliFarahat have you found the answer?

backendless docs

1 Like

Just use when unhandled error occurs in your workflow.

I’ve tried the @romanmg method but it can’t be used to API connector


Then that feauture should be suggested in the idea section

Ya it’s not possible to accurately handle this from our end. Only Bubble can add this error handling. Try to catch all errors with the workflows. If that does not work then you need to rethink your approach

1 Like

I think if you contact the owners they will add it.

Has anyone found a way to capture error codes from API connector?

Nope! which is a bummer. Error handling is the next biggest challenge in Bubble. That includes Front-end and Back-end errors :frowning_face:


Bump - this is still a feature gap that needs filling

1 Like

Just a reminder: people need this @eve @emmanuel @josh !!

Yup. We do.

You can do it in a plugin but that is not ideal.


Definitely need this

Are you saying the the API calls in the plugin allow for different error response handling? Or just doing your own GET requests in the plugin code?

+100 for this. I’m getting pretty crafty with workarounds, but it would be really nice to have a backend trigger option for 400 codes. They’re getting picked up in the server logs, so having access to that within a workflow would be :ok_hand:


I wonder if we add more comments to this post if it will move it further up the roadmap as its been in here since 2016 :slight_smile: