workspaces

Resolve Saved View

Changed on

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.

post/api/v1/workspaces/saved-views/resolve

Request

  • Base URL
    https://api.minro.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.minro.com/api/v1/workspaces/saved-views/resolve
  • Auth
    none declared

Headers

authorizationstring nullable

Bearer <token>

Request body

filterobject
exclude_idsstring[]
include_idsstring[]
preview_limitinteger

Response

Successful Response

dataobject required

Changes

  • 299da1f7604aRevision changes
    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

  • 2eae594b5490Revision changes
    • info

      the response's property default value {"request_id":"","timestamp":"2026-09-16T23:27:36.856600"} was removed for the status

    • info

      the response's property default value 2026-09-16T23:27:36.856600 was removed for the status