How to Use a Corporate Events API for Earnings, Dividends, and Conference Calls

Most financial data looks backward. Prices tell you what a security did. Fundamentals tell you what a company reported. Both are essential, and neither tells you what is about to happen.

Corporate events are the other half. An earnings date three weeks out, an ex-dividend date next Tuesday, a conference call with a dial-in at 8:30am: these are the scheduled facts that drive positioning, alerting, and most of what users expect a finance application to know. Getting them by hand means scraping investor relations pages one company at a time, which does not scale and breaks constantly. A corporate events API is how you get that calendar as data.

What Is a Corporate Events API?

A corporate events API returns the schedule of known and announced company events as structured records you can query, filter, and join to the rest of your data.

The distinguishing feature is that it is forward-looking. A fundamentals API answers "what did this company report last quarter." A corporate events API answers "when is this company reporting next, at what time of day, and where is the call." That difference changes what you can build. Alerting, calendars, event-driven screening, and pre-earnings workflows all depend on knowing a date before it arrives.

Intrinio's Corporate Events feed is sourced from Wall Street Horizon and covers more than 6,000 US and global securities, refreshed daily at 8pm EST. It carries upcoming earnings dates, dividend pay dates and ex-dates, dividend amount, currency and frequency, conference call dates and broadcast URLs, corporate action dates, and company reference detail such as website and listing exchange. It is delivered over the API and as CSV.

Tracking Upcoming Earnings Dates Through an API

Earnings dates are the most requested piece of an earnings calendar API, and the most misunderstood.

The record for a security gives you more than a single date. It carries the next earnings date, the fiscal quarter and year that date belongs to, and the time of day the announcement is expected, meaning before the open or after the close. It also carries the dates for each quarter across the year, so you are not limited to the next one. Where a transcript exists, the record points to it with its quarter, year, and URL.

Two access patterns cover almost every use case.

The first is a lookup on a single security. You have a ticker on screen and you want the next date for it. The Latest Earnings Record for Security endpoint returns exactly that.

The second is a sweep. You want every upcoming earnings date across your whole universe so you can build a calendar view or fire alerts. The Latest Earnings Records for All Securities endpoint returns the set in one pass, which you page through and write to your own store.

Two things are worth designing around. Time of day matters more than teams expect: an after-the-close report lands in a different trading session than a before-the-open one, and a calendar that ignores this will mis-sequence everything downstream. And earnings dates move. Companies reschedule, and a date that is confirmed today may be an estimate next week. Refresh on the feed's daily cadence rather than caching a date once and trusting it until it passes.

Using Dividend Pay Dates and Ex-Dividend Dates

A dividend data API is really a date API, because a dividend is defined by four dates that do four different jobs.

The announcement date, sometimes called the declared date, is when the company states its intention to pay. Nothing is owed yet.

The ex-dividend date is the one that determines entitlement. Buy on or after the ex-date and the dividend belongs to the seller, not to you. This is the date that matters for anyone modeling total return or building a dividend capture workflow, and it is the one most often confused with the pay date.

The record date is when the company checks its books to see who holds the shares.

The pay date is when the cash actually arrives, often weeks after the ex-date.

Alongside the dates, the dividend record carries the amount, the currency, the payment frequency, and a status field that tells you where the dividend sits in its lifecycle. Forward-looking metrics including forward dividend rate and forward yield come through the same record, along with the last ex-dividend date and amount for historical reference.

The endpoints follow the same two shapes as earnings. Dividends by Security and Latest Dividend Record for Security serve a single name. Dividends by date for exchange and Latest Dividend Records for All Securities serve a sweep, which is what you want for building a forward dividend calendar.

One design note for anyone covering global securities: the currency field exists because dividends are not all paid in dollars. If you aggregate amounts across a multi-currency portfolio without converting first, your income projection will be wrong in a way that is difficult to spot.

Tracking Conference Calls and Other Company Events

Conference call data is the piece teams usually end up scraping, and it is the piece that benefits most from being handed over as structured data.

The record carries the call date and time, the dial-in phone number, the passcode, and the broadcast URL. That is enough to render a functional "listen to the call" control in an application without a human ever visiting an investor relations page. Where a transcript is available afterward, the record links to it with its quarter and year, which closes the loop from scheduled call to searchable text.

Corporate action dates come through the same feed, as do company reference details such as the company website and the exchange the security trades on. Those reference fields sound minor until you are trying to build a clean event card in a user interface and find yourself missing the one field that makes it look finished.

Corporate Events vs. Corporate Actions: What's the Difference?

These two terms get used interchangeably and they should not be.

A corporate event is something scheduled on a calendar. An earnings announcement, a conference call, an investor day, an annual meeting. The event happens, information is released, and the security itself is unchanged. The data is a date plus some context.

A corporate action is something that changes the security. A stock split changes the share count and the price. A spinoff creates a new instrument. A dividend payment reduces the share price on the ex-date. These require you to adjust historical price series, or every chart and every return calculation you produce will be wrong across the action.

The practical consequence is that the two live in different places and serve different jobs. Corporate events sit in the Corporate Events feed. Price adjustment data sits with stock prices, through the Stock Price Adjustments by Security and Stock Price Adjustments by Exchange endpoints, because its purpose is to correct a price history rather than to populate a calendar.

A dividend is the clearest illustration, because it appears in both roles. As an event, it is a set of forward dates you show a user. As an action, it is an adjustment factor applied to a historical price series. Using the event record to adjust prices, or the adjustment record to build a forward calendar, produces an application that is subtly and persistently wrong. Decide which job you are doing before you decide which endpoint to call.

Access Corporate Events Data With Intrinio

Intrinio's Corporate Events feed brings earnings dates, the full dividend date set, conference call details with broadcast URLs, and corporate action dates into one place, sourced from Wall Street Horizon, refreshed daily at 8pm EST, across more than 6,000 US and global securities. It is available over the API and as CSV.

This feed is part of the Enterprise plan, which is scoped to what you actually need rather than sold as a fixed bundle.

Request Enterprise Access to talk through coverage, delivery, and how the events data fits alongside the pricing and fundamentals feeds you are already using.

‍