Investing.com earnings calendar
Company earnings releases for a date range: date, timing (before the open, after the close), release time once reported, the company (id, symbol, name, exchange, country, currency, sector id, links), fiscal year and quarter, period end, EPS and revenue forecasts, actuals and surprise percentages, and the share price before and after the release. Filter by country, importance and sector. Up to 92 days per call. Pass next_cursor back as cursor; null on the last page.
Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
from | string | First date, YYYY-MM-DD (default today). Example: 2026-10-26 |
to | string | Last date, YYYY-MM-DD (default from). Example: 2026-10-30 |
countries | string | Comma-separated countries: US, GB, EZ (euro zone), DE, FR, IT, ES, JP, CN, AU, CA, NZ, CH, IN, BR, HK, KR, MX, or Investing.com numeric country ids. Default: all. Example: US |
importance | string | Comma-separated company importance levels: low, medium, high. Default: all. Example: high |
sectors | string | Comma-separated Investing.com sector ids (as in instrument.sector_id). Default: all. |
limit | integer | Releases per page (1-200, default 100). |
cursor | string | next_cursor from the previous page. |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/investing/v1/earnings-calendar?from=2026-10-26" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/investing/v1/earnings-calendar",
params={"from": "2026-10-26"},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/investing/v1/earnings-calendar");
url.searchParams.set("from", "2026-10-26");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); Response
A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).