SeaTable API

Name: SeaTable API
Brand: SeaTable API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationbearer12 EndpointsREST

For Agents

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

Use for: I need to append row(s), I want to rows, Search for row(s), Find all row(s)

Connect the SeaTable API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SeaTable API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SeaTable API.

Append row(s)

List rows

Update row(s)

Delete row(s)

Get row

GET STARTED

Start building with SeaTable API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SeaTable API for, with concrete tasks.

★ 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).

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.

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.

Search Jentic for 'append row(s)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

12 endpoints — seatable is an online database and spreadsheet platform.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

SeaTable API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'append row(s)') and Jentic returns the matching SeaTable API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SeaTable API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using SeaTable API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

SeaTable API

Connect the SeaTable API to your agent

Capabilities

Start building with SeaTable API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs