Skip to main content
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.
The person on the other side (target_*) is the one the row is about either way. In both directions, everyone at your customers is kept, whatever their title; at every other account, only people who match your buyer titles. 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. Offset-paginated: pass the previous response’s next_offset as offset until has_more is false.

Authorizations

Authorization
string
header
required

The API key you created on the API settings page of the Clustr app.

Query Parameters

competitor_id
string

Keeps the interactions with this tracked competitor, by its Clustr ID (cmp_…). Repeat the parameter for several competitors (?competitor_id=a&competitor_id=b), or leave it out for every competitor. The id from earlier responses also works.

from
string<date-time>

The start of the time window, as an RFC 3339 timestamp, for example 2026-07-01T00:00:00Z.

to
string<date-time>

The end of the time window, as an RFC 3339 timestamp.

crm
enum<string>

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 client list, so it returns nothing while your client 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
critical
enum<string>

critical_only keeps only the interactions flagged critical; all keeps every interaction.

Available options:
all,
critical_only
type
enum<string>

Keeps the interactions of this kind: comment, like or share. Repeat the parameter for several kinds.

Available options:
comment,
like,
share
role
enum<string>

Keeps the interactions by a competitor salesperson in this role: bdr, ae, am, csm, exec, founder or other. Repeat the parameter for several roles.

Available options:
bdr,
ae,
am,
csm,
exec,
founder,
other
seniority
enum<string>

Keeps the interactions by a competitor salesperson at this seniority: high, mid, low or unknown. Repeat the parameter for several levels.

Available options:
high,
mid,
low,
unknown
target
string

Keeps the interactions with one engaged person, by their Clustr ID (per_…) or their LinkedIn id. Use it to open one person from List Engaged Prospects.

account
string

Keeps the interactions at one account, by its Clustr ID (acc_…) or its LinkedIn numeric company id (company_numeric_id on List Competitor Accounts). Any other value answers 400.

direction
enum<string>

Keeps one direction: outbound (the salesperson engaged the person's post) or inbound (the person engaged the salesperson's own post). Leave it out for both.

Available options:
outbound,
inbound
intent
enum<string>

Keeps the interactions on a post that shows buying intent: any, or one intent, hiring_for, evaluating, migrating, rfp or budget_or_project. Each entry's intent_label and intent_reason say which intent the person's post shows. Leave it out for every interaction.

Available options:
any,
hiring_for,
evaluating,
migrating,
rfp,
budget_or_project
order
enum<string>

recent sorts newest first and seniority ranks by the engaging salesperson's seniority. Leave it out for the default threat ranking.

Available options:
recent,
seniority
limit
integer

The number of interactions per page, at most 200.

offset
integer

The number of interactions to skip, for the next page.

Response

A page of interactions

success
boolean
required
Example:

true

data
object
required