Feature Requests

Tables and solutions created through the SmartSuite API can now start clean. The Create Table endpoint accepts a new create_default_fields flag: set it to false and the table is created without the five default fields (Status, Priority, Due Date, Assigned To and Description), holding only the system fields plus whatever structure you send. The Create Solution endpoint's create_default_application flag does the same one level up, creating a solution with no placeholder "Table 1". Integrations, provisioning scripts and AI agents that define their own structure no longer have to find and delete defaults they never asked for, and any request that omits either flag behaves exactly as it does today. Available on all plans.

"...ability to generate namespaced api keys with certain permissions for app creation..." Order of importance: Rate limit factor Security Management As an app creator having API keys assigned at the user level w/ rate limiting can be challenging to manage for security (rotation/isolation) and stability on external apps. Having the ability to generate namespaced api keys with certain permissions for app creation would speed up development of apps and provide better stability/maintenance/security of the apps. Some Examples: Single admin uses their key for multiple apps and resets api keys and forgets all the places impacted Single admin does same as above yet hits rate limit. Using a users api key on backend for a website that has client-side form submission in a web app could cause important information to be lost due to rate limiting and accidental key rotation.

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

I recommend updating the help article to include details on configuring SmartSuite AI with our own OpenAI API key. This would be helpful for other members who might have the same question.

Problem: Records have to be explicitly saved every time before clicking a button that uses information from the record. Often users can forget to do this, with unintended results. Solution: Adding an option to "Save Record, then Open Link" to the button field would solve this issue. If anyone has an idea on how to do this with the current option please let me know at this community post: https://community.smartsuite.com/developer-hub-u5l41n7u/post/saving-records-before-clicking-buttons-hDQvcTLzUHF53NA