Benefit of Constraints in API Call vs Filtering API Call results

If I am making a GET call what would be the benefit of using constraints in my API call compared to just using the filter operators?

I’ve set up a GET call to use dynamic constraints from a set of inputs on the page and it is working fine. But what would be the benefit of doing that rather than just filtering the GET call response data using filter operators.

I personally can only see benefits to using the filter operators as I’d be able to use the GET call to return all values which can be stored on the page in a list and then just use the filter operators to filter those results rather than having new API calls initiated if I were to be using the constraints in the GET call.

If you need to get all the results initially, It’s better to use :filtering. But if you don’t, it’s better to use constraints to reduce the payload get by Bubble.

Is there a way to bypass the limit of 100 items to return all items on a GET call?

To which API?

API on Bubble app. Right now I am just testing out stuff and have two Bubble Apps that I am using.

I think you should have a look at App Connector maybe. Not sure if the limit is different.
But for Bubble Data API, the limit is 100 item you can get.

@boston85719 Could you just make a post request to one of your backend workflow endpoints and use the “Return data from API” action?

I’m not sure how that would work. I am actually just now starting to try and set up a POST call from APP 1 to a backend workflow endpoint in APP 2 to try and create data in the DB of APP 2.

I’ll have to investigate how the Return Data from API would work once I can sort through how to do the POST for data creation.

@boston85719 Hope this helps! Loom | Free Screen & Video Recording Software

Thanks @jacobgershkovich

I appreciate the video. I’m a bit confused on what the use of the second step to return the results is for.

My assumption is that if I have APP 1 setup with a backend workflow to ‘create a new person’ and APP 2 uses an API POST to send data which will then be used in APP 1 to create data in it’s DB using the backend workflow, that the second step of ‘return data from api’ would basically send a response to APP 2 which could be used to make an alert that the data had been created in APP 1 successfully.

My goal right now is to lay down a foundational understanding of how the API calls as well as the API endpoints will allow me to have an application (3rd party) send data to my Bubble app to create entries in my Bubble apps database.

My current stage in this is that I have an backend api endpoint created in APP 1

which I used the reference to get a grip on how things should be set up, and in doing so used the ‘Detect Data’ button to get the parameters being sent from APP 2 which uses a POST call to send data from a RG on the page to APP 1

This has been successful, except one issue I am going to try and sort through, is that my DB entry in APP 1 comes back with list of things in a single database entry rather than several entries containing single items

What is strange as well, is that admin-name field has a list, while name is empty and no other fields have lists and instead are single entries of the first Repeating Groups entry from APP 2.

I was hoping to do a ‘bulk upload via API’ with this setup.