canonical: https://jentic.com/apis/slite.slite.page/slite-slite-page

# Slite Slite Page Slite API

The Slite API enables you to programmatically interact with your Slite workspace. Create, read, update, and delete notes, manage users and groups, search your documentation, and use AI-powered features to query your knowledge base. The API exposes 22 endpoints secured with bearer authentication.

## For AI agents

Programmatically get authenticated user, create a note. Covers 22 operations with bearer authentication.

## Scope

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

## Capabilities

- Get authenticated user
- Create a note
- List notes
- Update a note
- Delete a note

## Use cases

### Productivity Operations

Use the Slite API to perform productivity operations programmatically. The API provides 22 endpoints covering core functionality including get authenticated user, create a note, list notes.

Example prompt: Call GET /me to get authenticated user

### Automated ask Management

Automate ask operations by combining multiple Slite API endpoints. Agents can create a note and then list notes in a single workflow.

Example prompt: Call POST /notes to create a note, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Slite 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 authenticated user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Get authenticated user |
| POST | `/notes` | Create a note |
| GET | `/notes` | List notes |
| GET | `/notes/{noteId}` | Get a note |
| PUT | `/notes/{noteId}` | Update a note |
| DELETE | `/notes/{noteId}` | Delete a note |
| GET | `/notes/{noteId}/children` | Get note children |
| PUT | `/notes/{noteId}/tiles/{tileId}` | Update a tile |

## Key resources

- **ask** — Operations related to ask
- **groups** — Operations related to groups
- **knowledge-management** — Operations related to knowledge-management
- **me** — Operations related to me
- **notes** — Operations related to notes

## Why Jentic

- **Setup:** Wiring the Slite API by hand means sending a JWT bearer token in the Authorization header to api.slite.com/v1 and managing the notes read, create, and update calls yourself. Through Jentic you install once, import Slite from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Slite puts the note id in the URL path (`/notes/{noteId}` and `/notes/{noteId}/children`), so a rule can pin your agent to a specific note. You choose the operations it may call, so destructive ones like note deletion are not included unless you add them.
- **Credential handling:** Your Slite bearer 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 'create a note' or 'read a note's children', and Jentic returns the matching Slite operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Slite API use?

The Slite 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 authenticated user with the Slite API?

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

### What are the rate limits for the Slite 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 authenticated user through Jentic?

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

### How many endpoints does the Slite API have?

The Slite API exposes 22 endpoints covering ask, groups, knowledge-management operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Slite operations and credentials the agent may use, so you can grant read and create calls like GET /notes and POST /notes while withholding destructive ones such as DELETE `/notes/{noteId}.` Slite puts the note id in the URL path (`/notes/{noteId}` and `/notes/{noteId}/children`), so a rule can pin the agent to a single note rather than the whole workspace. The bearer token stays with your instance and is injected only for the operations you approve.