AITable API

Name: AITable API API
Brand: AITable API
Availability: InStock

★ Only Publicly Available SpecProductivityCollaborationbearer14 EndpointsREST

For Agents

Read and write rows in collaborative datasheets, manage fields and views, and upload attachments. Designed for agents that operate spreadsheets as a backend.

Quickstart

Get started with AITable API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create records in a collaborative datasheet"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AITable API API.

List spaces and traverse the node tree to find a target datasheet

Read records from a datasheet with filtering and pagination

Create, update, and delete records in batches

Add and remove fields on a datasheet to evolve its schema

List views configured on a datasheet for filtered reads

GET STARTED

Start building with AITable API API

Explore with Jentic

View OpenAPI Spec

Use for: List all spaces I can access, Get records from datasheet {id} where Status equals Open, Create a new record in datasheet {id} with the given fields, Update the Status field on records 1, 2, and 3

Not supported: Does not handle billing, document editing, or chat — use for collaborative datasheet records, fields, and attachments only.

Jentic publishes the only available OpenAPI specification for AITable API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AITable API, keeping it validated and agent-ready. AITable is a collaborative data platform — a programmable spreadsheet-database hybrid in the same family as Airtable. The 14-endpoint Fusion API exposes spaces and nodes (workspaces and tabs), datasheet records, fields, views, attachment uploads, and contact directories. Authentication is bearer-token based, and operations are designed for batch record creation, updating, and deletion.

Use Cases

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

★ Spreadsheet as agent memory

Use an AITable datasheet as a structured persistent store for an AI agent — write task results into rows, query past results by status, and update fields as work progresses. Batch endpoints let the agent process many rows in one call.

POST to /datasheets/{datasheetId}/records with an array of new task rows, then PATCH the same endpoint to mark them as 'In Progress'

Internal tool back-end

Power a lightweight internal tool (CRM, ticket tracker, asset register) by writing to AITable records. The Fields endpoints let an admin agent evolve schemas, and Views give read-only filtered cuts to share with stakeholders.

Create a 'Status' field on the datasheet via POST /datasheets/{id}/fields, then bulk-update existing records to set the new field

Attachment ingestion

Allow an agent to capture screenshots, PDFs, or audio files and attach them to records. POST /datasheets/{id}/attachments uploads the file, and the resulting attachment id can be referenced by an attachment field on a record.

Upload report.pdf via POST /datasheets/{id}/attachments and PATCH the matching record's Attachments field with the returned id

AI agent integration via Jentic

An agent uses Jentic to discover AITable's record operations by intent, loads the schema, and runs reads/writes. The bearer token is held in the Jentic vault, so agents can update spreadsheets without ever touching the credential.

Search Jentic for 'create rows in a datasheet', load the AITable POST /datasheets/{datasheetId}/records operation, and execute with the target datasheet id

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for aitable api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/spaces

List spaces

GET

/datasheets/{datasheetId}/records

Get records with filter and pagination

POST

/datasheets/{datasheetId}/records

Create records in batch

PATCH

/datasheets/{datasheetId}/records

Update records in batch

DELETE

/datasheets/{datasheetId}/records

Delete records in batch

POST

/datasheets/{datasheetId}/fields

Create a field

POST

/datasheets/{datasheetId}/attachments

Upload an attachment

GET

/spaces

List spaces

GET

/datasheets/{datasheetId}/records

Get records with filter and pagination

POST

/datasheets/{datasheetId}/records

Create records in batch

PATCH

/datasheets/{datasheetId}/records

Update records in batch

DELETE

/datasheets/{datasheetId}/records

Delete records in batch

Why though Jentic?

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

Credential isolation

AITable bearer tokens are stored encrypted in the Jentic vault. The agent receives a scoped execution capability — the raw token never enters the agent's prompt or memory.

Intent-based discovery

Agents search by intent (e.g., 'create rows in a spreadsheet') and Jentic returns the matching AITable record operation with its input schema so the agent calls it without browsing docs.

Time to first call

Direct AITable integration: half a day to wire bearer auth, batch records, and attachments. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Airtable

The original spreadsheet-database hybrid with a more mature ecosystem.

Choose Airtable when an existing organisation already runs on it. Choose AITable when you want an open or self-hostable alternative with a similar API shape.

Alternative

Smartsheet

Enterprise spreadsheet platform with project-management features.

Choose Smartsheet for project tracking with Gantt and approvals; choose AITable for lighter-weight datasheet automation.

Complementary

Notion API

Pair Notion docs with AITable structured records for hybrid workflows.

Use Notion for unstructured docs and AITable for structured rows; agents can move data between them.

FAQs

Specific to using AITable API API through Jentic.

Why is there no official OpenAPI spec for AITable API?

AITable does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AITable API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AITable API use?

AITable uses HTTP bearer authentication — supply your token in the Authorization: Bearer <token> header. Through Jentic, the token is stored encrypted in the Jentic vault and injected at execution, so the agent never sees it.

Can I create multiple records in one call?

Yes. POST /datasheets/{datasheetId}/records accepts an array of records, and PATCH and DELETE on the same path also operate in batch. This is the recommended way to keep request volume low.

How do I read records from a specific view through Jentic?

Use the Jentic search query 'get records from a datasheet view'. Jentic returns the GET /datasheets/{datasheetId}/records operation; pass the viewId query parameter to scope the read to that view.

Are there rate limits on the AITable Fusion API?

AITable applies plan-based rate limits that are not enumerated in the OpenAPI spec. Implement retry-with-backoff on 429 responses and prefer batch endpoints to stay under quotas.