Company Signal Events
Enriched, paginated drill-down into the signal events driving a single company’s expansion.
Authorizations
Body
- Domain Search ID
- Domain
- LinkedIn URL
A unique identifier for the company search operation.
Filter to specific signal types.
AD, NEWS, INFRA, PARTNER, EVENT_PLUS, EXEC, OFFICE, HIRE, SCALE, PRODUCT ["EXEC", "HIRE"]Optional. Scope the feed to one or more foreign markets (ISO 3166-1 alpha-2, e.g. ["JP","SG"]). Omitted → all foreign markets (the home market is always excluded).
["JP", "SG"]ISO [from, to] date range for the signal/transition window. Takes precedence over window_days when both are supplied.
["2026-04-01", "2026-06-29"]Optional. Size of the rolling events window in days. Defaults to 90 (the standard display window) when neither this nor transitioned_dates is supplied. transitioned_dates takes precedence when both are sent.
90
Plain-language description of what you sell, or the buyer profile you're evaluating this company against. Used only to ground the AI summary (see is_explain_match); unlike the company search, it is NOT interpreted into filters here.
"We sell Employer-of-Record and local payroll; best-fit buyers hire in a new market before setting up a legal entity."
When true and a query is supplied, data.summary returns a single AI summary of this company's expansion activity read against your query, grounded in the company's real signals with [n] citations. Unlike the company search's per-company match_summary, this summary is built from the company's ENTIRE feed for the window (all markets, every signal), so it is stable regardless of page / per_page.
true
A company domain used for company search operations. If we receive a URL such as www.pubrio.com or https://docs.pubrio.com/, the system will convert it to pubrio.com for processing.
"pubrio.com"
The fully formed URL of the LinkedIn company profile. URL begin with http and contain linkedin.com/company/
"https://www.linkedin.com/company/pubrio"
The page number of the Pubrio data that you want to retrieve.
1
The number of search results that should be returned for each page. Limited the number of results per page improves the endpoint's performance.
25
Optional. An identifier for the user profile (workspace) making the request. This is no longer required as the API key already includes your workspace information. If provided, it helps in associating the lookup with a specific user, allowing for data retrieval and credit tracking.
Check out user details endpoints under the Profile tab for more information.

