> ## 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. # Get table stats > Get aggregate stats for one table: row count, columns per kind, failed cell count, the newest active run (if any), and whether the table is at its row cap. ## OpenAPI ````yaml /openapi.json get /tables/{table_id}/stats/ 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}/stats/: get: tags: - tables summary: Get table stats description: >- Get aggregate stats for one table: row count, columns per kind, failed cell count, the newest active run (if any), and whether the table is at its row cap. operationId: get_table_stats parameters: - in: path name: table_id required: true schema: format: uuid title: Table Id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/TableStatsSchema' 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: Table 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: TableStatsSchema: description: Aggregate stats for one table, composed from three downward reads. properties: active_run: anyOf: - $ref: '#/components/schemas/TableRunReadSchema' - type: 'null' description: The newest active run, when one exists. at_row_cap: description: Whether the table has reached its row cap. title: At Row Cap type: boolean cell_settlement_by_column: additionalProperties: $ref: '#/components/schemas/CellSettlementSchema' description: >- How each column's cells ended, per column ID. A column with no cells is absent — read absence as zero across every figure. The completeness read. `filled_cells_by_column` and `failed_cells_by_column` are both projections of this and are kept only so an existing API-key client does not break. propertyNames: format: uuid title: Cell Settlement By Column type: object columns_by_kind: additionalProperties: type: integer description: Number of columns per column kind (manual/formula). title: Columns By Kind type: object failed_cells: description: Cells currently carrying an evaluation error. title: Failed Cells type: integer failed_cells_by_column: additionalProperties: type: integer description: >- Errored cells per column ID. A column with no failures is absent — read absence as zero. What the column header's error badge shows. propertyNames: format: uuid title: Failed Cells By Column type: object filled_cells_by_column: additionalProperties: type: integer description: >- Cells holding a stored value, per column ID. A column with no filled cells is absent — read absence as zero. How much of the column has DATA in it, which is not how much of it is DONE — for that, and for the breakdown behind it, read `cell_settlement_by_column`. propertyNames: format: uuid title: Filled Cells By Column type: object last_run_at_by_column: additionalProperties: format: date-time type: string description: >- When each column last produced a value. Derived from its newest computed cell — a column absent here has never run. Not the column's updated_at, which moves when it is merely renamed. propertyNames: format: uuid title: Last Run At By Column type: object row_count: title: Row Count type: integer required: - row_count - columns_by_kind - failed_cells - failed_cells_by_column - filled_cells_by_column - active_run - at_row_cap title: TableStatsSchema 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 TableRunReadSchema: description: A table recompute run with its static denominator and monotone counters. properties: cells_done: description: >- Cells processed so far; clamped to cells_total so the banner can never overshoot. title: Cells Done type: integer cells_failed: description: Cells whose formula evaluation failed. title: Cells Failed type: integer cells_no_data: description: >- Cells that ran clean but found nothing. Free, never retried, and excluded from errored views. Counted within cells_done. title: Cells No Data type: integer cells_skipped: description: >- Cells the run deliberately skipped — a missing required input or a false run condition. Counted within cells_done. title: Cells Skipped type: integer cells_total: description: Exact static denominator, fixed when the run plan is minted. title: Cells Total type: integer column_id: anyOf: - format: uuid type: string - type: 'null' description: >- The column a column-lineage run recomputes, parsed from its workflow identity; null for whole-table runs. Narrows the grid's busy paint to one column — `row_scope` is what narrows it to the rows within that column. title: Column Id completed_at: anyOf: - format: date-time type: string - type: 'null' title: Completed At created_at: format: date-time title: Created At type: string error: anyOf: - type: string - type: 'null' description: Failure description when the run status is failed. title: Error export_retry_attempt: default: 0 description: >- How many automatic export retries preceded this run. 0 is a run a person or a schedule asked for; higher values mark the follow-ups queued for rows whose push failed for a retryable reason, so a run history can tell 'we tried again' from 'you ran it again'. title: Export Retry Attempt type: integer id: format: uuid title: Id type: string row_scope: $ref: '#/components/schemas/TableRunRowScopeReadSchema' description: >- The rows this run resolved to at mint. Present on every read so a resync cannot lose it and silently fall back to painting the whole column busy. started_at: anyOf: - format: date-time type: string - type: 'null' title: Started At status: $ref: '#/components/schemas/TableRunStatus' description: The run's lifecycle status. table_id: format: uuid title: Table Id type: string trigger: $ref: '#/components/schemas/TableRunTrigger' description: What kind of mutation requested the run. required: - id - table_id - trigger - status - cells_total - cells_done - cells_failed - cells_skipped - cells_no_data - error - created_at - started_at - completed_at - row_scope title: TableRunReadSchema type: object CellSettlementSchema: description: >- One column's cells, split by how their last attempt ended. FILLED IS NOT COMPLETE, and reading them as the same number is the bug this shape exists to end. ``filled`` is a storage fact: the cell holds a value. ``complete`` is a work fact: the last attempt reached a verdict, nothing has invalidated it since, and no stopped run still owes a recompute. They diverge in both directions. An enrichment that ran cleanly and found nothing is complete and empty, which on an AI column is the ordinary case; a cell holding last week's value under an edited formula is filled and incomplete. Every figure counts only cells that HAVE a stored row. A cell nothing has ever attempted has no row at all, so a column's outstanding work is ``row_count`` minus ``complete``, not a number reported here. properties: complete: description: >- Cells with nothing owed on them: a terminal verdict, still fresh, and not awaiting a recompute a stopped run never delivered. Excludes failures, which a retry can still fill. title: Complete type: integer failed: description: Cells that ran and errored. Retryable, so not complete. title: Failed type: integer filled: description: Cells holding a value in some typed slot. title: Filled type: integer no_data: description: >- Cells that ran cleanly and produced nothing. A definitive answer about this row rather than an incident, and never charged. title: No Data type: integer skipped: description: >- Cells deliberately held back: a required input was empty, or the run condition was false. title: Skipped type: integer stale: description: >- Cells whose inputs changed after they were computed. Cuts across the other counts: a stale cell still shows its old value. title: Stale type: integer succeeded: description: Cells that ran and produced a value. title: Succeeded type: integer required: - filled - complete - succeeded - no_data - skipped - failed - stale title: CellSettlementSchema 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 TableRunRowScopeReadSchema: description: >- The rows a run resolved to — what lets a client mark exactly those busy. ``record_ids`` is populated for the ``record_ids`` kind alone. ``all_rows`` and ``unlisted`` both mean "assume every row": the first because it is true, the second because the set was too large to carry on every frame. Collapsing them keeps a client's fallback one branch rather than two. properties: kind: $ref: '#/components/schemas/TableRunScopeKind' description: How the resolved row set is published. record_ids: anyOf: - items: format: uuid type: string type: array - type: 'null' description: The exact rows the run will touch; null unless kind is record_ids. title: Record Ids rows: anyOf: - type: integer - type: 'null' description: Rows the resolved scope covers; null for all rows. title: Rows required: - kind - rows - record_ids title: TableRunRowScopeReadSchema type: object TableRunStatus: description: >- Lifecycle status of a table run. ``PENDING`` exists for API compatibility but is never observed — runs are born ``RUNNING`` at mint. ``CANCELLING`` is the requested-stop state the page activities observe; the workflow finalizes it to ``CANCELLED``. enum: - pending - running - cancelling - cancelled - paused_for_credits - completed - completed_with_errors - failed title: TableRunStatus type: string TableRunTrigger: description: What kind of mutation requested a recompute run. enum: - cell_edited - row_added - row_manual - column_added - column_edited - column_manual title: TableRunTrigger type: string TableRunScopeKind: description: >- How a minted run's RESOLVED row set is published to readers. Distinct from :class:`TableRunScope`, which is what the caller ASKED for. The two disagree routinely — ``ALL`` on a ``keep_existing_results`` table is silently narrowed to the unfilled rows at mint — and only the resolved set can be painted, so only the resolved set is stored. ``UNLISTED`` is a real row subset whose ids were too many to carry on every changefeed frame (see ``max_persisted_scope_rows``). It reads exactly like ``ALL_ROWS`` to a client: assume every row. That keeps the fallback one branch rather than two, at the cost of over-painting the rare huge partial. enum: - all_rows - record_ids - unlisted title: TableRunScopeKind type: string securitySchemes: HTTPBearer: scheme: bearer type: http APIKeyHeader: in: header name: X-API-Key type: apiKey ````