improvement(external-endpoints): v2 versions with clean signatures + updated docs based on openapi spec

[icecrasher321]

Summary

Introduces a new, parallel /api/v2 external API surface that standardizes the
response envelope, pagination, error handling, and auth across every resource —
fixing the inconsistencies that had accreted in /api/v1 without breaking existing
v1 consumers. v1 stays in place and untouched on the wire; v2 is where the breaking
improvements land. Also includes a set of safe, in-place v1 correctness fixes
surfaced during the audit, and a full API-reference docs rework.

Type of Change

• Documentation
• Other: Code cleanup

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 2, 2026 5:56am

[cursor]

PR Summary

Low Risk
Changes are limited to documentation content and OpenAPI spec loading for the docs site; no application API runtime code appears in this diff.

Overview
Reworks the docs OpenAPI setup from a single spec into multiple JSON files (openapi-core.json for execution, human-in-the-loop, and usage, plus domain v2 specs such as files/audit). openapi.ts now feeds all of them into Fumadocs, resolves operations across specs for generated pages, and hardens $ref expansion with cycle detection.

The API reference sidebar is reorganized: run/cancel/job-status endpoints move out of Workflows into a new (generated)/execution group under an Execution and Usage section; workflows pages are limited to lifecycle CRUD/deploy. Locales get aligned nav (including tables, files, knowledge bases where they were missing).

Getting started (all locales) now links async polling to /api-reference/execution/getJobStatus. Enterprise audit logs docs switch the example auth header to X-API-Key, extend the list response example with limits, and note actorName, metadata, and rate-limit headers.

^{Reviewed by Cursor Bugbot for commit 98c8567. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds a parallel v2 external API and refreshes the API docs.

• New v2 routes for audit logs, files, knowledge, logs, tables, and workflows.
• Shared v2 response envelopes, pagination, and error helpers.
• Updated OpenAPI specs and generated docs navigation.
• Small v1 API correctness updates kept in place.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
apps/sim/app/api/v2/tables/[tableId]/rows/route.ts	Adds v2 row list, create, update, and delete handlers using the shared table services and v2 response envelope.
apps/sim/app/api/v2/tables/[tableId]/rows/[rowId]/route.ts	Adds v2 single-row read, update, and delete handlers with workspace checks and normalized row output.
apps/sim/app/api/v2/tables/[tableId]/rows/upsert/route.ts	Adds a v2 upsert endpoint that returns the normalized row and operation result.
apps/sim/app/api/v2/tables/[tableId]/columns/route.ts	Adds v2 column create, update, and delete handlers backed by the existing table column service.
apps/docs/lib/openapi.ts	Updates docs generation to load multiple OpenAPI specs and resolve references within the owning spec.

_{Reviews (2): Last reviewed commit: "improvement(external-endpoints): v2 vers..." | Re-trigger Greptile}

[greptile-apps]

Unknown Columns Are Dropped

When a v2 caller sends row data with a misspelled or differently cased column name, rowDataNameToId removes that key before validateBatchRows runs. The request can then succeed while silently losing the caller's submitted value; the same translation pattern is used by the single-row insert, update, and upsert paths.

[greptile-apps]

Invalid Filters Succeed Empty

filterNamesToIds leaves unknown filter fields unchanged, so a bulk update or delete with a misspelled public column name is executed as a lookup on a non-existent JSON key. The API can return a successful response with zero affected rows instead of rejecting the invalid destructive filter.

[greptile-apps]

Column Undo Can Lose Data

This v2 delete path returns as soon as deleteColumn finishes, while the shared column service strips the deleted column's row data in a fire-and-forget cleanup. If an external caller immediately recreates or restores a column with the same id, that delayed cleanup can remove the restored column values after the API has already reported success.