> ## 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. # Query table rows > List a table's rows with keyset pagination on an opaque cursor. Without a sort, rows come in DISPLAY order — the user-controlled row position, with the time-ordered record ID as a tiebreak. With one, they come in that column's value order, and rows with no value for it sort LAST in both directions. Filters are predicates on cell values and compose with either order. `column_ids` projects each row's cells: send the columns the grid will render and the response carries only those. It echoes the projection back, so a column outside it reads as 'not fetched' rather than 'blank'. A POST because a filter list has no honest query-string encoding. Each cell's computing flag is derived: stale AND an active run covers that row. Performance note: an unfiltered sort streams the column's index. Add a filter and Postgres sorts the matched set instead, so a filter that matches most of a very large table is correspondingly slower. ## OpenAPI ````yaml /openapi.json post /tables/{table_id}/rows/query/ 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}/rows/query/: post: tags: - table-rows summary: Query table rows description: >- List a table's rows with keyset pagination on an opaque cursor. Without a sort, rows come in DISPLAY order — the user-controlled row position, with the time-ordered record ID as a tiebreak. With one, they come in that column's value order, and rows with no value for it sort LAST in both directions. Filters are predicates on cell values and compose with either order. `column_ids` projects each row's cells: send the columns the grid will render and the response carries only those. It echoes the projection back, so a column outside it reads as 'not fetched' rather than 'blank'. A POST because a filter list has no honest query-string encoding. Each cell's computing flag is derived: stale AND an active run covers that row. Performance note: an unfiltered sort streams the column's index. Add a filter and Postgres sorts the matched set instead, so a filter that matches most of a very large table is correspondingly slower. operationId: query_table_rows parameters: - in: path name: table_id required: true schema: format: uuid title: Table Id type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/TableRowsQueryRequestSchema' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/TableRowsPageSchema' 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: TableRowsQueryRequestSchema: description: >- Request body for the rows query. A POST rather than a GET because a filter list has no honest query-string encoding. ``column_ids`` is the projection: send the columns the grid will actually render and the response carries only those cells. properties: column_ids: anyOf: - items: format: uuid type: string maxItems: 500 type: array - type: 'null' description: >- Project each row's cells to these columns. Omit for every column. The response echoes the projection in `column_ids` so a client can tell a blank cell from one it did not ask for. title: Column Ids cursor: anyOf: - maxLength: 1024 type: string - type: 'null' description: Opaque cursor from a previous page's next_cursor. title: Cursor limit: default: 100 description: Maximum rows per page. maximum: 100 minimum: 1 title: Limit type: integer offset: anyOf: - minimum: 0 type: integer - type: 'null' description: >- Start the listing this many rows in, rather than at the top: a jump-to-row seek. Mutually exclusive with `cursor`, which resumes a listing rather than starting one. Postgres walks the skipped rows, so this is for a deliberate jump — keep paging with `next_cursor`. title: Offset record_ids: anyOf: - items: format: uuid type: string maxItems: 1000 type: array - type: 'null' description: >- Hydrate exactly these rows, instead of describing a listing. Mutually exclusive with `sorts`, `where`, `row_status`, `offset` and `cursor` — those select rows, and this names them. Pair with `/rows/ids/` to fetch an ordering once and then fill in row contents a window at a time, which lets re-sorting or re-filtering reuse cells the client already holds. title: Record Ids row_status: anyOf: - $ref: '#/components/schemas/TableRowStatus' - type: 'null' description: >- Restrict to rows whose CELLS are in a given state: `errored` (any cell failed to compute) or `fully_computed` (none did). ANDed with `where`. This is a question about computation, which the filter operators — all of which test one column's value — cannot ask. sorts: description: >- Order by these columns, in priority order, instead of the display order. Blanks sort last for every key, whichever way that key runs. items: $ref: '#/components/schemas/TableRowSortSchema' maxItems: 3 title: Sorts type: array where: anyOf: - $ref: '#/components/schemas/TableRowsWhereSchema-Input' - type: 'null' description: >- The predicate tree every returned row must satisfy. Omit for an unfiltered listing. title: TableRowsQueryRequestSchema type: object TableRowsPageSchema: description: One keyset page of table rows. properties: column_ids: anyOf: - items: format: uuid type: string type: array - type: 'null' description: >- The columns whose cells this page carries, or null for all of them. A column outside this list is NOT blank — it was simply not fetched. title: Column Ids has_more: title: Has More type: boolean limit: title: Limit type: integer next_cursor: anyOf: - type: string - type: 'null' description: Cursor for the next page; None when this is the last page. title: Next Cursor rows: items: $ref: '#/components/schemas/TableRowSchema' title: Rows type: array required: - rows - column_ids - next_cursor - has_more - limit title: TableRowsPageSchema 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 TableRowStatus: description: >- A row-level state, derived from its cells rather than stored. ``ERRORED`` is "any cell of this row failed to compute"; ``FULLY_COMPUTED`` is its exact complement, so the two partition the table. Serves the built-in smart views, which are questions about computation rather than about values — the ordinary filter vocabulary cannot express either. enum: - errored - fully_computed title: TableRowStatus type: string TableRowSortSchema: description: The column a rows query is ordered by, and which way. properties: column_id: format: uuid title: Column Id type: string direction: $ref: '#/components/schemas/TableSortDirection' default: asc description: Ascending or descending. required: - column_id title: TableRowSortSchema type: object TableRowsWhereSchema-Input: description: >- The whole predicate for a rows query. ``items`` mixes conditions with groups under one joiner, so ``A and (B or C)`` is an AND over ``[A, group(OR, [B, C])]``. Send no ``where`` at all rather than an empty one — "no filter" stays a single state. The cap is on LEAVES, not on items: eight conditions cost eight correlated EXISTS clauses whether they are grouped or not, and it is the clause count that the query planner pays for. properties: items: description: Conditions and groups. items: $ref: '#/components/schemas/TableRowWhereItemSchema-Input' maxItems: 8 minItems: 1 title: Items type: array joiner: $ref: '#/components/schemas/TableFilterJoiner' default: and description: How the top-level items combine. required: - items title: TableRowsWhereSchema 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 TableSortDirection: description: Which way a sorted row listing runs. enum: - asc - desc title: TableSortDirection type: string TableRowWhereItemSchema-Input: oneOf: - $ref: '#/components/schemas/TableRowFilterSchema-Input' - $ref: '#/components/schemas/TableRowFilterGroupSchema-Input' TableFilterJoiner: description: How the members of one filter level combine. enum: - and - or title: TableFilterJoiner type: string 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 TableRowFilterSchema-Input: description: >- One predicate a row must satisfy. Which operators apply depends on the column's type — a range comparison on a checkbox is rejected rather than silently matching nothing. The valueless operators (``is_empty``, ``is_not_empty``, ``is_true``, ``is_false``) must not carry a value. properties: column_id: format: uuid title: Column Id type: string operator: $ref: '#/components/schemas/TableFilterOperator' type: const: condition default: condition title: Type type: string value: anyOf: - $ref: '#/components/schemas/CellValue-Input' - type: 'null' description: The operand; omitted for the valueless operators. required: - column_id - operator title: TableRowFilterSchema type: object TableRowFilterGroupSchema-Input: description: >- A parenthesised run of conditions, joined among themselves. Holds conditions and never groups: one level of nesting is expressible and a second is not, structurally. That covers ``A and (B or C)`` — what a filter panel offers — while keeping the SQL a flat walk. properties: conditions: description: The conditions inside the parentheses. items: $ref: '#/components/schemas/TableRowFilterSchema-Input' maxItems: 8 minItems: 1 title: Conditions type: array joiner: $ref: '#/components/schemas/TableFilterJoiner' default: and description: How this group's conditions combine. type: const: group default: group title: Type type: string required: - conditions title: TableRowFilterGroupSchema 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 TableFilterOperator: description: >- A row filter predicate. Which operators are legal depends on the column's data type; the service validates the pairing and rejects a mismatch, so an operator here is a vocabulary entry rather than a promise it applies everywhere. Two families live here. The VALUE operators ask about what a cell holds and are keyed off the column's storage slot. The STATE operators ask about what the last run DID to the cell — errored, skipped, never ran, went stale — and are keyed off the column's kind instead: they read the compute metadata that only a computed column ever writes, and mean nothing on a hand-typed one. enum: - eq - neq - gt - gte - lt - lte - contains - not_contains - contains_any_of - not_contains_any_of - starts_with - is_true - is_false - is_empty - is_not_empty - has_error - has_no_error - has_results - has_no_results - has_not_run - is_stale - is_not_stale - run_condition_not_met - run_stopped title: TableFilterOperator type: string 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 securitySchemes: HTTPBearer: scheme: bearer type: http APIKeyHeader: in: header name: X-API-Key type: apiKey ````