Feature Requests

I would like to see a place on the UI where I can track my API usage

For legal document signing, many countries are now approved in the use of Adobe Acrobat Sign as their gold standard for e-signing tool. Industries such as legal, real estate and accounting are now using Adobe Acrobat Sign for the documents signing such as Leases, Contracts of Sale, and Tax Returns. It is not practical, nor legal, to use another tool such as Smartsuite Form to collect signatures for these kinds of legal documents. However, there is a real need to improve the efficiency of transferring the information filled in legal documents (such as names and contact details) into a database such as Smartsuite in order to do further work. Currently, most databases are not supporting this integration, and people are still manually retyping this information into their system once collected the form. From what I observed, Airtable, Slack and Typeform have all produced API's for Adobe Acrobat Sign and integrate through Make.com . To what extend they integrate to? I do not know. I have not tried using these other products. However, I think it would be absolutely amazing if Smartsuite could have this capability ....... one day!

Allow us to define the 'slug' field during the initial creation of new fields. Currently, comprehending the JSON returned when retrieving records with numerous fields can be challenging, as it displays auto-generated slugs containing random characters. If we can set the slug ourselves and mandate its uniqueness, it will enhance the readability of HTTP responses, thereby simplifying their utilization.

Instead of needing to make an additional API call to the Get File URL endpoint, it would be great if any API calls that return records would immediately contain the URL of the file

It would be nice to have an easier way to get the workspace id versus having to copy it from a URL. My suggestion would be to put it in the workspace settings.

I've created a Make API to handle a data dump of backups, based on this: https://community.smartsuite.com/developer-hub-u5l41n7u/post/how-to-create-a-smartsuite-backup-scenario-in-make-com-EouUcEmF1DHNNAe However, the larger the table data, it times out for each Table that takes over a minute. I tried it as part of the URL string, as in: https://app.smartsuite.com/api/v1/applications/{{19.id}}/records/generate_csv?limit=1000 The link above doesn't succesfully pass on the ?limit-1000 to generate_csv, so I cannot use make to cycle through the data because I cannot reduce the size of the data. Noting I did separately implemented the backup on the solution level, but that doesn't export data as text like a cvs does, so with a CVS that gets too big and thus does a timeout, there isn't a way to use the backup for tables when the export has too many records yet cannot limit each loop to 1000 records. @Peter Novosel recommended I create this as a request. As I'm certain that most users don't use API's or will run into the need for data backups, this post is really for tracking purposes more than a feature which any casual user will upvote!

When I am using the API to pull data from my solution's tables, it appears that all of the fields I've added to the table are available, but instead of field names it references them using an abstract ID. Airtable has a similar set of APIs, but theirs allows the API client to key either by ID or by name. That makes their API a little easier to use.

Currently, when making a GET call to a table, while we can sort or filter, all fields are pulled when we only need a certain subset of fields, especially for our larger tables that have an extraordinary number of fields. Our current workaround is to create a secondary table with only the fields we need for the API call, which then must be synced with the primary table (i.e., when a new record is created in the primary/master table, that record must also be created in the secondary table, adding an additional layer of table links). Rather than create a secondary table, we'd like to be able to make the call to a specific view of a table so that only specific fields are pulled during the API call. Happy to further expand if you need more details.

Something similar to this > https://airtable.com/marketplace/blkJ16czOGRAFvBFg/baseql

It would be super useful if linked fields would also hydrate or be displayed with their names in the API. Alternatively an easy way to find or display the field id's would also help.