I’ve started rolling out an API data source in my app, very slowly. It appears to be rough around the edges. One limitation in particular that I’ve wrestled with support on is the block’s inability to use “see more” or pagination for this type of data source.
I think pagination was a long shot, but the “see more” button should work and it doesn’t. Support said they’ll put it in the queue, but it sounded like that may not be a high priority.
Well, with API data sources, which are typically 3rd party large scale databases, this is actually even more important than with, say, Airtable, which would typically have a smaller dataset.
Until this is fixed, I would expect the browser to choke on the GET call if the call happens to bring back a large dataset and not able to lazy load or paginate somehow.
If there is any way prioritize this one, that would be great. Otherwise, API data source has a limited use case.
I was under the impression that REST w/ JWT token was generally considered a stronger security than SQL over a public IP with username/password. I see that Xano allows whitelisting incoming IPs, which may bump up the security of the Xano connector option to be similar to the API data source option. That’s assuming Softr could provide the IPs to whitelist in Xano.
If we can’t resolve the paging for an API data source, I might need to go with the other option. The question is, can we?
Hi Artur.
Just wanted to follow up on this. So, no pagination or see more button for a list on top of a rest api data source, correct? And no fix, correct?
If so, is the Xano connector the next best option I have? Does that option have a pagination or see more button?
Xano connector requires the Database Connector to be enabled in Xano. Xano recently changed their pricing and this connector is now priced separately at $29/mo. That’s another $348 a year I’d need to pay to Xano just to make Softr’s Xano connector work.