Full API and MCP support for Templates, Collection, Views and Widgets

WHAT DO YOU RECOMMEND?

Define a specific feature that is missing or could be improved:

While exploring the API, I noticed that some workspace features are fully manageable programmatically, while others appear to be only partially exposed or not exposed at all.

From what I can see:

  • Templates: the API currently exposes List templates and Get template, but there are no endpoints to create, update, or delete templates. I also noticed a recent feature request asking for template CRUD support, which received a “Thanks for the suggestion” response, but I couldn’t find any indication that this limitation is intentional.

  • Collections: the API allows adding/removing objects from existing collections and reading their content and views. However, it doesn’t seem possible to create a collection or fully configure its structure programmatically.

  • Views: existing views can be read, but I couldn’t find public endpoints to create, rename, or configure views (filters, sorting, visible properties, layout, etc.).

  • Sidebar widgets: I couldn’t find any public API for creating or managing workspace widgets.

HOW COULD IT BE DONE?

á…źDetail the solution you would like to get what you need:

Just add all features

REAL WORLD USE CASES

Describe how this feature would be used, and why it should be implemented. (Demo images are very helpful)

These capabilities would make a huge difference for AI agents and automation. Today an agent can populate an existing workspace, but it cannot fully build or configure one from scratch.

RECOMMENDED ALTERNATIVES

á…źExplain any workaround or feature you may have considered:

ADDITIONAL CONTEXT

á…źIf further context, people, or related Feature Requests should be mentioned, do so right here:

Yes, we’re working heavily on the API to improve it and are aware of the various limitations. Nonetheless, thanks for letting us know.