canonical: https://jentic.com/apis/quip.com/quip

# Quip Automation API

The Quip Automation API allows you to automate processes and integrate Quip with other products and services. You can use the API to create, read, update, and delete documents, spreadsheets, folders, and messages in Quip. The API exposes 32 endpoints secured with bearer authentication.

## For AI agents

Programmatically get current user, get user. Covers 32 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Get current user
- Update user
- Access Quip Automation API communications resources via REST API

## Use cases

### Communications Operations

Use the Quip Automation API to perform communications operations programmatically. The API provides 32 endpoints covering core functionality including get current user, get user, get users.

Example prompt: Call GET `/1/users/current` to get current user

### Automated Authentication Management

Automate authentication operations by combining multiple Quip Automation API endpoints. Agents can get user and then get users in a single workflow.

Example prompt: Call GET `/1/users/{id}` to get user, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Quip Automation API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'get current user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/1/users/current` | Get current user |
| GET | `/1/users/{id}` | Get user |
| GET | `/1/users` | Get users |
| GET | `/1/users/contacts` | Get contacts |
| POST | `/1/users/update` | Update user |
| GET | `/1/users/subdomain` | Get subdomain |
| GET | `/1/users/current/threads` | Get current user threads |
| GET | `/1/threads/{id}` | Get thread |

## Key resources

- **Authentication** — Operations related to Authentication
- **Blobs** — Operations related to Blobs
- **Folders** — Operations related to Folders
- **Messages** — Operations related to Messages
- **OAuth** — Operations related to OAuth

## Why Jentic

- **Setup:** Wiring the Quip Automation API by hand means learning its bearer auth, targeting the platform.quip.com host, and handling retries across its user and thread operations yourself. Through Jentic you install once, import Quip from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Quip puts the user and thread id in the URL path (`/1/users/{id}`, `/1/threads/{id}`), so a rule can pin your agent to one thread or user: it reads that resource and nothing else. You choose the operations it may call, so a write like updating a user is not included unless you add it.
- **Credential handling:** Your Quip token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get the current Quip user' or 'read a thread', and Jentic returns the matching Quip operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Quip Automation API use?

The Quip Automation API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get current user with the Quip Automation API?

Yes. Use the GET `/1/users/current` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Quip Automation API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get current user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current user'. Jentic returns the matching Quip Automation API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Quip Automation API have?

The Quip Automation API exposes 32 endpoints covering authentication, blobs, folders operations.

### Can I limit what my agent is allowed to do with the Quip Automation API?

Yes. Because you run Jentic One yourself, your own rules decide which Quip operations and credentials the agent may use. Since Quip puts the user and thread id in the URL path (GET `/1/users/{id}`, GET `/1/threads/{id}`), a rule can pin the agent to a single thread or user so it reads that resource and nothing else. You also choose the operations it may call, so a write such as POST `/1/users/update` stays out of reach unless you add it.