FMP Earnings Calendar API
Python Example & WorkflowFMP 财报日历 API
Python 示例与生产工作流

TL;DR

Prerequisites and architecture boundary准备工作与架构边界

This implementation is for research dashboards, portfolio calendars, earnings-monitoring agents, and pre/post-event workflows. You need an FMP API key, an allowed plan, a date-window policy, secure secret storage, and a destination such as a database or queue.

本实施方案适用于研究看板、投资组合日历、财报监控 Agent，以及财报前后工作流。需要准备 FMP API Key、允许访问该接口的套餐、日期窗口策略、安全密钥存储，以及数据库或队列等输出位置。

FMP Earnings Calendar API Python exampleFMP 财报日历 API Python 示例

The official stable endpoint is https://financialmodelingprep.com/stable/earnings-calendar. The example below supplies an API key and explicit date window, raises on HTTP errors, validates the JSON shape, and never logs the credential.

官方 Stable API 路径是 https://financialmodelingprep.com/stable/earnings-calendar。下面的示例携带 API Key 和明确日期窗口，对 HTTP 错误直接失败，验证 JSON 结构，并且不记录密钥。

import os
from datetime import date, timedelta

import requests

API_URL = "https://financialmodelingprep.com/stable/earnings-calendar"
API_KEY = os.environ["FMP_API_KEY"]

start = date.today()
end = start + timedelta(days=7)

response = requests.get(
    API_URL,
    params={
        "from": start.isoformat(),
        "to": end.isoformat(),
        "apikey": API_KEY,
    },
    timeout=(3.05, 20),
)
response.raise_for_status()

events = response.json()
if not isinstance(events, list):
    raise ValueError("Expected the FMP earnings calendar to return a list")

print(f"received {len(events)} earnings events")

Understand the response before writing business logic编写业务逻辑前先理解返回字段

FMP documents announcement date, estimated EPS, and actual EPS as core earnings-calendar data. Its related earnings documentation also describes release-session labels such as before market open (BMO) and after market close (AMC), while the changelog records fields including fiscalDateEnding and updatedFromDate. Inspect the live payload available to your plan before relying on any field.

FMP 官方文档把公告日期、预估 EPS 和实际 EPS 作为财报日历核心数据；相关财报文档还说明了盘前（BMO）和盘后（AMC）等发布时段，Changelog 则记录了 fiscalDateEnding 与 updatedFromDate 等字段。依赖任何字段前，都要检查当前套餐实际返回的数据。

Normalize event date, fiscal period, session, and estimates统一事件日期、财务期间、发布时段与预估值

Keep the raw FMP record unchanged, then create a separate canonical event. A normalized record should make uncertainty visible instead of turning a date or BMO/AMC label into a false exact timestamp.

原始 FMP 记录应保持不变，再单独生成统一事件。标准化记录应该显式表达不确定性，而不是把日期或 BMO/AMC 标签伪装成精确时间戳。

{
  "event_id": "earnings:security-123:2026-08-06",
  "issuer_id": "issuer-123",
  "security_id": "security-123",
  "symbol_as_reported": "EXAMPLE",
  "event_date": "2026-08-06",
  "release_session": "after_market_close",
  "release_time_precision": "session_only",
  "exchange_timezone": "America/New_York",
  "fiscal_period_end": "2026-06-30",
  "eps_estimate": 1.23,
  "eps_actual": null,
  "revenue_estimate": null,
  "revenue_actual": null,
  "provider": "financial_modeling_prep",
  "retrieved_at": "2026-08-03T08:00:00Z",
  "validation_status": "accepted_with_unknowns",
  "raw_record_hash": "sha256:..."
}

Step-by-step earnings monitoring implementation分步构建财报监控工作流

Validate each event before it reaches an alert or agent事件进入提醒或 Agent 前必须逐项验证

Control API keys, rate limits, caching, and alert load控制 API Key、限流、缓存与提醒负载

Do not hardcode plan quotas in application logic or this guide. Verify current endpoint access, call limits, commercial rights, and pricing in FMP's official plan documentation before deployment.

不要在应用逻辑或本指南中写死套餐配额。部署前应在 FMP 官方套餐文档中核对当前接口访问权、调用限制、商业使用权和价格。

Common FMP earnings calendar failure modesFMP 财报日历常见失败模式

Where QVeris fits in an earnings workflowQVeris 在财报工作流中的位置

FMP Earnings Calendar API FAQFMP 财报日历 API 常见问题

Verify the endpoint, changes, timing, and access核对接口、变更、更新时间与访问权限

FMP documentation is the source of truth for current parameters, fields, cycle times, access tiers, and commercial terms. Re-run contract tests when FMP changes the stable endpoint or response schema.

当前参数、字段、更新周期、访问套餐与商业条款应以 FMP 官方文档为准。Stable API 或返回 Schema 发生变化时，应重新运行契约测试。