An overview of the requirements to access API endpoints for Quip Event Monitoring.
What is Quip Event monitoring?
Quip Event Monitoring provides access to API endpoints that can be used to retrieve log data for Quip actions performed by your site members. For example, you might ingest these event logs from Quip into the security information & event management (SIEM) workflows used to govern your company’s applications.
Requirements
In order to utilize these API endpoints, you must have both:
*Note: If you have approved access to the Quip Admin API but have not purchased Quip Shield or Quip Event Monitoring, you are not permitted to use the Events and Near Real-Time Events endpoints of the Admin API. This is also documented here.
Using the API Endpoints
Once you have access to the Quip Admin API, follow the instructions at quip.com/dev/admin/documentation to get set up and start using the following two endpoints:
For full documentation, please visit our developer API docs.
000380926

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.