Saved Views

A saved view captures how a workspace is displayed: the layout (board, table, calendar, timeline, or map), plus the filters, sorting, grouping, and column settings applied on top of it. Members switch between views to see the same records through different lenses without re-configuring anything. In the API a saved view is a SavedView object, and it belongs to a workspace (Project).

Views are either personal (visible only to the member who created them) or shared (visible to everyone in the workspace). Any workspace member can create personal views; only OWNER and ADMIN members can create shared ones. The layout details live in the free-form viewConfig JSON, which the server validates against a fixed schema before storing.

POST https://api.blue.cc/graphql
X-Bloo-Token-ID: YOUR_TOKEN_ID
X-Bloo-Token-Secret: YOUR_TOKEN_SECRET
X-Bloo-Company-ID: YOUR_COMPANY_ID
X-Bloo-Project-ID: project_123

The X-Bloo-Project-ID header scopes requests to one workspace. Company and project headers accept either an ID or a slug. Header names are case-insensitive.

Operations

Three more mutations round out the surface but don’t have dedicated pages:

Create a saved view

Use the createSavedView mutation to add a view to a workspace. The minimum is a name, a viewType, and a viewConfig object (which may be empty, {}). Everything else - an icon and whether the view is shared - is optional.

Request

The smallest call creates a personal board view with no extra configuration. An empty viewConfig: {} is valid; the layout falls back to defaults.

mutation CreateSavedView {
  createSavedView(
    input: { projectId: "project_123", name: "My Board", viewType: BOARD, viewConfig: {} }
  ) {
    id
    name
    viewType
    isShared
    position
  }
}

Parameters

CreateSavedViewInput

SavedViewType

Response

{
  "data": {
    "createSavedView": {
      "id": "clm4n8qwx000008l0g4oxdqn7",
      "name": "My Board",
      "viewType": "BOARD",
      "isShared": false,
      "position": 65535
    }
  }
}

Returns

The mutation returns the created SavedView.

Full example

A shared table view filtered to a tag, sorted by due date, grouped by a custom field, with two columns hidden.

mutation CreateSprintView {
  createSavedView(
    input: {
      projectId: "project_123"
      name: "Sprint Planning"
      icon: "layout-grid"
      isShared: true
      viewType: DATABASE
      viewConfig: {
        searchQuery: "launch"
        tagIds: ["tag_123"]
        tagMode: "or"
        sort: { type: "builtin", field: "duedAt", direction: "asc" }
        groupBy: { type: "customField", fieldId: "field_123" }
        hiddenColumns: ["field_456", "field_789"]
        pinnedColumns: { left: ["field_123"], right: [] }
      }
    }
  ) {
    id
    name
    icon
    viewType
    isShared
    position
    viewConfig
    createdBy {
      id
      fullName
    }
    project {
      id
      name
    }
    createdAt
  }
}

View configuration

viewConfig is a JSON object, but it is not free-form - the server validates it against a fixed schema and rejects unknown shapes. The whole object must serialize to under 50,000 bytes. Every key below is optional; an empty {} is valid and the layout uses defaults. Unrecognized keys are stored but ignored on read.

Filtering

Sorting

sort is a single object (not an array), with all three fields required:

Grouping

groupBy is an object with a required type:

Columns

Timeline

These keys apply when viewType is TIMELINE:

Errors

viewConfig validation failures are thrown as a plain ViewConfigValidationError, not an Apollo error, so the response carries no specific code (it surfaces as a generic server error). Validation rejects a viewConfig that isn’t an object, exceeds 50,000 bytes, a name that is empty or over 100 characters, an icon over 50 characters, or a malformed sort, groupBy, pinnedColumns, or timeline shape (see View configuration). The message describes the offending field, e.g. sort.direction must be 'asc' or 'desc'.

Permissions

• Personal views (isShared: false, the default): any workspace member may create one.
• Shared views (isShared: true): only members with the OWNER or ADMIN access level may create one. Others receive FORBIDDEN.

Positioning

New views are assigned a position of the last position in their scope plus 65535, or 65535 for the first view in that scope. Scope is per-workspace and split by sharing: a shared view is positioned after the last shared view; a personal view is positioned after the caller’s last personal view. Use updateSavedViewPosition to reorder afterward.

Related

• List saved views
• Update a saved view
• Delete a saved view
• Workspaces
• Custom fields