> ## Documentation Index > Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt > Use this file to discover all available pages before exploring further. # Set many table cell values > Apply up to 1000 manual cell edits in ONE transaction, then recompute their downstream formula cells — inline when the scope is small (see `recomputed_column_ids`), otherwise via a SINGLE cell-edited run covering all of them. The endpoint that makes a grid paste one request instead of N. A null value clears that cell. All-or-nothing: every column and value is validated before anything is written, so a formula column or a type mismatch anywhere rejects the whole batch and writes nothing. Same-value edits are counted in skipped and write nothing. Read-your-writes: the response carries every named row's post-write state and version. ## OpenAPI ````yaml /openapi.json post /tables/{table_id}/cells/bulk/ openapi: 3.1.0 info: contact: email: support@getoneprofile.ai name: Oneprofile Support description: >- REST API reference for Oneprofile, the GTM data layer for your CRM. Manage tables, enrichments, and integrations. Authenticate with an API key to get started. termsOfService: https://www.getoneprofile.ai/terms title: API Reference | Oneprofile version: '0.0' servers: - url: https://api.getoneprofile.ai security: [] tags: - description: Sender profiles, connected mailboxes, tags, and the Google connect flow. name: senders - description: The workspace do-not-contact list, enforced before every send. name: suppression - description: 'Sequence authoring: the graph, the table-backed audience, previews.' name: sequences - description: >- The LinkedIn channel: connecting an account to a sender, its safety limits and history, and the protocol the browser extension speaks. name: linkedin - description: 'The unified outreach inbox: threads, replies, labels, events.' name: inbox - description: 'The AI reply layer: workspace settings, drafts, and approval.' name: inbox-ai - description: Notification rules, per-user preferences, and the Slack connection. name: notifications - description: Endpoints for seeing all available integration types. name: integration-types - description: Endpoints for creating and managing integrations. name: integrations - description: Endpoints for the generic OAuth install/claim app-listings engine. name: app-listings - description: Endpoints for creating and managing API keys. name: apikey - description: Endpoints for managing billing and subscription information. name: billing - description: Endpoints for creating and managing tables. name: tables - description: Endpoints for table columns, formula previews, and on-demand column runs. name: table-columns - description: Endpoints for table rows and manual cell edits. name: table-rows - description: Endpoints for observing and cancelling table recompute runs. name: table-runs - description: >- Endpoints for org-shared per-column display preferences: hidden, pinned, width, and colour tint. name: table-ui-prefs - description: >- Endpoints for the org-shared names given to the column tint palette: what this organisation calls each colour. Org-level, not per-table. name: table-column-color-labels - description: >- Endpoints for the enrichment action catalog, model list, presets, draft generation, and saved agents. name: table-enrichments - description: >- Endpoints for teaching a saved agent from example rows: training sessions, per-row feedback, and the proposed prompt to approve. name: agent-training - description: >- The durable audit trail of a table's enrichment actions: configured, edited, run, cancelled, and settled cost. name: table-enrichment-audit-logs - description: Endpoints for saving and applying column templates. name: table-templates - description: Server-sent change feed for a table's grid. name: table-events - description: 'Endpoints for org-shared saved table views: sort, filters, hidden columns.' name: table-views - description: >- The per-table AI Assistant: named conversations, the column suggestions a build turn produces, and the questions an analyze turn answers. name: table-assistant - description: >- Endpoints for PER-USER table preferences: favourites and recently opened. Unlike the rest of the table surface these are personal, so two members of one organisation legitimately see different answers. name: table-user-prefs - description: >- Endpoints for building a table from an uploaded CSV: upload and preview the inferred columns, commit the reviewed mapping, then poll the row load. name: table-imports - description: Endpoint for downloading a table's rows as CSV. name: table-export - description: >- Endpoints for the integration a table imports from: attach and preview it, promote imported fields into columns, and run the import on demand. name: table-sources - description: >- Endpoints for a table's recurring import cadence: set it, pause it, and read the next fire times. name: table-schedules - description: >- Endpoints for pushing a table's rows out to a connected integration: list writable destinations, derive their write capabilities, and map export columns. name: table-writeback - description: >- Endpoints backing a lookup column's setup: the connections whose records a column could read, and the identity fields one record type can be looked up by. name: table-integration-lookup - description: >- Endpoints for sourcing leads from the lead database: count and preview matches, land them in a table, and keep saved searches. name: find-leads - description: >- Endpoints for discovering a domain's subdomains from public certificate logs and landing the results in a table. name: find-subdomains - description: Endpoints for the credit balance meter and usage reporting. name: credits - description: >- Endpoints for the workspace referral program: the shareable link, the friends who joined through it, and claiming a code after signup. name: referral - description: >- Endpoints for the design partner program's customer surface: whether this workspace is a design partner, the badges its feedback has earned, and sending and reading that feedback. name: design-partner - description: >- Endpoints for the org-level AI business context — company description, ideal customer profile, buyer personas and interest signals — plus domain-based generation. name: ai-context paths: /tables/{table_id}/cells/bulk/: post: tags: - table-rows summary: Set many table cell values description: >- Apply up to 1000 manual cell edits in ONE transaction, then recompute their downstream formula cells — inline when the scope is small (see `recomputed_column_ids`), otherwise via a SINGLE cell-edited run covering all of them. The endpoint that makes a grid paste one request instead of N. A null value clears that cell. All-or-nothing: every column and value is validated before anything is written, so a formula column or a type mismatch anywhere rejects the whole batch and writes nothing. Same-value edits are counted in skipped and write nothing. Read-your-writes: the response carries every named row's post-write state and version. operationId: bulk_set_table_cells parameters: - in: path name: table_id required: true schema: format: uuid title: Table Id type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/TableCellsBulkEditRequestSchema' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/TableCellsBulkMutationResponseSchema' description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/ForbiddenResponse' description: Forbidden '404': content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' description: Row or column not found '422': content: application/json: schema: $ref: '#/components/schemas/UnprocessableEntityResponse' description: Invalid request made to the API. '500': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Internal server error. '502': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Bad gateway error. '503': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Service unavailable. security: - HTTPBearer: [] - APIKeyHeader: [] components: schemas: TableCellsBulkEditRequestSchema: description: >- Request body for the bulk cell write — all-or-nothing, one recompute run. properties: edits: description: The cell edits to apply. items: $ref: '#/components/schemas/TableCellBulkEditItemSchema' maxItems: 1000 minItems: 1 title: Edits type: array required: - edits title: TableCellsBulkEditRequestSchema type: object TableCellsBulkMutationResponseSchema: description: >- Read-your-writes result of a bulk cell write — never carries a run ID. ``rows`` covers every row named by the request, including ones whose edits were all same-value no-ops, so the client can reconcile its whole selection in one pass. properties: applied: description: Edits that changed a value and were written. title: Applied type: integer recomputed_column_ids: description: >- Formula columns recomputed INLINE within this request — their values in `rows` are final and no background run was requested. Empty when a run was queued instead. items: format: uuid type: string title: Recomputed Column Ids type: array rows: items: $ref: '#/components/schemas/TableRowSchema' title: Rows type: array skipped: description: Same-value edits that wrote nothing. title: Skipped type: integer stale_column_ids: description: >- Transitive formula dependents now marked stale across all edited rows. items: format: uuid type: string title: Stale Column Ids type: array required: - rows - stale_column_ids - applied - skipped title: TableCellsBulkMutationResponseSchema type: object UnauthorizedResponse: properties: detail: description: The detail of why the request is unauthorized. title: Detail type: string required: - detail title: UnauthorizedResponse type: object ForbiddenResponse: properties: detail: description: The detail of why the request is forbidden. title: Detail type: string required: - detail title: ForbiddenResponse type: object NotFoundResponse: properties: detail: description: The detail of why the resource was not found. title: Detail type: string required: - detail title: NotFoundResponse type: object UnprocessableEntityResponse: properties: detail: description: >- The detail of the error. This is the error message to show to the user. You should also use the issues field to show more detailed error messages per field. Use this field for a single liner error message. title: Detail type: string issues: description: >- The issues that caused the error. There can be multiple issues. Each issue is a user-facing error message. items: $ref: '#/components/schemas/UnprocessableEntityIssue' title: Issues type: array required: - detail - issues title: UnprocessableEntityResponse type: object ServerErrorResponse: properties: detail: description: The detail of why the server returned an error. title: Detail type: string required: - detail title: ServerErrorResponse type: object TableCellBulkEditItemSchema: description: One edit in a bulk cell write; a null value clears the cell. properties: column_id: format: uuid title: Column Id type: string record_id: format: uuid title: Record Id type: string value: anyOf: - $ref: '#/components/schemas/CellValue-Input' - type: 'null' description: >- The new cell value, or null to clear it so the column default renders. required: - record_id - column_id title: TableCellBulkEditItemSchema type: object TableRowSchema: description: >- A table row; cells are keyed by the column ID as a string (JSON object keys). There is no row-level version or update stamp any more — freshness is a per-cell fact, and the detail panel shows each field's own ``updated_at``. properties: cells: additionalProperties: $ref: '#/components/schemas/TableCellSchema' title: Cells type: object created_at: description: When the row was created. format: date-time title: Created At type: string record_id: format: uuid title: Record Id type: string required: - record_id - created_at - cells title: TableRowSchema type: object UnprocessableEntityIssue: properties: input: anyOf: - type: string - type: integer - type: number - type: boolean - items: {} type: array - additionalProperties: true type: object description: The user's input that caused the error. title: Input loc: description: >- The location of the error. Always contains 1 or 2 elements. The first element is the type of location (e.g. 'body', 'query', 'path', 'header'). The second element is the name of the field that caused the error. If the error is not related to a specific field, the second element is not present. items: type: string title: Loc type: array msg: description: The message of the error. The error message to show to the user. title: Msg type: string type: description: >- The type of the error. Useful for frontend code to handle different types of errors. title: Type type: string required: - loc - msg - type - input title: UnprocessableEntityIssue type: object CellValue-Input: anyOf: - type: string - type: integer - type: number - type: boolean - format: date-time type: string - format: date type: string - items: anyOf: - $ref: '#/components/schemas/CellValue-Input' - type: 'null' type: array - additionalProperties: anyOf: - $ref: '#/components/schemas/CellValue-Input' - type: 'null' type: object TableCellSchema: description: >- One cell of a table row; a column absent from the row's cell map renders blank. ``computing`` is DERIVED, never stored: a cell is computing iff it is stale AND some active run has this row in its resolved scope. That second half used to reduce to "any active run exists anywhere in the table", because a run row published nothing about which rows it would touch; it now consults the scope the mint resolved, so a run over ten rows marks ten rows computing rather than every stale cell in the table. ``version`` is the cell's own monotonic watermark. It replaced a row-level counter, so two people editing different cells of one row no longer invalidate each other's cached view. properties: cancelled: default: false description: >- A run that owed this cell a recompute was cancelled or paused before reaching it. Cleared by any subsequent write; distinct from never-run (which has no cell at all). title: Cancelled type: boolean computed_at: anyOf: - format: date-time type: string - type: 'null' description: Last compute time (formula cells). title: Computed At computing: default: false description: Stale AND an active run has this row in its scope. title: Computing type: boolean confidence: anyOf: - type: string - type: 'null' description: >- The agent's own read on its answer (high/medium/low); null for actions that report none. What the grid's confidence glyph draws. title: Confidence credits_charged: anyOf: - type: number - type: 'null' description: >- Credits charged for producing this value; null for free work (manual edits, formulas, cache hits). title: Credits Charged error: anyOf: - type: string - type: 'null' description: The cell's evaluation error, when it failed. title: Error error_class: anyOf: - type: string - type: 'null' description: >- Machine-readable class of a failed enrichment cell (timeout, rate_limited, schema_violation, ...); null for formula errors and everything that is not an error. title: Error Class manual_override: default: false description: >- A hand-entered correction on an enrichment cell. Runs pass over it unless they explicitly target the cell; the grid marks it. title: Manual Override type: boolean settled_as: $ref: '#/components/schemas/TableCellSettlement' default: pending description: >- How the last attempt on this cell ENDED, never what it shows. The grid needs it to tell `no_data` (ran, found nothing) from `pending` (never ran). Both render blank, and on a formula column neither carries an error to tell them apart, so without this a finished cell was indistinguishable from an untouched one. skipped_reason: anyOf: - type: string - type: 'null' description: >- Non-null means the last run deliberately held this cell back — a required input was empty, or the run condition was false. A third outcome distinct from value and error; nothing ran, nothing was charged. title: Skipped Reason stale: default: false description: Value out of date; a recompute is pending. title: Stale type: boolean updated_at: description: When this cell was last written. format: date-time title: Updated At type: string value: description: The cell value; numbers are surfaced as JSON numbers. title: Value version: description: Per-cell watermark; apply a delta only if at least this. title: Version type: integer required: - value - error - version - updated_at title: TableCellSchema type: object TableCellSettlement: description: >- How this cell's last attempt ENDED. Never what the cell shows. Answers "is any work owed here", and nothing else. What a cell DISPLAYS is still read from the typed value slots, and must stay that way: sorting, filtering and ``HAS_RESULTS`` all ask what the cell contains. Only completeness asks this. THE FACT THAT WAS MISSING. The table stored what a cell contains and had no column for whether work was still owed on it, so every completeness figure guessed the second from the first. The guess was wrong in both directions. A cell that ran cleanly and produced nothing is DONE, and it read as permanently incomplete — on an AI column that is the majority outcome, so a table whose every run had finished could never reach 100%. Meanwhile a provider's ``200 OK`` carrying ``{"email": None}`` read as filled. Deliberately ORTHOGONAL to ``stale``. A stale cell keeps the settlement of the attempt that produced the value it is still showing; freshness is the ``stale`` flag's job, and duplicating it here would give one fact two homes that could disagree. "Complete" is therefore a conjunction of the two, and the aggregate spells it out rather than hiding it in a member. Members mirror the run counters on ``table_run`` (``cells_done`` / ``_failed`` / ``_skipped`` / ``_no_data``) one for one, so the footer mid-run and the footer idle finally measure comparable things. enum: - succeeded - no_data - skipped - failed - pending title: TableCellSettlement type: string securitySchemes: HTTPBearer: scheme: bearer type: http APIKeyHeader: in: header name: X-API-Key type: apiKey ````