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

# SeaTable API

SeaTable is an online database and spreadsheet platform. The API provides comprehensive access to bases, tables, rows, columns, views, links, files, and more. Authentication uses tokens with different scopes: Account-Token for account-level operations, API-Token for base access, and Base-Token for base-specific requests. The API exposes 12 endpoints secured with bearer authentication.

## For AI agents

Programmatically append row(s), list rows. Covers 12 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Append row(s)
- List rows
- Update row(s)
- Delete row(s)
- Get row
- Query with SQL
- Create table

## Use cases

### Identity and Authentication Operations

Use the SeaTable API to perform identity auth operations programmatically. The API provides 12 endpoints covering core functionality including append row(s), list rows, update row(s).

Example prompt: Call POST /api-gateway/api/v2/dtables/{base_uuid}/rows to append row(s)

### Automated Rows Management

Automate rows operations by combining multiple SeaTable API endpoints. Agents can list rows and then update row(s) in a single workflow.

Example prompt: Call GET /api-gateway/api/v2/dtables/{base_uuid}/rows to list rows, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SeaTable 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 'append row(s)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api-gateway/api/v2/dtables/{base_uuid}/rows | Append row(s) |
| GET | /api-gateway/api/v2/dtables/{base_uuid}/rows | List rows |
| PUT | /api-gateway/api/v2/dtables/{base_uuid}/rows | Update row(s) |
| DELETE | /api-gateway/api/v2/dtables/{base_uuid}/rows | Delete row(s) |
| GET | /api-gateway/api/v2/dtables/{base_uuid}/rows/{row_id} | Get row |
| POST | /api-gateway/api/v2/dtables/{base_uuid}/sql | Query with SQL |
| POST | /api-gateway/api/v2/dtables/{base_uuid}/tables | Create table |
| POST | /api-gateway/api/v2/dtables/{base_uuid}/views | Create view |

## Key resources

- **Rows** — Operations for querying, creating, updating, and deleting rows
- **Tables** — Operations for managing tables
- **Views** — Operations for managing views
- **Links** — Operations for managing row links between tables
- **Files** — Operations for uploading and managing files

## Why Jentic

- **Setup:** Wiring the SeaTable API by hand means obtaining its bearer token, pointing calls at the right cloud or self-hosted server, and building each row, table, and SQL request yourself. Through Jentic you install once, import SeaTable from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SeaTable puts the base id in the URL path (/dtables/{base_uuid}/...), so a rule can pin your agent to one base: it can append and read rows there and nothing else. You choose the operations it may call, so destructive ones like deleting rows or creating tables are not included unless you add them.
- **Credential handling:** Your SeaTable 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 'append rows to a base' or 'query a base with SQL', and Jentic returns the matching SeaTable operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the SeaTable API use?

The SeaTable 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 append row(s) with the SeaTable API?

Yes. Use the POST /api-gateway/api/v2/dtables/{base_uuid}/rows endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SeaTable 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 append row(s) through Jentic?

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

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

The SeaTable API exposes 12 endpoints covering rows, tables, views operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SeaTable operations and credentials the agent may use. Since SeaTable puts the base id in the URL path (/dtables/{base_uuid}/...), you can pin the agent to a single base and grant only read and append on its rows, for example GET and POST on /api-gateway/api/v2/dtables/{base_uuid}/rows. Destructive operations such as deleting rows or creating tables stay off limits unless you explicitly add them.