SnozeDevelopers
API referenceDatabases

Delete a view

Checks the view's deletion impact first and refuses while blocking dependencies remain, or when the impact carries warnings and `confirmed` is not truthy; otherwise the view is removed. Deleting a shared view requires the `views:write` permission and a locked view is reserved to workspace owners and admins, while a personal view can be removed by its owner.

DELETE
/v1/workspaces/{workspaceId}/databases/{databaseId}/views/{viewId}

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

workspaceId*string
databaseId*string
viewId*string

Query Parameters

confirmed?string|null

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X DELETE 'https://api.snoze.dev/v1/workspaces/string/databases/string/views/string'
Example Response
{  "data": {    "id": "string",    "workspaceId": "string",    "databaseId": "string",    "key": "string",    "label": "string",    "kind": "table",    "placement": "database",    "manifest": {},    "relationFieldId": "string",    "ownerUserId": "string",    "scope": "shared",    "locked": true,    "definitionVersion": 0,    "createdAt": "string",    "updatedAt": "string"  }}

Update a view's definition

Applies a change to the view's label, kind, manifest, scope, placement or source database. `expectedVersion` must match the view's current `definitionVersion`, so a stale edit is rejected as a conflict rather than overwriting a concurrent one. Editing a shared view needs the `views:write` permission, changing its placement also needs `resources:write`, and locking a view is reserved to workspace owners and admins.

Preview what deleting a view would affect

Returns the blocks, automations and other references that depend on the view, with an overall status of `safe`, `needs_confirmation`, or `blocked`. Read-only. Requires the `databases:write` permission.