---
title: "Resolve Saved View"
method: POST
path: "/api/v1/workspaces/saved-views/resolve"
tags: ["workspaces"]
---

# Resolve Saved View

`POST /api/v1/workspaces/saved-views/resolve`

Resolve a saved view's filter to a real audience, server-side.

Until now a view could only be applied in the browser, over whatever customers
were loaded, so counts were counts of the fetched sample and no server flow
could target a view at all. This returns the true workspace-wide audience.

Suppressed and soft-deleted customers are excluded: a resolved view is a
sendable audience, not an analytical population. Filters that cannot be
evaluated in SQL (industry/role buckets, PostHog event filters) are NAMED in
`unresolvable_fields` rather than ignored — ignoring them would return a
superset of what the user saw, which is the dangerous direction for a send.

## Headers

- `authorization` string, nullable — Bearer <token>

## Request body

- ViewResolveRequest — A saved view's filter, plus the manual overrides the client tracks alongside it.
  - `filter` object
  - `exclude_ids` string[]
  - `include_ids` string[]
  - `preview_limit` integer

## Response `200`

Successful Response

- EnvelopeDict
  - `data` object, required
  - `meta` Meta
    - `request_id` string
    - `timestamp` string, date-time
    - `total` integer, nullable
    - `truncated` boolean, nullable

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/minro/apis/minro-cs-platform.md) · [All operations](https://skmtc.dev/minro/apis/minro-cs-platform/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/minro/minro-cs-platform/revisions/eb854265cf29/schema)