GuidesAPI DocsChangelogMy AppsSeismic Exchange
API Docs

Get saved views

get
https://api.seismic.com/programs/v2/spaces//savedViews

Retrieves a paginated list of saved view configurations within a specified space, returning all user-created and system-defined views that match the optional filter criteria. Saved views encapsulate complete workspace UI state including grid column layouts, filter configurations, sort preferences, and timeline display settings, enabling users to quickly switch between different data visualization perspectives. This endpoint is essential for populating view selector dropdowns, implementing view management interfaces, displaying available workspace configurations, and enabling view discovery features. Use this to fetch all available saved views when initializing a workspace, to build view selection menus showing users their custom views alongside default system views, or to implement view management panels where users can browse and select from their collection of saved configurations. The response includes view metadata (name, type, route, creator) and can be filtered by view type (list vs timeline), route context (programs, requests, tasks), or name substring for search functionality. Supports cursor-based pagination for efficient handling of large view collections and sorting by creation or update timestamps.

Key Features:

  • Paginated retrieval of all saved views in a space with cursor-based navigation
  • Filter by view type (list/timeline), route (programs/requests/tasks), or name substring
  • Sort results by createdAt or updatedAt timestamps in ascending or descending order
  • Returns both user-created custom views and system-provided default views
  • Includes complete view metadata for building view selector interfaces

Typical Use Cases:

  1. Populate View Selector Dropdown: Call GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/savedViews?route=tasks&type=list to fetch all list-type task views for displaying in a workspace view selector menu.
  2. View Management Interface: Call GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/savedViews?sort=updatedAt:desc&limit=20 to display the 20 most recently modified views in a view management panel where users can browse, edit, or delete their saved configurations.
  3. View Search: Call GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/savedViews?name=Priority to find all views with Priority in their name, enabling users to quickly locate specific saved configurations.

Expected Response:
Returns 200 OK with SavedViewQueryResponse containing items array of SavedView objects, pagination metadata (cursor, limit, count), and meta information. Each SavedView includes id, name, type, route, spaceId, gridState, gridFilterModel, gridSortModel, timelineState, createdAt, updatedAt, and creator details.

Authorization Logic:

  1. User must have valid JWT token with view or manage scopes
  2. Private views are only visible to their creators; shared views visible to all space members
  3. System-provided default views are visible to all users with space access
Path Params
string
required
length between 7 and 22

The unique identifier of the space containing the target entity. This determines the scope of entity queries and ensures proper access control. The space must be accessible to the authenticated user with appropriate permissions. It can be the unique identifier (GUID) of the space or the word "default" to indicate the default programs space. Common values include "default" and "rkr83lapKkyCJuLLWqLqzB".

Query Params
string

Optional substring filter to search for saved views by name. Case-insensitive partial matching against view names, useful for implementing search autocomplete or filtering view lists. For example, name=Priority returns views named 'High Priority Tasks', 'Priority Programs Q1', and 'My Priority List'. Leave empty to return all views regardless of name. Commonly used when users type into view selector search boxes or when implementing view discovery features.

string
enum

Optional filter to return only saved views of a specific visualization type. Allowed values are 'list' for grid/table views with columns and rows, or 'timeline' for Gantt chart or calendar-based timeline views. Use type=list when populating grid view selectors, or type=timeline when showing timeline view options. Leave empty to return all view types. This filter helps separate different visualization modes in the UI and ensures users only see views compatible with their current display context.

Allowed:
string
enum

Optional filter to return only saved views associated with a specific workspace context or entity type. Allowed values are 'programs' for program management views, 'requests' for request tracking views, or 'tasks' for task list views. Use route=tasks when displaying task view selectors, route=programs for program view selectors, or route=requests for request view selectors. Leave empty to return views across all routes. This filter ensures view selectors only show contextually appropriate saved configurations, preventing users from accidentally applying task views to programs or vice versa.

Allowed:
sort
array of strings

Optional array of sort expressions to order the saved views result set. Each expression uses field:direction format where field is the property name (createdAt, updatedAt, name) and direction is 'asc' for ascending or 'desc' for descending. Common patterns include sort=createdAt:desc to show newest views first, sort=updatedAt:desc to show recently modified views first, or sort=name:asc for alphabetical ordering. Multiple sort criteria can be provided to establish precedence (e.g., ["name:asc", "createdAt:desc"] sorts alphabetically then by creation date). Leave empty to use default ordering. Useful for implementing view management interfaces where users expect chronological or alphabetical view lists.

sort
string

Opaque pagination token returned in the previous response's cursor field, used to retrieve the next page of saved views. On the first request, omit this parameter or leave empty to start from the beginning. On subsequent requests, pass the cursor value from the previous response to fetch the next page. Cursor tokens are server-generated, base64url-encoded strings that should not be parsed or modified by clients. Continue paginating until the response cursor is null, indicating no more results. Required for workspaces with many saved views to efficiently navigate large result sets without loading all views at once.

int32

Maximum number of saved views to return in a single response page. Accepts positive integers, commonly between 10 and 100. Use smaller values (10-25) for UI dropdowns with limited screen space, or larger values (50-100) for view management pages displaying many items. Defaults to a server-defined limit (typically 50) if omitted. Combine with cursor parameter to implement pagination when total view count exceeds the limit. Setting appropriate limits balances response payload size with number of round trips needed to fetch all views.

Responses

Updated 1 day ago

Language
Response 
Click Try It! to start a request and see the response here! Or choose an example:
application/json
Updated 1 day ago