Skip to main content

Set the default workspace view

Set an accessible saved view as the caller’s default view for its workspace.

POST/api/workspace-views/{view_id}/default
HTTP referenceScope workspace_views:writeUpdated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

Developer API keys need the listed scope. A valid authenticated user session may also call this route.

Saved views are scoped to the authenticated organization and user: organization-visible views and the caller’s private views may be listed, and mutation access is limited to editable views.

The raw view routes also accept workspace=signals. Developer keys use workspace_views:read to list and workspace_views:write to mutate these saved views; authenticated user sessions are also supported. This documents the raw endpoint behavior; the registered crm.saved_views list operation continues to describe Leads and Companies. Signals filter/topic values are preserved instead of receiving legacy CRM field-token rewrites. Shared view normalization still applies; typed filter descriptors and query_sort are supported for Leads views only.

The route clears the caller’s prior default for that workspace before marking this view as default.

Path parameters

  • view_idrequired

    string

    Saved view identifier.

Errors

StatusMeaning
401Authentication is missing or invalid.
403The credential is invalid or lacks the required scope, or the caller cannot access the resource.
400Organization or user context is missing.
404View is not visible to the caller.

Docs