New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

getUpcomingEarnings

Returns a list of upcoming earnings dates with filtering capabilities. You can filter by date range, single date, exchange, or ticker symbol. Results are limited to dates from today onwards. Premium only.

SERVERAPI Ninjas SOURCEhttps://mcp.api-ninjas.com/mcp
Low RISK CLASS
Category Read
Parameters 70 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-api-ninjas-mcp/getupcomingearnings.md

What getUpcomingEarnings does on API Ninjas

AI agents call getUpcomingEarnings 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.

ParameterTypeRequiredDescription
date string — Single date in YYYY-MM-DD format. If provided, overrides start_date and end_date to filter by this exact date.
limit integer — Maximum number of results to return. Must be between 1 and 100 (inclusive). Default is 100.
offset integer — Number of results to skip for pagination. Must be a non-negative integer. Use in combination with limit to paginate through results.
ticker string — Ticker symbol to filter by (e.g., AAPL, 0700.HK). Returns only earnings for that specific company.
end_date string — End date in YYYY-MM-DD format. Must be after start_date. Defaults to 10 years from today if not provided.
exchange string — Exchange code to filter by (e.g., NASDAQ, NYSE, HKSE, LSE, TSX). Returns only earnings from companies listed on the specified exchange.
start_date string — Start date in YYYY-MM-DD format. Must be today or later. Defaults to today if not provided.

Parameters from the server's own tool schema.

Why getUpcomingEarnings is rated Low

Even though getUpcomingEarnings 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.

Questions about getUpcomingEarnings

What does the getUpcomingEarnings tool do? +

Returns a list of upcoming earnings dates with filtering capabilities. You can filter by date range, single date, exchange, or ticker symbol. Results are limited to dates from today onwards. Premium only. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.

What parameters does getUpcomingEarnings accept? +

getUpcomingEarnings accepts 7 parameters: date, limit, offset, ticker, end_date, exchange, start_date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getUpcomingEarnings? +

Register the API Ninjas MCP server in PolicyLayer and add a rule for getUpcomingEarnings: 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.

What risk level is getUpcomingEarnings? +

getUpcomingEarnings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getUpcomingEarnings? +

Yes. Add a rate_limit block to the getUpcomingEarnings 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.

How do I block getUpcomingEarnings completely? +

Set action: deny in the PolicyLayer policy for getUpcomingEarnings. 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.

What MCP server provides getUpcomingEarnings? +

getUpcomingEarnings 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of API Ninjas's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.