canonical: https://jentic.com/apis/retable.io/retable

# Retable API

Retable API for managing workspaces, projects, tables (retables), rows, and columns in a spreadsheet-like database. The API exposes 17 endpoints secured with apiKey authentication.

## For AI agents

Programmatically insert a row, get rows from a table. Covers 17 operations with apiKey authentication.

## Scope

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

## Capabilities

- Insert a row
- Get rows from a table
- Update a row
- Delete rows
- Create a workspace

## Use cases

### Productivity Operations

Use the Retable API to perform productivity operations programmatically. The API provides 17 endpoints covering core functionality including insert a row, get rows from a table, update a row.

Example prompt: Call POST `/retable/{retable_id}/data` to insert a row

### Automated Columns Management

Automate columns operations by combining multiple Retable API endpoints. Agents can get rows from a table and then update a row in a single workflow.

Example prompt: Call GET `/retable/{retable_id}/data` to get rows from a table, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Retable 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 apiKey tokens manually.

Example prompt: Search Jentic for 'insert a row', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/retable/{retable_id}/data` | Insert a row |
| GET | `/retable/{retable_id}/data` | Get rows from a table |
| PUT | `/retable/{retable_id}/data` | Update a row |
| DELETE | `/retable/{retable_id}/data` | Delete rows |
| POST | `/workspace` | Create a workspace |
| GET | `/workspace` | Get all workspaces |
| GET | `/workspace/{workspace_id}` | Get a specific workspace |
| POST | `/workspace/{workspace_id}/project` | Create a project |

## Key resources

- **Columns** — Operations related to Columns
- **Data** — Operations related to Data
- **Files** — Operations related to Files
- **Projects** — Operations related to Projects
- **Retables** — Operations related to Retables

## Why Jentic

- **Setup:** Wiring the Retable API by hand means passing your ApiKey with its RTBL-v1 prefix, targeting the api.retable.io/v1/public host, and managing workspace, project, and row calls yourself. Through Jentic you install once, import Retable API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Retable API puts the retable id in the URL path (`/retable/{retable_id}/data`), so a rule can pin your agent to one retable: it can read and insert rows there and nothing else. You choose the operations it may call, so destructive ones like row deletion are not included unless you add them.
- **Credential handling:** Your Retable API key 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 'insert a row' or 'read data from a retable', and Jentic returns the matching Retable API 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 Retable API use?

The Retable API uses an API key passed in the `ApiKey` 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 insert a row with the Retable API?

Yes. Use the POST `/retable/{retable_id}/data` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Retable 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 insert a row through Jentic?

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

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

The Retable API exposes 17 endpoints covering columns, data, files operations.

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

Yes. Because you run Jentic One yourself and your own rules decide which operations and credentials the agent may use, you control exactly which Retable API calls it can make. Since the Retable API carries the retable id in the URL path, such as `/retable/{retable_id}/data`, you can pin the agent to a single retable so it only reads and inserts rows there. You also choose the operations it may call, so a destructive action like DELETE `/retable/{retable_id}/data` is excluded unless you explicitly allow it.