Delete Saved View

Permanently delete a saved view from a Blue workspace and clear any default-view references that pointed to it.

Use the deleteSavedView mutation to permanently remove a saved view from a workspace. Saved views are SavedView objects in the API. Before the view is deleted, Blue clears every default-view reference that pointed to it — both the workspace default (Project.defaultViewId) and every user’s personal default (ProjectUser.defaultViewId) — so no record layout is left pointing at a missing view.

Deleting a view publishes a real-time DELETED event to anyone subscribed to the workspace’s views (see Related). This action is permanent and cannot be undone.

Request

mutation DeleteSavedView {
  deleteSavedView(id: "view_123") {
    success
    operationId
  }
}

Send the request to https://api.blue.app/graphql with your authentication headers:

curl https://api.blue.app/graphql \
  -H "Content-Type: application/json" \
  -H "blue-token-id: YOUR_TOKEN_ID" \
  -H "blue-token-secret: YOUR_TOKEN_SECRET" \
  -H "blue-org-id: YOUR_ORG_ID" \
  -d '{"query":"mutation { deleteSavedView(id: \"view_123\") { success operationId } }"}'

Header names are case-insensitive.

Parameters

ParameterTypeRequiredDescription
idString!YesID of the SavedView to delete.

Response

{
  "data": {
    "deleteSavedView": {
      "success": true,
      "operationId": "clm4n8qwx000008l0g4oxdqn7"
    }
  }
}

Returns

deleteSavedView returns a MutationResult.

FieldTypeDescription
successBoolean!true when the view was deleted. false when deletion failed after authorization (see the note below).
operationIdStringIdentifier for this mutation. Use it to correlate the resulting real-time event on the subscribeToSavedView subscription so a client that triggered the delete can skip re-applying its own update.
Always check success

Permission and lookup failures (SAVED_VIEW_NOT_FOUND, FORBIDDEN) are thrown as GraphQL errors before any deletion is attempted. But if the delete itself fails after authorization succeeds — for example a database error while clearing default references — the mutation returns { "success": false } instead of an error. Treat success: false as a real outcome and check it on every call; do not assume a missing errors array means the view is gone.

Errors

CodeWhen
SAVED_VIEW_NOT_FOUNDNo view with that id exists in a workspace you can access. Message: Saved view was not found.
FORBIDDENYou are not allowed to delete this view (see Permissions). Message: You are not authorized.
{
  "errors": [
    {
      "message": "You are not authorized.",
      "extensions": { "code": "FORBIDDEN" }
    }
  ]
}

Permissions

Who may delete a view depends on whether it is shared and who created it:

ViewWho can delete
Personal view you createdYou only
Shared view you createdYou, or any workspace OWNER/ADMIN
Shared view created by someone elseWorkspace OWNER/ADMIN only
Personal view created by someone elseNobody — even an OWNER/ADMIN cannot delete another member’s personal view

A workspace admin’s elevated rights apply to shared views only. A personal (non-shared) view can be deleted exclusively by its creator. Attempting to delete a view you may not modify raises FORBIDDEN; if you cannot see the view’s workspace at all, the API returns SAVED_VIEW_NOT_FOUND so the view’s existence is not leaked.