Historical and upcoming
earnings calendar API
Backfill historical earnings dates, sync upcoming reports, and layer in post-earnings market reactions when needed. Structured JSON for alerts, dashboards, trading tools, newsletters, and research workflows.
/v1/calendar/earnings?date=todayQuery historical and upcoming earnings events by date for imports, daily refreshes, and product scheduling.
/v1/earnings-reactions?symbol=AAPLLayer in post-earnings price and volume moves alongside beat/miss data when your workflow needs it.
Why teams choose Earnings API
Historical + upcoming calendar
Start with date-based earnings events, from backfills to upcoming report monitoring.
Structured for automation
Predictable JSON fields make it straightforward to trigger jobs, populate UIs, cache responses, and reconcile daily syncs.
Layer in reaction data
Add post-earnings price and volume moves for the symbols that need deeper event analysis.
Built for backfills and sync jobs
Query date-based earnings calendars for historical imports, daily refreshes, and scheduled product workflows.
How it works
Get the earnings calendar
Fetch earnings events with date=today, yesterday, tomorrow, or YYYY-MM-DD for historical backfills and upcoming report syncs.
Backfill or sync by date
Import historical calendars, refresh upcoming dates daily, or run scheduled workflows against date-based event data.
GET /v1/calendar/earnings?date=today&apikey=YOUR_API_KEYLayer in market reactions
When you need post-event context, pull /v1/earnings-reactions for selected symbols to compare beat or miss data with price and volume moves.
Build your product
Power alerts, dashboards, newsletters, trading tools, or internal research workflows.
Sample Calendar Response
JSON{
"date": "2025-07-02",
"pre": [
{
"symbol": "JPM",
"name": "J P Morgan Chase & Co",
"epsEstimate": 5.01,
"eps": 4.81,
"revenue": 45798000000,
"revenueEstimate": 46166454906
}
],
"after": [
{
"symbol": "DAL",
"name": "Delta Air Lines, Inc.",
"epsEstimate": 1.53,
"eps": 1.85,
"revenue": 16003000000,
"revenueEstimate": 14682059858
}
],
"notSupplied": [
{
"symbol": "BK",
"name": "The Bank Of New York Mellon Corporation ",
"epsEstimate": 1.97,
"eps": 1.72,
"revenue": 8869000000,
"revenueEstimate": 5141942072
}
]
}Ideal for
Earnings Alert Tools
Sync upcoming report dates, trigger notifications, and monitor selected post-event market reactions.
Quant Dashboards
Backfill calendars, refresh upcoming events, and add surprise or reaction data inside trading dashboards.
Financial Newsletters
Build earnings previews from upcoming calendars and historical context from date-based imports.
Research & Analytics Platforms
Power internal research tools, earnings-focused data products, and scheduled sync pipelines.
Start with the calendar. Layer in reaction data.
Most integrations begin with /calendar/earnings. High-value workflows add /earnings-reactions for post-event analysis, then use profile and earnings as supporting data.
FAQ
Do I need to create an API key manually?
No. When you sign up, your API key is generated automatically and available in your dashboard.
What should I integrate first?
Start with /v1/calendar/earnings. It is the entry point for most products and the easiest way to backfill historical dates or sync upcoming events.
Can I backfill historical earnings dates?
Yes. Paid access is designed for products that need historical imports, upcoming earnings syncs, and automated date-based workflows.
What should I call after calendar?
Most teams fetch /v1/earnings-reactions for symbols that matter, then join in /v1/profile/{symbol} or /v1/earnings as needed.
Is this white-label?
The API is built for integration into your product UI, automation layer, or internal data pipeline.