--- title: "Count what a new filter does to the sequences that follow a view" method: POST path: "/tables/{table_id}/views/{view_id}/sequence-impact/" tags: ["table-views"] --- # Count what a new filter does to the sequences that follow a view `POST /tables/{table_id}/views/{view_id}/sequence-impact/` ## Request - Base URL: `https://api.getoneprofile.ai` (the document declares no server; this is the origin it was published from) - URL: `https://api.getoneprofile.ai/tables/{table_id}/views/{view_id}/sequence-impact/` - Auth: one of: - API key in header `X-API-Key` - HTTP bearer Before a view's filter is saved, says for each draft, running or paused sequence that reads its contacts through the view how many contacts the new filter adds, removes (they stop, reading Left the audience) and leaves unchanged. Saving the filter applies it to those sequences at once. A sequence that does not keep in sync with its table ignores the edit and carries no counts. Writes nothing. A POST for the same reason the rows query is one: a filter list has no honest query-string encoding. ## Path parameters - `table_id` string, uuid, required - `view_id` string, uuid, required ## Request body - TableViewSequenceImpactRequestSchema: The filter a view would be saved with, to count what it does to its sequences. - `where` TableRowsWhereSchemaInput: 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, so "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. - `items` TableRowWhereItemSchemaInput[], required: Conditions and groups. - union - TableRowFilterSchemaInput: 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. - `column_id` union, required: A column ID, or `__any_column__` to ask about every cell in the row at once. `__any_column__` takes only `has_error` and `has_no_error`. - string, uuid - '__any_column__' | '__record_id__': The filter targets that name the whole ROW rather than one column. ``ANY_COLUMN`` asks a question of every cell in the row at once: "does any column have an error?" is the table-wide half of the per-column ``has_error``. It stands in the ``column_id`` slot of an ordinary condition (the same trick the system sort keys use), so a row-wide question travels through every surface that already carries a predicate tree (a saved view, a run's scope, an export, a count) with nothing to add to any of them. The dunder spelling keeps it apart from any UUID. - `operator` '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', required: 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. - `type` 'condition' - `value` union - string - integer - number - boolean - string, date-time - string, date - CellValueInput[] - object - TableRowFilterGroupSchemaInput: 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. - `conditions` TableRowFilterSchemaInput[], required: The conditions inside the parentheses. - `column_id` union, required: A column ID, or `__any_column__` to ask about every cell in the row at once. `__any_column__` takes only `has_error` and `has_no_error`. - … - `operator` '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', required: 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. - `type` 'condition' - `value` union - … - `joiner` 'and' | 'or': How the members of one filter level combine. - `type` 'group' - `joiner` 'and' | 'or': How the members of one filter level combine. ## Response `200` Successful Response - TableViewSequenceImpactListSchema: Every unfinished sequence that reads its contacts through the view, by id. - `sequences` TableViewSequenceImpactSchema[], required - `capped` boolean, required: The view matches more rows than the counts read; added is at least this. Removed and not changed are exact. - `diff` AudienceDiffReadSchema, required: What an audience change does to who is in progress: pending, active, waiting or paused. - `added` integer, required: Contacts in progress after the change who are not now: new contacts, contacts back where they left off, and when starting fresh everyone who starts at step one. When the counts are capped, the new contacts are only the rows read: at least this many. - `not_changed` integer, required: Every other contact already in the sequence. Exact. - `pauses_sending` boolean, required: Applying it pauses a running sequence first. A filter change never does. - `removed` integer, required: Contacts in progress now who stop, reading Left the audience. Exact at any table size. - `follows_table` boolean, required: The sequence keeps in sync with the table. A fixed list ignores a filter edited here, so it has no diff. - `name` string, required - `sequence_id` string, uuid, required - `status` 'draft' | 'running' | 'paused' | 'completed', required: Lifecycle of a sequence. DRAFT until launch; RUNNING sequences are locked against structural edits (pause → edit → resume); PAUSED stops scheduling while leaving every enrolment exactly where it is; COMPLETED is terminal. ## Other responses - `401`: Unauthorized - `403`: Forbidden - `404`: Table not found - `422`: Invalid request made to the API. - `500`: Internal server error. - `502`: Bad gateway error. - `503`: Service unavailable. --- [API](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile.md) · [All operations](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/llms.txt) · [OpenAPI document](https://skmtc.dev/getoneprofile/apis/api-reference-oneprofile/revisions/4a6bd71e3f02?raw)