Financial data is informational and may be inaccurate. See Disclaimer.

drillr.ai
API keys →

Earnings

Earnings call summary

GET/api/v2/earnings-call-summaryUS only
Coverage
US
Billing
20 cr / thousand calls

One row per earnings call: a structured summary across five dimensions — management highlights, guidance, risks, segment performance and Q&A topics — plus the title and the date; the raw transcript is not provided. Use ticker + fiscal_year + period to locate a single call; 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

ParameterTypeRequiredDescription
tickerstringrequiredA single ticker.
fiscal_yearintrequiredFour-digit fiscal year, e.g. 2026.
periodstringrequiredFiscal quarter Q1–Q4; only these four values are accepted. FY / H1, which are used by the financial-statement endpoints, are not accepted. A fourth-quarter call uses Q4 and is unaffected by the rule that US financial statements have no standalone Q4 period.
limitintoptionalMaximum 20. Default 1.

Response fields

FieldTypeDescription
tickerstringThe company's canonical ticker
fiscal_yearintFiscal year
periodstringFiscal quarter Q1–Q4
datedateEarnings call date
titlestringSummary title
management_highlightsstringSummary of management statements and operating highlights
guidancestringSummary of forward-looking guidance
risksstringSummary of risks and operating challenges
segment_performancestringSummary of product, business line or regional performance
qa_topicsstringSummary of key analyst Q&A topics

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.