Competitor Monitoring
List Competitor Interactions
The Signals feed, every competitor-rep interaction with a person at one of your accounts
GET
The Signals feed. One row per interaction (comment, reaction, share) between a tracked competitor’s rep and a person at one of your accounts, across every competitor you monitor.
Both directions are covered, and each row says which in
direction:
outbound: the rep commented on or liked the person’s post.inbound: the person commented on or liked the rep’s own post.
target_*) is the one the row is about either way. In both directions, only people who match your buyer titles are kept, at your customers as at every other account.
Each row carries who did it, who they engaged, that person’s company, the ICP verdict, your live CRM state for the account (in CRM, open deal, owner) and the comment classifier’s is_critical verdict with the reason it gave. This is the row data behind the Signals table in the app, with the same filters.
Rows are ranked open-deal → in-CRM → critical → recency. Pass order=recent for a pure newest-first log, or order=seniority to rank a founder’s like above an SDR’s.
Each row is shown under one competitor: competitor_id is the one your competitor_id filter picked, else the first, and competitor_ids lists every competitor the rep is tracked under. Repeat competitor_id to keep several competitors.
Offset-paginated: pass the previous response’s next_offset as offset until has_more is false.
Authorizations
Query Parameters
Keeps interactions by the state of the engaged person's company in your CRM: all, in_crm, not_in_crm, open_deal or customer.
customer keeps only the accounts you already own, the companies on your customer list, so it returns nothing while your customer list is empty. Use it for a retention view, where a competitor working one of your customers calls for a different response than one working a prospect.
Available options:
all, in_crm, not_in_crm, open_deal, customer