POST/bases/views/update

Update a base view

Updates a view's name, type, configuration, or position on a base. Supply viewId and pageId, and include only the settings you want to change; config is merged with the stored configuration, with omitted keys preserved and keys set to null removed.

  • IdempotentThe SDK sends Idempotency-Key, so a retried request is only applied once.

6 body fields

The view to update and the settings to change. viewId and pageId are required; all other fields are optional.

configobjectoptional
A patch, not a replacement. Keys you omit keep their current value, keys you set are overwritten, and a key set to `null` is *removed* from the stored config.
namestringoptional
The new name for the view.
pageIdstringrequired
Id of the base. A base *is* a page, so this is the base's page id - the same id you would pass to the page endpoints.
positionstringoptional
The fractional index that places the view among its neighbours.
typestringoptional
The view type: `table`, `kanban`, or `calendar`.
Allowed:tablekanbancalendar
viewIdstringrequired
The UUID of the view to update.

4 status codes
200Returns the updated view object.
dataobjectoptional
statusintegeroptional
successbooleanoptional
400Returned when the request fails validation.
errorstringoptional
Reason phrase, for example `Bad Request`.
messagestringoptional
statusCodeintegeroptional
403Returned when access is forbidden or bases are not included in the current licence.
errorstringoptional
Reason phrase, for example `Bad Request`.
messagestringoptional
statusCodeintegeroptional
404Returned when the base is not found.
errorstringoptional
Reason phrase, for example `Bad Request`.
messagestringoptional
statusCodeintegeroptional

Error handling

A 400 is returned when the request fails validation. A 403 is returned when access is forbidden or bases are not included in the current licence, and a 404 is returned when the base is not found. viewId must be a UUID, pageId must be a UUID, and type, if supplied, must be table, kanban, or calendar.