---
title: "Update View"
method: PUT
path: "/v2/view/{view_id}"
tags: ["Views"]
---

# Update View

`PUT /v2/view/{view_id}`

Rename a view, update the grouping, sorting, filters, columns, and settings of a view.

## Path parameters

- `view_id` string, required

## Request body

- object
  - `name` string, required
  - `type` string, required
  - `parent` object, required — The parent parameter specifies where the view is located in the ClickUp Hierarchy. Both `id` and `type` are required. \ \ The `id` is the id of the Workspace, Space, Folder, or List where the view is located. \ \ The `type` value indciates the level of the Hierarchy where the view is located.
    - `id` string, required — The id of the Workspace, Space, Folder, or List where the view is located.
    - `type` integer, required — The level of the Hierarchy where the view is created. \ \ Options include: \ \ Workspace (Everything Level): `7` \ \ Space: `4` \ \ Folder: `5` \ \ List: `6`
  - `grouping` object, required
    - `field` string, required — Set the field to group by.\ \ Options include: `none`, `status`, `priority`, `assignee`, `tag`, or `dueDate`.
    - `dir` integer, required — Set a group sort order using `1` or `-1`.\ \ For example, use `1`show tasks with urgent priority at the top of your view, and tasks with no priority at the bottom.\ \ Use `-1` to reverse the order to show tasks with no priority at the top of your view.
    - `collapsed` string[], required
    - `ignore` boolean, required
  - `divide` object, required
    - `field` unknown
    - `dir` unknown
    - `collapsed` string[], required
  - `sorting` object, required
    - `fields` string[], required — Include an array of fields to sort by.\ \ You can sort by the same fields available when [filtering a view](https://developer.clickup.com/docs/filter-views).
  - `filters` object, required
    - `op` string, required — The available operator (`op``) values are `AND`` and `OR``.
    - `fields` string[], required — View the list of [fields available](https://developer.clickup.com/docs/filter-views) to filter by.
    - `search` string, required
    - `show_closed` boolean, required
  - `columns` object, required — Custom Fields added to a view at the Everything level will be added to all tasks in your Workspace. Once Custom Fields are added to one of these views, you cannot move it to another level of the Hierarchy.
    - `fields` string[], required — Custom Fields require the `cf_` prefix and must be formatted as a JSON object. Example: `cf_eb1234567890-c676-4c10-9012-345678901234`
  - `team_sidebar` object, required
    - `assignees` string[], required
    - `assigned_comments` boolean, required
    - `unassigned_tasks` boolean, required
  - `settings` object, required
    - `show_task_locations` boolean, required
    - `show_subtasks` integer, required — Acceptable values are `1`, `2`, or `3`, which show subtasks separate, expanded, or collapsed.
    - `show_subtask_parent_names` boolean, required
    - `show_closed_subtasks` boolean, required
    - `show_assignees` boolean, required
    - `show_images` boolean, required
    - `collapse_empty_columns` string, nullable, required
    - `me_comments` boolean, required
    - `me_subtasks` boolean, required
    - `me_checklists` boolean, required

## Response `200`

- object
  - `view` unknown, required

---

[API](https://skmtc.net/clickup/apis/clickup-api-v2-reference.md) · [All operations](https://skmtc.net/clickup/apis/clickup-api-v2-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/clickup/clickup-api-v2-reference/revisions/72216f55b952/schema)