Saved Views

Overview

Saved ticket views let users persist filter combinations for quick access. Views come in two flavors: personal (only visible to the creator) and workspace (visible to all members, admin required to create or modify).

List Saved Views

Returns all views accessible to the authenticated user.

GET /api/saved-views

Example Response

{
    "data": [
        {
            "id": 1,
            "ulid": "01hx9f3k2a...",
            "name": "My open tickets",
            "slug": "my-open-tickets",
            "icon": "inbox",
            "is_personal": true,
            "search": null,
            "statuses": ["open"],
            "assigned_to_me": true,
            "unassigned": false,
            "assigned_user_id": null,
            "channel_ids": [],
            "tag_ids": []
        }
    ]
}

Show Saved View

GET /api/saved-views/{savedTicketView}

Create Saved View

POST /api/saved-views

Request Body

Field	Type	Required	Description
`name`	string	Yes
`icon`	string	No
`is_personal`	boolean	No	Defaults to `true`. Pass `false` for a workspace view (admin).
`search`	string	No	Full-text search term
`statuses`	array	No	Array of status values
`assigned_to_me`	boolean	No
`unassigned`	boolean	No
`assigned_user_ulid`	string	No	ULID of the user the view should filter by
`channel_ulids`	array	No	ULIDs of channels to filter by
`tag_ulids`	array	No	ULIDs of tags to filter by

Channel and tag ULIDs from other workspaces are silently ignored.

Update Saved View

PUT /api/saved-views/{savedTicketView}

All fields optional. Omit a field to leave it unchanged.

Delete Saved View

DELETE /api/saved-views/{savedTicketView}

Personal views can only be deleted by their owner. Workspace views require admin role.