List Company Events
Returns Events this company participates in, newest first. This is the same contract as GET /api/v1/events, scoped to a single company by the path. Plan gating, ordering, updated_after sync (including merge/removal tombstones for this company), and cursor semantics all match the flat resource; see its documentation for the full detail.
A tombstone respects the same event-grain filters as the flat resource, including last_article_after/before. A merged event’s last_article_at freezes at merge time, so those filter a tombstone against that frozen value rather than against when the merge happened. window cannot be used for sync polling (mutually exclusive with updated_after).
Parameters that name or describe a different company or listing are rejected here with 400 invalid-parameter: company, ticker, watchlist, listed, exchange, market, domicile, index and sector. The path already fixes the company; use GET /api/v1/events to filter the full collection by any of them. watchlist=false and listed with any value other than true remain inert. mode is rejected with 400 invalid-parameter; use GET /api/v1/events?company={company_id}&q={query}&mode=semantic to search one company’s events by meaning.
Responses carry an ETag and Cache-Control: private, max-age=0, must-revalidate; send the ETag back as If-None-Match to receive a 304 Not Modified. There is no Last-Modified, so If-Modified-Since alone never revalidates. This is the same contract, and the same reason, as GET /api/v1/events. Requests carrying q or updated_after are not cached and return Cache-Control: no-cache, no-store.
Authorizations
API Key authentication using Bearer token
Headers
ETag value from a previous response. Returns 304 Not Modified if data has not changed.
Path Parameters
Company ID or ticker symbol. Accepts the exchange-suffixed form (e.g. VOLV-B.ST); former tickers resolve too. When a ticker is shared by more than one company, the company with a listing on a Nordic exchange is returned, then the one with an active listing, then the most recently listed. Use the company ID for an unambiguous lookup.
Query Parameters
Number of events to return per page (default 25, max 100).
Opaque pagination cursor from a previous response. Works with q too; q is a filter, not a separate search mode. When continuing an updated_after sync, resend the same updated_after value.
Comma-separated list of fields to include in the response. id is always included.
ISO 8601 datetime. Returns only this company's events updated after this timestamp, including merge/removal tombstones. Use for incremental sync.
Full-text filter over the event's own title and summary as well as its live member articles' indexed content (title, summary, key points, plus tagged company names and key facts), so an event can match on a company its coverage only tags. Matches stay in the default feed order (most recently reported first) and are cursor-paginated like any other request; combine with window/last_article_after for "latest on X".
Filter by event type slug, comma-separated. These are Events taxonomy slugs (hyphenated) from GET /api/v1/event_types and are the only values accepted here. The underscored calendar event_type values used by GET /api/v1/calendar_events are rejected. A few spellings overlap across the two vocabularies (e.g. delisting) while denoting different things. An unrecognized slug returns 400 naming the bad slug(s).
Editorial importance, the feed's materiality threshold, comma-separated (e.g. notable,routine). Valid values: notable (material, front-page-worthy events), routine (ledger records: routine filings, scheduled disclosures), commentary (opinion/analysis pieces). Use significance=notable to restrict the feed to material events. An unrecognized value returns 400 naming the bad value(s).
Sort order. latest (default) sorts most recently reported first, the unfiltered feed order. significance groups events into 3 coarse editorial tiers (notable, then routine, then commentary), most recently reported first within each tier; expect large ties within a tier. A mid-walk routine→notable escalation may be skipped, since the ordering is a best-effort snapshot. For a broad importance filter, prefer significance=notable with the default sort; page 1 is identical. Mutually exclusive with updated_after (an unrecognized value, or either sort value combined with updated_after, returns 400).
Filter to events with a live member article from this country (ISO 3166-1 alpha-2, comma-separated). Applied at the article grain, so sync tombstones do not respect it.
Filter to events with a live member article in any of these categories, by their id (comma-separated; unknown ids are ignored). Applied at the article grain, so sync tombstones do not respect it.
Filter to events with a live member article from these sources, by their id (comma-separated, max 25). Applied at the article grain, so sync tombstones do not respect it.
ISO 8601 datetime. Only events first reported at or after this time.
ISO 8601 datetime. Only events first reported before this time.
ISO 8601 datetime. Only events whose most recent activity (last_article_at, or first_reported_at when that is null) is at or after this time. Mutually exclusive with window.
ISO 8601 datetime. Only events whose most recent activity is before this time. Mutually exclusive with window.
Relative shorthand for last_article_after, e.g. 8h, 24h, 7d (hours or days only, max 365d equivalent). Evaluated per request against the server clock. Mutually exclusive with last_article_after, last_article_before, and updated_after.
Filter to events with a live member article from this source type, comma-separated. Valid values: news_publication, wire_service, press_release, government, trade_publication, blog, stock_exchange, research. Articles from disabled sources are excluded. Applied at the article grain, so sync tombstones do not respect it. An unrecognized value returns 400 naming the bad value(s).
Filter to events with a live member article of this content type, comma-separated. Valid values: news, analysis, press_release, market_commentary, market_news, trading_halt, trading_event, other. Applied at the article grain, so sync tombstones do not respect it. An unrecognized value returns 400 naming the bad value(s). Content type is an AI-assigned label per article. To find events with a member article from a primary disclosure source, filter on source_type (wire_service, stock_exchange, press_release, government) instead.
Filter to commentary events that comment on or react to the factual event with this id. Unresolvable id returns an empty result set, not an error.
When true, widen this feed, and the company_ids returned on each event, to events where this company has a peripheral role (advisor, speaker, or a passing mention) as well. Default false restricts to an active-involvement role (subject, acquirer, target, investor, issuer, partner).