Retable API

Name: Retable API API
Brand: Retable API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationapiKey17 EndpointsREST

For Agents

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

Use for: I need to insert a row, I want to rows from a table, Search for a row, Find all rows

Connect the Retable API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Retable 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 Retable API API.

Insert a row

Get rows from a table

Update a row

Delete rows

Create a workspace

GET STARTED

Start building with Retable API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Retable API API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

17 endpoints — retable api for managing workspaces, projects, tables (retables), rows, and columns in a spreadsheet-like database.

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

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

Why though Jentic?

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

Credential isolation

Retable API apiKey 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., 'insert a row') and Jentic returns the matching Retable API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Asana

Alternative productivity API

Choose Asana when you need a different approach to productivity operations

Alternative

Monday

Alternative productivity API

Choose Monday when you need a different approach to productivity operations

Complementary

Clickup

Complementary productivity API

Choose Clickup when you need a complementary approach to productivity operations

FAQs

Specific to using Retable API API through Jentic.

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