Baserow may, from time to time, deprecate functionality in its REST and/or Websocket API. To ensure that your application runs smoothly, and without downtime, we will use this page to inform API integrators of what features are deprecated, and how long we’ll support compatibility for.
In early 2023 we decided to rename the concept of a “group” to “workspace”.
For nearly all users, the only noticeable change will be that within the UI, references to “group” will disappear in favor of “workspace”.
For API consumers, however, they will need to eventually migrate from our “group” endpoints to functionally identical “workspace” ones. To help API consumers migrate to the new endpoints, our API specification has been updated so that each deprecated “group” endpoint will suggest the functionally identical “workspace” equivalent.
The most significant change to our API is that we’ve duplicated all “group” endpoints so that there is a functionally identical “workspace” one.
In any API or WebSocket response which previously serialized a “group” ID, name or nested object, there will be an identical “workspace” one.
This means that there will be no intentional breaking changes in our API responses. There are, however, some codebase changes to be aware of.
baserow.api.groupshas been renamed to
baserow_premium.admin.groupshas been renamed to
fill_groupwas renamed to
import_group_applicationswas renamed to
export_group_applicationswas renamed to
groupID, name or nested object, will keep returning them. The only change to these responses will be the inclusion of an exact