Earnings

Earnings calendar

GET/api/v2/earnings-calendar

Coverage: US / CN / JP
Billing: 20 cr / thousand calls

One row per company per earnings announcement, covering the three markets US / CN / JP, queried by announcement date date. The endpoint does not filter by ticker; filter the returned rows when querying a single company.

from / to are required and inclusive on both ends, and the window spans at most 90 days; a window longer than 90 days, or a to earlier than from, returns 400; a window with no records returns an empty array.

For announcements not yet disclosed or not yet ingested, eps_actual / revenue_actual are null, and the estimates may be null as well; actuals are filled in after disclosure. last_updated is the update date of the calendar source record and has no fixed ordering relative to the announcement date.
Amounts are denominated in the trading currency of the listing venue; the row carries no currency field, and cross-market comparison requires client-side conversion.
eps_actual follows the normalized basis of the calendar source and may disagree with eps_basic in /income-statements.

Query parameters

Parameter	Type	Required	Description
from	date	required	Start date, inclusive.
to	date	required	End date, inclusive; at most 90 days from from.
limit	int	optional	Maximum 500. Default 50.
page	int	optional	Starts at 1. Default 1.

Sorted date asc, ticker asc. Paged with limit and page (pages start at 1); fewer rows than limit means the last page.

Response fields

Field	Type	Description
ticker	string	The company's canonical ticker
date	date	Earnings announcement date (the field filtered by from / to)
eps_actual	number	Actual EPS; null when not yet disclosed or not yet ingested
eps_estimated	number	Analyst consensus EPS
revenue_actual	number	Actual revenue, in the trading currency of the listing venue; null when not yet disclosed or not yet ingested
revenue_estimated	number	Analyst consensus revenue, in the same currency as revenue_actual
last_updated	date	Most recent update date of the calendar source record

Request

curl -H "X-API-KEY: $DRILLR_API_KEY" \
  "https://gateway.drillr.ai/api/v2/earnings-calendar?from=2026-03-06&to=2026-06-03&limit=50&page=1"

Response · 200

{
  "data": [
    {
      "ticker": "NVDA",
      "date": "2026-05-28",
      "eps_actual": 1.05,
      "eps_estimated": 1.01,
      "revenue_actual": 46743000000,
      "revenue_estimated": 46047000000,
      "last_updated": "2026-05-29"
    }
  ]
}

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.