Events · US only

Event timeline

GET/api/v2/eventsUS only

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

One row = the common envelope of one event, covering all 9 event_class values, with no type-specific fields. Use it to answer "what has happened recently at this company / across the entire market"; for type-specific fields, go to the typed endpoint that matches the event_class, fetch the row with the same ticker plus from = to = event_date, then align on event_id (the same value on both sides; the typed endpoints do not accept an event_id parameter).

The guidance and legal_regulatory classes appear only on this timeline; classification detail such as the direction of a profit warning or a trading halt and resumption action is in axis.
event_group_id= returns every filing and every version of the same real-world event, and is the only way to see rows with is_current = false.
The rows of this endpoint are also the shape of the webhook company event payload.

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	Canonical enum from (42 types); 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.
event_class	string	optional	All 9 classes of ; multiple values allowed, comma-separated; a class that has no data yet returns an empty array, not a 400. Default All.
event_group_id	string	optional	Returns every filing of the same real-world event: each lifecycle stage plus the companion events split onto their own rows (for example an acquisition and its accompanying financing); when this parameter is passed, all versions in the group are returned instead of only the latest version.
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

Request

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

Response · 200

{
  "data": [
    {
      "event_id": "2ab01e9be7acdb60d1fa9fdb1a50d66099f571c6",
      "ticker": "BA",
      "market": "US",
      "event_class": "capital",
      "event_type": "debt_issuance",
      "axis": {
        "action": "amend"
      },
      "source_category": "8-K:1.01",
      "event_date": "2026-08-24",
      "title": "Debt Issuance: 2023 Five-Year Credit Agreement",
      "stage": "amended",
      "event_group_id": "17f96e213777c218efe4",
      "is_current": true,
      "accession_number": "0001628280-26-059427",
      "form_type": "8-K",
      "filing_url": "https://www.sec.gov/Archives/edgar/data/12927/000162828026059427/0001628280-26-059427.txt",
      "filing_date": "2026-08-28"
    }
  ]
}

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.