getEarningsCalendar
Returns earnings reports for one company (ticker), one calendar date (date), or a date range (date_start/date_end). At least one of these is required, and date cannot be combined with a range. Covers 50,000+ tickers on US and international exchanges with history back to 2000. Results are sorted b...
This record as markdown: /tools/com-api-ninjas-mcp/getearningscalendar.md
What getEarningsCalendar does on API Ninjas
AI agents call getEarningsCalendar to retrieve information from API Ninjas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | Single report date in YYYY-MM-DD format (e.g. 2026-07-30). Returns every company reporting on that date. Cannot be combined with date_start or date_end. |
offset | integer | — | Number of results to skip, for pagination. Each request returns up to 50 results, so use offset=50, 100, ... to page. |
ticker | string | — | Company ticker symbol (e.g. MSFT, 7203.T). Returns that company's earnings reports, newest first. |
date_end | string | — | End of a report-date range (YYYY-MM-DD, inclusive). Must be on or after date_start. If date_start is omitted, the range starts 7 days before date_end. |
date_start | string | — | Start of a report-date range (YYYY-MM-DD, inclusive). If date_end is omitted, the range ends 7 days after date_start. |
show_upcoming | boolean | — | Include scheduled future reports (dates after today). Without it only past and same-day reports are returned. Premium only: free-tier requests that pass this pa |
Parameters from the server's own tool schema.
Why getEarningsCalendar is rated Low
Even though getEarningsCalendar only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs getEarningsCalendar safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getEarningsCalendar, this is the rule to start with:
getEarningsCalendar is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API Ninjas, apply this rule, and every getEarningsCalendar call is checked against it from then on.
Questions about getEarningsCalendar
Returns earnings reports for one company (ticker), one calendar date (date), or a date range (date_start/date_end). At least one of these is required, and date cannot be combined with a range. Covers 50,000+ tickers on US and international exchanges with history back to 2000. Results are sorted by date (newest first) and returned 50 per request; use offset to page. Past reports only by default; set show_upcoming=true (premium) to include scheduled future reports. EPS and revenue are in the company's reporting currency. actual_eps/estimated_eps are on the adjusted (non-GAAP) basis analysts use; actual_eps_gaap is GAAP diluted EPS from the SEC 10-Q/10-K (US SEC filers). For upcoming dates filtered by exchange use /upcomingearnings. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getEarningsCalendar accepts 6 parameters: date, offset, ticker, date_end, date_start, show_upcoming. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getEarningsCalendar: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches API Ninjas. Nothing to install.
getEarningsCalendar is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getEarningsCalendar rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for getEarningsCalendar. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
getEarningsCalendar is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue