Saves a named view (a stored set of column choices and filters) under your account so it can be reused via the $viewID query parameter on subsequent listing calls. The body must include a non-empty name and a valid viewObject JSON describing the configuration.

View names must be unique per user. Use PUT /views/{viewID} to update an existing view in place.

Note: if a view with the same name already exists for the caller, the call returns 400 (Bad Request) rather than the more accurate 409 Conflict — handle 400 from this endpoint as a possible duplicate-name signal.