Upsert
Create or update a saved view.
The view id is supplied by the caller (a UUID), which makes this operation
idempotent — repeating the same request converges to the same view rather
than creating a duplicate. Mutable fields are optional: a field that is set
is written, a field that is omitted is left unchanged. To guard against
overwriting a concurrent edit, pass the etag you last read.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Client-supplied UUID identifying the view. The same id updates the same view; a new id creates a new view.
Title. Required when creating; omit to keep the existing title on update.
1 - 200Description. Omit to keep the existing description.
10000Surface the view applies to. Omit to keep the existing context.
SAVED_VIEW_CONTEXT_UNSPECIFIED, SAVED_VIEW_CONTEXT_CHECKS, SAVED_VIEW_CONTEXT_ISSUES The selection. Required when creating; omit to keep the existing selection.
Display configuration. Omit to keep the existing config.
Sharing state. Omit to keep the existing visibility.
SAVED_VIEW_VISIBILITY_UNSPECIFIED, SAVED_VIEW_VISIBILITY_SHARED, SAVED_VIEW_VISIBILITY_GRANTED Access grants. When present, replaces the entire grant set (an empty list clears all grants); when omitted, grants are left unchanged. Changing grants requires manage/admin permission on the view.
Optional optimistic-concurrency guard. When set, the update fails with a conflict if the view was modified since this etag was read.
Response
Success
The stored view after the upsert.