Get Bridge
Fetch the summary of a single Bridge by ID — name, owner, filter type, current status, last-updated timestamp, and total row count. A Bridge watches for one type of buyer activity — RFPs, meetings, purchases, conferences, contact or job changes, or other signals — within a buyer-list scope, extracts a configurable set of column values when something matches, and stores each match as a row.
For what the Bridge is configured to look for — the buyer scope it watches, the search filters/queries it runs, and the match/scoring criteria — call getBridgeConfiguration. For the per-column schema (columnId, name, prompt, type, fieldFormat, etc.) needed to construct column-targeted filters in listBridgeRows, call getBridgeColumnMetadata.
Response
Bridge details
Type of filter applied to the bridge — also what each of its rows represents, surfaced per row as entity. RFP bridges match RFPs.
RFP, Meeting, Purchase, Buyer, AccountScoring, Contact, Signal, Conference, JobChange, VendorPresence, ProductCompetitorPresence, CompanionPresence Lifecycle status. Initializing and Matching mean the bridge is still building its rows, Open means it is live, Failed means the build failed, Draft means it was never started. An imported bridge (isImported) waits in Draft, with no rows, until its contacts' buyer matches are reviewed and completed.
Initializing, Matching, Draft, Open, Failed, Deleting True when the bridge was built from a list of contacts the user imported rather than from a search: it holds only those contacts and never picks up rows on its own, though its rows follow later updates to the matched contacts. It cannot be rebuilt or duplicated, and of its configuration only the name and description can change. Adding or removing its rows by hand turns it Manual (isManual) for good.