Earnings

Earnings call summary

GET/api/v2/earnings-call-summaryUS only

Coverage: US
Billing: 20 cr / thousand calls

Returns a structured summary of an earnings call across five dimensions: management highlights, guidance, risks, segment performance and Q&A topics, plus the title and date, one row per call; the transcript itself is not provided. Locate a call with ticker + fiscal_year + period; a fiscal quarter usually has only one call, so the default limit=1 is enough.

fiscal_year / period follow the company's own fiscal calendar (AAPL's FY2020 Q3 spans calendar months 4–6 of 2020, for example), not the calendar quarter.
Summaries are model-generated from the earnings call transcript; all five dimensions are free text and are null when empty.
Covers US-listed companies; a non-US ticker returns 404.

Query parameters

Parameter	Type	Required	Description
ticker	string	required	A single ticker.
fiscal_year	int	required	Four-digit fiscal year, e.g. `2026`.
period	stringenum	required	Fiscal quarter: `Q1` / `Q2` / `Q3` / `Q4`; `FY` is not accepted.
limit	int	optional	Maximum 20. Default: 1.

Response fields

Field	Type	Description
ticker	string	The company's canonical ticker
fiscal_year	int	Fiscal year
period	stringenum	Fiscal quarter `Q1`–`Q4`
date	date	Earnings call date
title	string	Summary title
management_highlights	string	Summary of management statements and operating highlights
guidance	string	Summary of forward-looking guidance
risks	string	Summary of risks and operating challenges
segment_performance	string	Summary of product, business line or regional performance
qa_topics	string	Summary of key analyst Q&A topics

Request

curl -H "X-API-KEY: $DRILLR_API_KEY" \
  "https://gateway.drillr.ai/api/v2/earnings-call-summary?ticker=AAPL&fiscal_year=2020&period=Q3"

Response · 200

{
  "data": [
    {
      "ticker": "AAPL",
      "fiscal_year": 2020,
      "period": "Q3",
      "date": "2020-07-30",
      "title": "Apple FY2020 Q3 earnings call summary",
      "management_highlights": "Services and wearables reached record revenue…",
      "guidance": "Management did not provide formal quarterly guidance…",
      "risks": "COVID-19 continued to create uncertainty…",
      "segment_performance": "iPhone revenue increased while Mac and iPad accelerated…",
      "qa_topics": "Analysts focused on product demand, margins and capital returns…"
    }
  ]
}

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.