Skip to main content
Views are saved configurations of the recordings, deals, companies and contacts tables in Claap. A view defines which columns are displayed, which filters are applied and how rows are sorted. The API exposes the same views users create and share in the Claap application. Each domain has its own set of endpoints under /v1/recordings/views, /v1/deals/views, /v1/companies/views and /v1/contacts/views, since the available columns, filters and sort fields differ between domains.

​
Visibility

Views in Claap are either public (shared with the workspace) or private to their owner. Since API requests do not impersonate workspace users, only public views are accessible through the API:
  • Listing endpoints only return public views. Built-in default views are not included either, as they cannot be modified.
  • Retrieving, updating or deleting a private view fails as if the view did not exist.
  • Created views are always public.

​
Ownership

Creating a view requires a creatorEmail attribute. It must be the email address of an active workspace member, who becomes the owner of the view, as if they had created it in the Claap application.

​
Partial updates

Update endpoints accept partial payloads: omitted attributes keep their current values. Sending an attribute replaces its value entirely — for instance, sending columns replaces the whole column list, not just the entries it contains. A few internal filter attributes are not exposed through the API and always keep their stored values on update.

​
The Me filter type

Some filters (for example the recording author or the deal owner) accept a special entry of type Me in addition to explicit users or email addresses. Me is resolved dynamically to whoever is viewing the table in the Claap application, which allows a single shared view like “My deals” to show different rows to each user.