Economic Calendar API — ForexFactory Calendar as Clean JSON (FOMC, CPI, NFP)

Economic Calendar Pro is an economic calendar API that turns the free ForexFactory calendar feed into clean, normalized JSON you can pipe into trading bots, dashboards, n8n/Make automations, or cron jobs. It covers every scheduled macro release — FOMC statements, CPI, Non-Farm Payrolls (NFP), rate decisions, PMI, GDP and more — for USD, EUR, GBP, JPY, CAD, AUD, NZD, CHF, CNY and other major currencies.

⚠️ Unofficial. This Actor is not affiliated with, endorsed by, or sponsored by ForexFactory or Fair Economy, Inc. It consumes their publicly available calendar feed.

What it does

• Fetches the ForexFactory economic calendar for this week, next week, and/or last week.
• Normalizes every event: stable event_id, ISO 8601 UTC timestamps, consistent field names.
• Filters by currency (USD, EUR, …), impact (High / Medium / Low / Holiday), and event-name keyword (CPI, FOMC, Non-Farm…).
• Change detection: run it on a schedule with changesOnly: true and get only new events or events whose forecast/previous/actual/time changed — perfect for alerts.
• Webhook delivery: optionally POSTs changed events to your endpoint as JSON.

Output schema

Each dataset row:

Field	Type	Description
source	string	Always forexfactory
event_id	string	Stable 16-char hash of title + currency + scheduled time
title	string	Event name, e.g. CPI m/m, Non-Farm Employment Change, FOMC Statement
country / currency	string	Currency code the event affects, e.g. USD
date_utc	string	Scheduled time as ISO 8601 UTC, e.g. 2026-07-22T12:30:00Z
impact	string	High, Medium, Low, or Holiday
forecast	string	Consensus forecast, e.g. 2.1% (may be empty)
previous	string	Previous reading (may be empty)
actual	string	Released value (the free feed does not publish it; kept for schema stability)
url	string	Deep link to the ForexFactory calendar day page
week	string	Which fetch window the event came from: this / next / last

In changes-only mode rows additionally carry:

Field	Type	Description
change_type	string	new or updated
changed_fields	array	Which watched fields changed, e.g. ["forecast"]
old_<field>	string	Previous value for each changed field

Input examples

Default (empty input {}): this week + next week, all currencies, all impacts.

High-impact USD events only:

{
  "currencies": ["USD"],
  "impacts": ["High"]
}

CPI releases across all majors, next week included:

{
  "weeks": ["this", "next"],
  "keyword": "CPI"
}

Scheduled change alerts with webhook (run hourly):

{
  "currencies": ["USD", "EUR"],
  "impacts": ["High"],
  "changesOnly": true,
  "webhookUrl": "https://hooks.example.com/econ-calendar"
}

Use cases

• n8n / Make.com pipelines — trigger workflows when a high-impact event is added or a forecast is revised; the webhook payload plugs straight into an HTTP trigger node.
• Trading bots — pause strategies around FOMC/NFP windows using date_utc (already UTC, no timezone math).
• Cron + API — schedule the Actor on Apify and read the dataset via the Apify API as your own forexfactory calendar API endpoint (JSON/CSV/Excel export built in).
• Dashboards & research — join event_id across runs to track forecast revisions over time.

Change detection details

The Actor keeps a snapshot of every event (keyed by event_id) in the named key-value store economic-calendar-state. On each run it diffs the fresh calendar against the snapshot. With changesOnly: true, only new/updated events are pushed to the dataset; with the default false, the full filtered calendar is pushed and the snapshot is still updated, so you can warm up the state before enabling alerts.

Pricing

Pay-per-event: you are charged a small fee per calendar row delivered (event-fetched) and per change alert (change-alert) — no subscriptions, no minimums. Exact prices are shown on the Actor's Apify Store page.

FAQ

Is this a free economic calendar API? The data source is the free public ForexFactory feed; running the Actor is billed per event delivered (see Pricing).

What timezone are the dates in? Everything is normalized to UTC ISO 8601 (...Z). The upstream feed publishes US/Eastern offsets; conversion is handled for you.

Does it include actual/released values? The free JSON feed only carries forecast and previous. The actual field is present in the schema but empty; time/forecast/previous revisions are still detected.

Why is next week's calendar sometimes empty? The upstream CDN occasionally hasn't published the nextweek file yet (HTTP 404). The Actor logs a warning and continues with the available weeks.

How often should I schedule it? Hourly is plenty for forecast-revision alerts; every 5–15 minutes if you want to catch late schedule changes before big releases.

Is event_id stable? Yes — it is a hash of title + currency + the feed's scheduled time, so it is identical across runs until the event itself is rescheduled (which is then reported as a change).