ForexFactory Economic Calendar Scraper

For forex/futures traders, quant research pipelines, and AI trading agents that need structured economic-release data — no API key, no login, no headless browser.

No API key required. No ForexFactory account. Pay Per Event — you're charged one event_row per calendar event returned. Every record includes parseConfidence (0.0–1.0) and warnings.

Scrape ForexFactory's public economic calendar (forexfactory.com/calendar) — one of the most widely used free forex-trader calendars on the web. Date/time (UTC), currency, impact level, actual/forecast/previous/revised values with parsed numeric variants, and — with detail mode switched on — the data source, release frequency, and a plain-English description of what each indicator measures.

---

Why this actor over the alternatives

Most ForexFactory scrapers on the Store only read the base calendar page. That page genuinely does not carry a data source, release frequency, or indicator description — those live on a separate per-indicator detail page. The common result: source / frequency / description fields declared in the output schema but sitting at 0% fill-rate forever, on every rival that only reads the base page.

This actor closes that gap. With includeDetail: true, it fetches each distinct indicator's ForexFactory detail page once per run (deduped by indicator — one extra request per unique indicator in your result set, not per event row) and folds source, sourceUrl, frequency, eventDescription, usualEffect, alsoCalled, and eventType into every matching event.

Field	Base calendar page	This actor (includeDetail: true)
date / time / currency / impact	✅	✅
actual / forecast / previous / revised (+ numeric)	✅	✅
source, sourceUrl	❌ not on this page	✅
frequency	❌ not on this page	✅
eventDescription (what the indicator measures)	❌ not on this page	✅
usualEffect, alsoCalled, eventType	❌ not on this page	✅ (bonus — not on the base page at all)

---

What data you get

One record per calendar event:

• eventId — stable composite key, <date>-<currency>-<slug(eventTitle)> (e.g. 2026-07-21-GBP-claimant-count-change)
• url, soloUrl — deep link into the calendar and the indicator's own detail page
• date, time, timestamp — UTC (derived from ForexFactory's own event epoch, not a display-timezone guess), displayTimezone
• country, currency, impact (low/medium/high/holiday), eventTitle, isAllDay, leaked
• actual, actualNumeric, forecast, forecastNumeric, previous, previousNumeric, revised, revisedNumeric, unit
• Detail mode only: source, sourceUrl, frequency, eventDescription, usualEffect, alsoCalled, eventType, detailFetched
• scrapedAt, parseConfidence, warnings

actual/revised are legitimately empty for events that haven't happened yet (a forward-looking this_week / next_week window) — that's the real state of the data, not a parser gap.

---

How to use

This week's high/medium impact USD/EUR/GBP/JPY events

{
  "range": "this_week",
  "currencies": ["USD", "EUR", "GBP", "JPY"],
  "impactLevels": ["high", "medium"],
  "includeDetail": false,
  "maxEvents": 50
}

Today's events with full indicator detail (source/frequency/description)

{
  "range": "today",
  "includeDetail": true,
  "maxEvents": 30
}

All currencies, next month, high impact only

{
  "range": "next_month",
  "impactLevels": ["high"],
  "maxEvents": 300
}

---

Input parameters

Field	Type	Default	Description
range	enum	this_week	today / tomorrow / yesterday / this_week / next_week / last_week / this_month / next_month / last_month
currencies	array of string	[] (all)	Currency codes to keep, e.g. USD, EUR, GBP, JPY
impactLevels	array of string	[] (all)	Subset of low / medium / high / holiday
includeDetail	boolean	false	Fetch each distinct indicator's detail page once to fill source/frequency/description
maxEvents	integer	200	Cap on rows returned (after filtering), hard max 1000
proxyConfiguration	object	RESIDENTIAL	Apify Proxy settings — works out of the box, no proxy key needed from you

---

Pricing

Pay Per Event: event_row — one charge per calendar-event record returned. includeDetail: true adds no extra per-row charge; the indicator detail fetch is internal COGS, deduped by indicator across your whole run.

---

Legal

ForexFactory's /calendar is a public, unauthenticated page — no login wall, no paywall. This actor reads only that publicly available economic-release schedule; it does not access any account-gated ForexFactory content (forums, trade-journal, member tools). Data is provided for informational purposes; it is not investment advice.

---

MCP / AI agent integration

This actor works as an Apify MCP tool — call it from Claude, GPT, or any MCP-compatible agent to pull a structured economic calendar into a trading research pipeline without scraping code of your own.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.