> ## 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 a listing's row IDs > Get the record IDs a listing selects, in order, carrying NO cell data. Takes the same `sorts`, `where` and `row_status` vocabulary as the rows query and answers only the membership-and-order half of it. Pages are correspondingly large — the default is 10,000 IDs — because a page of IDs is a fraction of the size of a page of rows. Pair it with the rows query's `record_ids` mode: fetch an ordering once, then hydrate contents a window at a time. A client holding both can re-sort or re-filter by refetching only the ordering, and reuse every cell it already has. A POST for the same reason the rows query is one: a filter list has no honest query-string encoding. ## OpenAPI ````yaml /openapi.json post /tables/{table_id}/rows/ids/ 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/ids/: post: tags: - table-rows summary: Query a listing's row IDs description: >- Get the record IDs a listing selects, in order, carrying NO cell data. Takes the same `sorts`, `where` and `row_status` vocabulary as the rows query and answers only the membership-and-order half of it. Pages are correspondingly large — the default is 10,000 IDs — because a page of IDs is a fraction of the size of a page of rows. Pair it with the rows query's `record_ids` mode: fetch an ordering once, then hydrate contents a window at a time. A client holding both can re-sort or re-filter by refetching only the ordering, and reuse every cell it already has. A POST for the same reason the rows query is one: a filter list has no honest query-string encoding. operationId: query_table_row_ids parameters: - in: path name: table_id required: true schema: format: uuid title: Table Id type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/TableRowIdsQueryRequestSchema' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/TableRowIdsPageSchema' 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: TableRowIdsQueryRequestSchema: description: >- Request body for the row-ID manifest. The same listing vocabulary as the rows query, minus the projection: this asks which rows a listing selects and in what order, not what is in them. Answering it reads no cell payload, so a client can hold a whole table's ordering cheaply and then hydrate only the window it is showing. properties: cursor: anyOf: - maxLength: 1024 type: string - type: 'null' description: Opaque cursor from a previous page's next_cursor. title: Cursor limit: default: 10000 description: >- Maximum record IDs per page. Far higher than the rows query's limit because a page of IDs carries no cells. maximum: 10000 minimum: 1 title: Limit type: integer offset: anyOf: - minimum: 0 type: integer - type: 'null' description: >- Start the listing this many rows in. Mutually exclusive with `cursor`. title: Offset row_status: anyOf: - $ref: '#/components/schemas/TableRowStatus' - type: 'null' description: Restrict to rows whose cells are `errored` or `fully_computed`. sorts: description: Order by these columns, in priority order, instead of display order. 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. title: TableRowIdsQueryRequestSchema type: object TableRowIdsPageSchema: description: One keyset page of a listing's record IDs, in order. properties: 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 record_ids: items: format: uuid type: string title: Record Ids type: array required: - record_ids - next_cursor - has_more - limit title: TableRowIdsPageSchema 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 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 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 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 ````