Coda API

Name: Coda API
Brand: Coda API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbearer124 EndpointsREST

For Agents

Read and write Coda doc rows, manage pages and tables, share and publish docs, and inspect formulas, controls and automations across 124 endpoints.

Install Jentic One Beta

Connect the Coda API to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Coda API.

List, search, create, copy, and delete Coda docs via the /docs endpoints

Read, insert, upsert, update, and delete table rows via /docs/{docId}/tables/{tableIdOrName}/rows

Walk the page tree, fetch page content, and export pages via /docs/{docId}/pages and /export

GET STARTED

Start building with Coda API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Coda API for, with concrete tasks.

★ Two-Way Sync Between Coda and a Backend

Keep a Coda table and an internal database aligned by reading rows on a schedule and writing changes back. POST /docs/{docId}/tables/{tableIdOrName}/rows supports insert and upsert, GET on the same path streams rows with pagination, and the X-Coda-Doc-Version header forces a fresh read when staleness is unacceptable. Most teams stand up a working sync in well under a day.

Upsert a list of order rows into the 'Orders' table via POST /docs/{docId}/tables/Orders/rows with keyColumns set to ['order_id'].

Doc Sharing and Publishing Automation

Programmatically share new docs with the right teams and publish customer-facing docs. POST /docs/{docId}/acl/permissions adds a principal, GET /docs/{docId}/acl/permissions lists the current ACL, and PUT /docs/{docId}/publish takes the doc public with optional discoverability controls. Useful for templated workspace provisioning when a new project starts.

Add the email alex@example.com as an editor on doc id abc123 by POSTing to /docs/abc123/acl/permissions.

Page and Content Export

Pull doc content out of Coda for use in another system - a wiki migration, a static site, or an LLM ingestion pipeline. POST /docs/{docId}/pages/{pageIdOrName}/export starts an export, GET on the matching /export/{requestId} polls until it is ready, and GET /docs/{docId}/pages/{pageIdOrName}/content returns the live page content. Combined this gives a deterministic, version-pinned snapshot.

Begin an export of page 'Roadmap' via POST /docs/{docId}/pages/Roadmap/export, then poll the resulting /export/{requestId} until status is complete.

Doc Templates and Workspace Onboarding

Spin up a new Coda doc from a template each time a project starts. POST /docs creates a doc (optionally cloning from an existing doc id), PATCH /docs/{docId} renames or moves it, and the ACL endpoints share it with the right people in one go. Repeatable in seconds with a single workflow.

Create a new Coda doc from sourceDoc id template-doc-id via POST /docs and rename it to 'Q3 Planning' with PATCH /docs/{docId}.

AI Agent Coda Workflows via Jentic

An AI assistant uses Jentic to read and write Coda rows on behalf of a user without storing the Bearer token. The agent searches for 'insert a row into a Coda table', loads the schema for POST /docs/{docId}/tables/{tableIdOrName}/rows, and executes - Jentic injects the API token from the vault and respects scoped tokens that limit the agent to specific docs or tables.

Use Jentic to search for 'insert a Coda row', load the POST /docs/{docId}/tables/{tableIdOrName}/rows schema, and add a row to the 'Inbox' table.

Key Endpoints

124 endpoints — the coda api lets developers and ai agents interact with coda docs the same way the editor does - listing and creating docs, sharing and publishing them, walking the page tree, and reading or writing rows in tables.

METHOD

PATH

DESCRIPTION

GET

/docs

List available docs

POST

/docs

Create a new doc

GET

/docs/{docId}/tables/{tableIdOrName}/rows

List rows in a table

POST

/docs/{docId}/tables/{tableIdOrName}/rows

Insert or upsert rows

POST

/docs/{docId}/acl/permissions

Share a doc by adding a permission

PUT

/docs/{docId}/publish

Publish a doc to the web

POST

/docs/{docId}/pages/{pageIdOrName}/export

Begin a page content export

GET

/docs

List available docs

POST

/docs

Create a new doc

GET

/docs/{docId}/tables/{tableIdOrName}/rows

List rows in a table

POST

/docs/{docId}/tables/{tableIdOrName}/rows

Insert or upsert rows

POST

/docs/{docId}/acl/permissions

Share a doc by adding a permission

Why Jentic?

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

Credential isolation

Your Coda token is stored once, encrypted, by your own Jentic One instance and added to the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'insert a Coda row' or 'share a Coda doc', and Jentic returns the matching Coda operation with its parameter schema so the agent builds a row payload without reading the full reference.

Time to first call

FAQs

Specific to using Coda API through Jentic.

What authentication does the Coda API use?

The Coda API uses HTTP Bearer authentication with a UUID-format API token created at https://coda.io/account. Tokens can be restricted by object (specific docs or tables) and by operation (read, write, or both). Through Jentic the token is stored encrypted in the vault and added to the Authorization header at execution time.

Can I insert and upsert rows into a Coda table?

Yes. POST /docs/{docId}/tables/{tableIdOrName}/rows accepts a list of rows for insert, and the same endpoint supports upsert via the keyColumns parameter. Writes are asynchronous - the response returns 202 with a requestId you can pass to /mutationStatus to confirm the edit was applied.

What are the rate limits for the Coda API?

Coda enforces per-user rate limits that vary by category (read, write, write-doc-content, list-docs, analytics) and returns 429 when exceeded. The exact numeric limits are not published in the spec and may change, so callers should treat 429 responses as the source of truth and back off with exponential retry.

How do I share a Coda doc with someone through Jentic?

Search Jentic for 'share a Coda doc', load the POST /docs/{docId}/acl/permissions schema, and execute with the principal email and access level (reader, writer, etc.). Install the SDK with pip install jentic and call it via the async client.

Can I export a Coda page as Markdown?

Yes. POST /docs/{docId}/pages/{pageIdOrName}/export starts an export job with the desired output format, and GET /docs/{docId}/pages/{pageIdOrName}/export/{requestId} polls for completion and returns the download link. Use this for wiki migrations or LLM ingestion.

Why do my row writes return 202 instead of 200?

Coda processes mutations asynchronously to keep edits consistent with collaborator changes. The 202 response includes a requestId; pass it to the mutation status endpoint to find out whether the edit succeeded, failed, or is still pending. Plan around a few seconds of write latency.

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

Yes. Because you run Jentic One yourself, your own rules decide which Coda operations and credentials the agent may use. Since Coda puts the doc id in the URL path (/docs/{docId}/...), a rule can pin the agent to a single doc and restrict it to reading and writing that doc's rows. Operations that change sharing or visibility, such as editing ACL permissions via /docs/{docId}/acl/permissions or publishing a doc, stay excluded unless you add them.

Coda API

Connect the Coda API to your agent

Capabilities

Start building with Coda API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs