Get Earnings Calendar
Fetch upcoming and scheduled company earnings from Finnhub within a date range (default: next 30 days). Returns report date, time (bmo/amc), EPS and revenue estimates, and actuals once reported, soonest first. Note: the free Finnhub plan primarily surfaces upcoming earnings — historical actuals (past EPS beats/misses) may be unavailable. Ideal for: earnings-date alerts, pre-earnings workflows, scheduling trades around reporting dates.
Catalog action Blockchain Data
Fetch upcoming and scheduled company earnings from Finnhub within a date range (default: next 30 days). Returns report date, time (bmo/amc), EPS and revenue estimates, and actuals once reported, soonest first. Note: the free Finnhub plan primarily surfaces upcoming earnings — historical actuals (past EPS beats/misses) may be unavailable. Ideal for: earnings-date alerts, pre-earnings workflows, scheduling trades around reporting dates.
At a Glance
| Field | Value |
|---|---|
| Action ID | finnhub-get-earnings-calendar |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | finnhub, stock, research, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
symbol | string | No | Optional stock symbol to filter by, e.g. 'AAPL'. Omit to query the whole calendar. |
from | string | No | Start date in YYYY-MM-DD format. Default: today (or 30 days before 'to' when only 'to' is given). |
to | string | No | End date in YYYY-MM-DD format. Default: 30 days after 'from' (or 30 days from today). |
limit | number | No | Maximum number of events to return. Range: 1-250. Default: 100. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
from | string | Yes | Start date of the queried range (YYYY-MM-DD) |
to | string | Yes | End date of the queried range (YYYY-MM-DD) |
symbol | string | null | Yes | Symbol filter applied, or null when the whole calendar was queried |
earnings | array | Yes | Earnings events, soonest first |
count | number | Yes | Number of events returned |
Examples
json{ "type": "finnhub-get-earnings-calendar", "payload": { "symbol": "ETH", "from": "example-from", "to": "example-to", "limit": 100 }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/finnhub-get-earnings-calendar/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "symbol": "ETH", "from": "example-from", "to": "example-to", "limit": 100 }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.