List Bridge Rows
List the rows of a single Bridge — the concrete matches the Bridge has produced — with optional filtering, sorting, and full-text search. Each row carries a processing status, optional buyer/organizer association, an updatedAt timestamp, and the per-column values populated for that match. The per-row columns map is keyed by the human-readable column name (not by columnId), and values are polymorphic per the column’s fieldFormat (string / number / boolean / object / null).
Prefer narrowing server-side with filters, sorts, and query in the request body over scanning every page.
For any column-targeted filter or sort — including Match Score, Match reasoning,
and any user-defined column — first call getBridgeColumnMetadata to obtain that
column’s columnId UUID and pass it as BridgeFilters.terms[].field or
RowSort.column. The column’s display name, key, or any prefixed reference is
NOT a valid value. A small set of common entry-level fields (status, buyerId,
opportunityId, entryName, triggeredAt) is also accepted for filtering.
Sort or filter columns that are not mapped on the server return 400. See
ListBridgeRowsRequest for the full schema of supported filter terms,
operations, and sort columns.
To paginate, start at pageNumber=1 and increment until pageNumber == totalPages.
Note on consistency: the data backing search/sort/filter is maintained separately from the row values returned here, and the two can briefly drift apart — especially while the service is under heavy load. As a result, recent changes (new rows, status changes, updated column values, updatedAt, etc.) may not be reflected in listing, sorting, or filtering immediately; they usually become consistent within a short time. If a just-changed row does not appear where you expect, retry shortly.
Authorizations
HTTP Bearer Authentication
Path Parameters
Query Parameters
Page number, 1-based. Minimum 1.
Page size. Must be > 0 and <= 100. Prefer <= 20.
Body
Filtering, sorting, and free-text search parameters for bridge rows. Refer to examples for proper usage.
Filter criteria for bridge rows. All `terms` are combined with logical AND — a row must
satisfy every term to be included. Provide an empty `terms` list (or omit `filters`) to
return all rows.
Sort specification for rows. For each sort term, `column` should be a bridge
column's `columnId` UUID — call `getBridgeColumnMetadata` to look it up. The
column's display name, `key`, or any prefixed reference is not a valid value.
A small set of common entry-level fields (`entryId`, `entryName`, `triggeredAt`)
is also accepted but discouraged. The synthetic column `rowUpdatedAt` sorts by when
the row was last updated — sort `DESC` to poll for recently-changed rows, matching the
`updatedAt` field in the response. Sort columns that are not mapped on the server return 400.
Full-text search query