Earnings
Earnings call summary
- 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/periodfollow 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 | string | required | Fiscal 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. |
| 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 | string | 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 |
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.