Create Object View
POST /objects/{object_slug}/views
Save a private or shared view owned by this credential, without impersonating a human.
Authorizations
Parameters
Path Parameters
Header Parameters
Request Body required
object
object
Who can apply a view. Only the creator can update or delete it.
Responses
201
Successful Response
object
Response shape — flat shape with state at top level for convenience.
object
Which CRM grid the saved view applies to. Free-form string at the DB level (cb_saved_views.entity_type is VARCHAR(50)) to avoid a schema migration when we add deals/tasks/leads — but enforced as an enum at the API boundary so we don’t accept typos.
NEITHER A SUBSET NOR A SUPERSET OF FilterEntityType — see the invariant
on that class, and the sibling docstring below, which states the same
relationship from the other side. The two enums overlap on the four GRID
values (contacts, companies, deals, leads);
FilterEntityType is a superset of THOSE and adds report, while the
list/view/search/workbench/ads members here have no counterpart there.
Custom objects additionally use an object-bound view context.
(This paragraph previously read “DELIBERATELY NARROWER THAN
FilterEntityType”, which inverted the relationship: this is the LARGER
enum. The narrowness that matters is real but specific — report is
excluded, and only report — so stating it as a general containment
invited exactly the wrong conclusion about the other nine.)
Native grid members can be saved with context_key = NULL for reuse
across that entity type. CUSTOM_OBJECTS is the exception: it requires an
immutable object context and the object-authorized endpoints. It must never
enter the native grids’ reusable saved-filter menus.
The five ADS_* members are the Google Ads ad-group grids’ remembered
column state (shown, hidden, order), one private view per user per grid with
context_key = NULL. Their state carries columnPrefs and never a
filter tree, so none of them belongs in FilterEntityType. They are
separate members, not a reuse of an existing grid’s type, because a list
read returns every view of an entity type: a column-state row filed under
contacts would appear in the Contacts “Saved filters” menu.
object
Who can apply a view. Only the creator can update or delete it.
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error