Vendors / Work management

Coda (Superhuman Docs)

The current Coda API documentation calls the product Superhuman Docs. It exposes accessible documents, tables and rows through the existing coda.io API.

Overall controlB7.3*/10
Assessment checked 2026-10-22Public documentation · No live account test

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Notion vs Coda: compare API access and data control ↗

OVERALL CONTROL / 0.6-customer-control

Grades and scoring

Overall B / 7.3*/10, with 14 of 16 applicable scoring inputs verified. Missing evidence discounts the supported score (unknown answers remain unknown).

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Data access and planned exit carry the most weight. Known commercial barriers cap access; an unpublished price applies a bounded discount. Post-cancellation retrieval is a separate disclosure. Open each dimension to inspect its inputs and sources.

A8.3/10

Data access

25% of the overall score before applicability adjustment.

Scored answers and evidence

Read interface 7.5/10

Structured API for the declared product scope

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The current Coda API documentation calls the product Superhuman Docs. It exposes accessible documents, tables and rows through the existing coda.io API.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗

Bulk delivery 8.8/10

Batched or iterable API requests

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Follow nextPageToken rather than inferring completion from page length; later requests need only pageToken.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗

Query expressiveness 8.8/10

Documented structured API filters

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Row queries select table data. Returned snapshots can lag browser state, and volatile formulas can differ from interactive results.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗

Access cost barrier 10.0/10

Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

API use is free in Free and paid workspaces; user roles and feature permissions still apply.

Coda current document and row API reference ↗
Free and Paid Workspaces · Checked 2026-10-22

Answer-to-score anchors ↗
A8.8*/10

Third-party accessibility

20% of the overall score before applicability adjustment.

Scored answers and evidence

Third-party eligibility 10.0/10

Customer authorization without discretionary provider approval

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Users issue bearer API tokens with their document permissions. The token owner’s workspace role constrains operations.

Coda current document and row API reference ↗
Getting Started and Free and Paid Workspaces · Checked 2026-10-22

Answer-to-score anchors ↗

Downstream permission -

-

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.

Coda current document and row API reference ↗
Getting Started and Free and Paid Workspaces · Checked 2026-10-22

Answer-to-score anchors ↗
A8.5/10

External action

15% of the overall score before applicability adjustment.

Scored answers and evidence

Write interface 7.5/10

Create and update in one business domain

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Insert or upsert table rows and update rows. Accepted mutations return a request ID that must be checked for completion.

Coda current document and row API reference ↗
Insert/upsert rows, Update row and Get mutation status · Checked 2026-10-22

Answer-to-score anchors ↗

Custom application path 10.0/10

Customer applications using fixed APIs without provider selection

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The documented interface can connect customer application code within its authorization and resource scope.

Coda current document and row API reference ↗
Getting Started and Free and Paid Workspaces · Checked 2026-10-22

Answer-to-score anchors ↗
C4.3/10

Continuity

15% of the overall score before applicability adjustment.

Scored answers and evidence

Refresh mechanism 5.0/10

Scheduled feeds or recurring extracts

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗

Limit visibility 10.0/10

Published numeric quotas and recovery instructions

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Read, write, content-write and list-doc limits differ. Handle 429 with backoff and retry.

Coda current document and row API reference ↗
Rate Limiting · Checked 2026-10-22

Answer-to-score anchors ↗

CDC and deletion capture 2.5/10

Full snapshots permit customer reconciliation; native deltas unverified

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗

Replay and gap recovery 2.5/10

Rebuild from a fresh snapshot; no historical replay established

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗
B7.5/10

Data exit

20% of the overall score before applicability adjustment.

Scored answers and evidence

Export custody 7.5/10

Customer-held structured files or API records

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗

Post-cancellation access Disclosure

-

Disclosure only; does not reduce planned-exit credit.

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The reviewed technical documentation does not establish retrieval rights after account termination.

Coda current document and row API reference ↗
Getting Started and Free and Paid Workspaces · Checked 2026-10-22

Answer-to-score anchors ↗

Planned migration fidelity 7.5/10

Portable structured records on documented routes; whole-product completeness unverified

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Table records are portable; snapshots, volatile formulas and asynchronous writes limit equivalence to an interactive doc. Native app restore was not established.

Coda current document and row API reference ↗
Using the API, Resource IDs and Links, Rows and Consistency · Checked 2026-10-22

Answer-to-score anchors ↗
D2.1*/10

Business logic and customization

5% of the overall score before applicability adjustment.

Scored answers and evidence

Logic authoring 2.5/10

External integration code; native business logic portability not established

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).

Coda current document and row API reference ↗
Getting Started and Free and Paid Workspaces · Checked 2026-10-22

Answer-to-score anchors ↗

Rights to custom logic -

-

Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Ownership and reusable export rights for native workflow artifacts need a separate contractual review.

Coda current document and row API reference ↗
Getting Started and Free and Paid Workspaces · Checked 2026-10-22

Answer-to-score anchors ↗

Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗

CUSTOMER CHOICE

Third-party accessibility

Users issue bearer API tokens with their document permissions. The token owner’s workspace role constrains operations.

Third-party eligibilityCustomer authorization without discretionary provider approvalSource & scope ↗
Access cost barrierAccess is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleSource & scope ↗
Downstream permission-Source & scope ↗

Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.

READ / INTEGRATE

API and export routes

Follow nextPageToken rather than inferring completion from page length; later requests need only pageToken. Row queries select table data. Returned snapshots can lag browser state, and volatile formulas can differ from interactive results.

Access routeAuthenticationCredential ownerProvider approvalAccess requirementLast checked
v1 document and table-row API, including row insertion and updatesAPI keyCustomerNoCustomer-supplied credentials2026-10-22

Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.

ECONOMIC ACCESS

Cost, authentication and limits

API use is free in Free and paid workspaces; user roles and feature permissions still apply.

Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.

ACT FROM OUTSIDE

External action

Insert or upsert table rows and update rows. Accepted mutations return a request ID that must be checked for completion.

Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.

KEEP ACCESS USEFUL

Continuity

Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.

CDC, deletions and recovery

QuestionAnswer / applicable routeEvidence
Can ongoing extraction identify updates and deleted records on the declared route?Full snapshots permit customer reconciliation; native deltas unverifiedCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22
How can extraction recover after missed events or an interrupted consumer?Rebuild from a fresh snapshot; no historical replay establishedCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22

Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.

LEAVE WITH YOUR DATA

Data exit and portability

Table records are portable; snapshots, volatile formulas and asynchronous writes limit equivalence to an interactive doc. Native app restore was not established.

Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.

BUILD / INSPECT / REUSE

Business logic and customization

Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).

Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.

AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS

Documented conditions

Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.

QuestionAnswer / applicable routeEvidence
What structured read interface is documented?Structured API for the declared product scopeCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The current Coda API documentation calls the product Superhuman Docs. It exposes accessible documents, tables and rows through the existing coda.io API.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22
How can customers retrieve data in bulk?Batched or iterable API requestsCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Follow nextPageToken rather than inferring completion from page length; later requests need only pageToken.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22
What queries can a customer issue outside the provider UI?Documented structured API filtersCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Row queries select table data. Returned snapshots can lag browser state, and volatile formulas can differ from interactive results.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22
Who decides whether a chosen third party may connect?Customer authorization without discretionary provider approvalCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Users issue bearer API tokens with their document permissions. The token owner’s workspace role constrains operations.

Coda current document and row API reference ↗Getting Started and Free and Paid WorkspacesChecked 2026-10-22
What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan?Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

API use is free in Free and paid workspaces; user roles and feature permissions still apply.

Coda current document and row API reference ↗Free and Paid WorkspacesChecked 2026-10-22
Which external write operations are documented?Create and update in one business domainCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Insert or upsert table rows and update rows. Accepted mutations return a request ID that must be checked for completion.

Coda current document and row API reference ↗Insert/upsert rows, Update row and Get mutation statusChecked 2026-10-22
How can customers connect an application they build or choose?Customer applications using fixed APIs without provider selectionCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The documented interface can connect customer application code within its authorization and resource scope.

Coda current document and row API reference ↗Getting Started and Free and Paid WorkspacesChecked 2026-10-22
What mechanism supports repeatable extraction of changes?Scheduled feeds or recurring extractsCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22
How are integration limits disclosed?Published numeric quotas and recovery instructionsCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Read, write, content-write and list-doc limits differ. Handle 429 with backoff and retry.

Where can a usable data copy be delivered?Customer-held structured files or API recordsCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22
What retrieval rights are documented at cancellation?-Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

The reviewed technical documentation does not establish retrieval rights after account termination.

Coda current document and row API reference ↗Getting Started and Free and Paid WorkspacesChecked 2026-10-22
How can customers define their own business logic?External integration code; native business logic portability not establishedCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).

Coda current document and row API reference ↗Getting Started and Free and Paid WorkspacesChecked 2026-10-22
What rights or portability are documented for custom workflow artifacts?-Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Ownership and reusable export rights for native workflow artifacts need a separate contractual review.

Coda current document and row API reference ↗Getting Started and Free and Paid WorkspacesChecked 2026-10-22
What usable data or native definitions can leave before cancellation?Portable structured records on documented routes; whole-product completeness unverifiedCoda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Table records are portable; snapshots, volatile formulas and asynchronous writes limit equivalence to an interactive doc. Native app restore was not established.

Coda current document and row API reference ↗Using the API, Resource IDs and Links, Rows and ConsistencyChecked 2026-10-22
What permission is needed for the documented downstream use?-Coda (Superhuman Docs) / v1 document and table-row API, including row insertion and updates; complete interactive-doc restoration is excluded.

Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.

Coda current document and row API reference ↗Getting Started and Free and Paid WorkspacesChecked 2026-10-22

SOURCES / SCOPE / HISTORY

Sources and open questions

This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.

Still to confirm

  • Downstream contractual permissions and post-cancellation retrieval rights
  • Complete migration of history, files, permissions and native workflow definitions

Documentation

Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.