Events · US only

Major shareholder ownership events

GET/api/v2/events-ownershipUS only

Coverage: US (classification enums unified across markets)
Billing: 20 cr / thousand calls

One row = one filing that discloses a major shareholder's ownership status (event_class = ownership), with the shareholder as the subject and the company as the object: crossing the reporting threshold (stake_change), a share pledge / freeze (share_pledge), a lock-up expiry (lock_up_expiry). Only stake_change, from 13D/G filings, currently has data; the share_pledge / lock_up_expiry enums are reserved and carry data only once the corresponding markets are connected; filtering on these two types returns an empty array today. Day-to-day insider trades are not covered here; /insider-trades.

The ownership percentage is a response field only; there is no range filter on it.
The endpoint does not offer cross-company queries by shareholder name (there is no holder= parameter), preventing cross-company shareholder profiling.
direction / intent / action / share_source are flattened out of the envelope axis, and each carries a value only on its own type.

Shared events conventions

Ad hoc corporate disclosure events: financings, deals and agreements, executive changes, corporate actions, changes in major shareholder holdings, and more. Classification is not broken out by each market's regulatory forms; it is defined by "what about the company changed": the source category code is preserved as-is in source_category, and the public contract uses one canonical set of event_class / event_type (9 classes / 42 types; see OpenAPI for the full enums and each type's fields). Onboarding a new market only adds mappings; the endpoints are unchanged.

The data covers only US-listed companies: a non-US ticker returns 404; when ticker is omitted, the endpoint scans all companies on record. The six endpoints share one parameter set and one set of common envelope fields. /events is the unified timeline that carries only the common envelope; each of the five typed endpoints serves one group of event types (the last column of the table) and adds that group's own fields on top of the envelope.

Query parameters

Parameter	Type	Required	Description
ticker	string	optional	Up to 10 values, comma-separated; when omitted, the endpoint scans across companies (for example "all CFO departures in the last 90 days"); combine with from / to. The market is carried by the canonical ticker itself, so there is no market parameter. Default Entire market.
event_type	string	optional	stake_change \| share_pledge \| lock_up_expiry; multiple values allowed, comma-separated. Default All.
from	date	optional	Start of the event date (event_date) range, inclusive; for a single day, set from = to.
to	date	optional	End of the event date range, inclusive.
limit	int	optional	Maximum 500. Default 50.
page	int	optional	Starts at 1. Default 1.

Sorted event_date desc, accession_number desc, then row order within one filing. Paged with limit and page (pages start at 1); fewer rows than limit means the last page.

Response fields

Field	Type	Description
event_id	string	Id of a single event; the same value on the typed endpoints and on the timeline
ticker	string	canonical ticker
market	string	Canonical market code
event_class	string	Canonical enum from the table above (9 classes)
event_type	string	Canonical enum from the table above (42 types)
axis	object	Key-value object holding the secondary axis of that type (for example a profit warning, {"direction":"down"}, or a revolving credit facility, {"instrument":"revolver","action":"new"}); for a type with no axis, the value is {}. See OpenAPI for the full set of keys and value domains. Typed endpoints flatten the common axes into top-level fields (instrument / action / subtype…), with the same values as axis; on the timeline, classification detail such as the direction of a profit warning or a trading halt and resumption action is only in this field
source_category	string	The market's native category code, preserved as-is: for US, the 8-K item (8-K:2.03; when several items are triggered, they are joined with commas) or the 13D/G form name (SC 13D / SC 13G)
event_date	date	Event date (signing / resolution / closing); the only date axis in this group
title	string	One-sentence title
stage	string	Lifecycle stage: announced approved amended completed terminated; the multi-stage filings of every market (proposal → shareholder meeting → approval → completion, and so on) all map onto this set
event_group_id	string	The successive filings of the same deal / financing / executive change share one id
is_current	bool	Whether the row is the latest version within the same event_group_id
accession_number	string	Native document number from the official source (US: SEC accession; JP: EDINET docID; CN: cninfo announcement id), or the equivalent filing number
form_type	string	One of the four provenance fields: the source filing type
filing_url	string	One of the four provenance fields: deep link to the official document
filing_date	date	One of the four provenance fields: the filing date
holder_name	string	Shareholder name (as filed)
pct_before	number	Ownership percentage before the change (%)
pct_after	number	Ownership percentage after the change (%)
threshold_pct	number	Statutory threshold that triggers the filing (US 5.0)
shares_after	number	Shares held after the change
shares_changed	number	Shares changed in this event
direction	string	stake_change secondary axis: increase \| decrease
intent	string	stake_change secondary axis: active (13D) \| passive (13G)
action	string	share_pledge secondary axis: pledge / release / supplement / freeze / unfreeze
share_source	string	lock_up_expiry secondary axis: ipo / private_placement / equity_incentive

Request

curl -H "X-API-KEY: $DRILLR_API_KEY" \
  "https://gateway.drillr.ai/api/v2/events-ownership?ticker=PLTR&from=2026-03-01&to=2026-03-31"

Response · 200

{
  "data": [
    {
      "event_id": "105be55eb44776e37c92f3d13eedcd33829833a5",
      "ticker": "PLTR",
      "market": "US",
      "event_class": "ownership",
      "event_type": "stake_change",
      "axis": {
        "intent": "passive"
      },
      "source_category": "SCHEDULE 13G",
      "event_date": "2026-03-31",
      "title": "SCHEDULE 13G: Vanguard Capital Management — 7.28% of Common Stock",
      "stage": "completed",
      "event_group_id": "6e063eeabde9fd324be7",
      "is_current": true,
      "accession_number": "0002100119-26-000893",
      "form_type": "SCHEDULE 13G",
      "filing_url": "https://www.sec.gov/Archives/edgar/data/1321655/000210011926000893/0002100119-26-000893.txt",
      "filing_date": "2026-04-30",
      "holder_name": "Vanguard Capital Management",
      "pct_before": null,
      "pct_after": 7.28,
      "threshold_pct": 5,
      "shares_after": 166908333,
      "shares_changed": null,
      "direction": null,
      "intent": "passive",
      "action": null,
      "share_source": null
    }
  ]
}

No key yet? Create one under API Keys — it is shown once, so store it where your shell can read it. Connecting an agent over MCP instead? That signs in through the browser and needs no key at all.

Authentication, conventions, rate limits and error shapes are the same for every endpoint — they live on REST API.