CalendarExport - expert for MetaTrader 5

MetaTrader 5 ships a complete economic calendar, and MQL5 can read it through CalendarValueHistory(). Nothing outside the terminal can. The Python MetaTrader5 package exposes prices, symbols, orders, positions and history — but no calendar function at all.

So a research script, a dashboard, a bot or a spreadsheet has no way to ask the terminal when the next high-impact release lands. This Expert Advisor is that missing bridge: attach it to any chart and it periodically writes the calendar to a CSV file in MQL5\Files, where anything outside the terminal can read it.

It is strictly read-only. It never opens, closes or modifies a position.

Five details that matter

• UTF-8 output. Event names are localised by the terminal, so on a non-English MT5 they contain accented or non-Latin characters. Written in the local codepage they become bytes that are not valid UTF-8, and most consumers either throw or silently mangle the name.
• Sorted by time. The calendar is queried once per currency, so the natural output is grouped by currency and jumps back and forth in time. This one is chronological.
• Written in a single call. The file is built in memory and written at once. A reader that opens it mid-write would otherwise see a truncated list and have no way of knowing.
• HTML entities decoded. The terminal stores event names escaped: CFTC S&P 500 ... comes back as S&P. Written through unchanged it reaches every consumer wrong.
• A freshness header. The first line carries the update time, the event count and the server's UTC offset, so a consumer can tell a stale file from a current one — and notice that the EA was detached, instead of showing an old calendar as if it were live.

The update time is read from the trade server clock and not from the last tick. With the market closed the last tick stands still, so a file dated that way would look stale while being rewritten every few minutes, and the event window would slide backwards over the weekend.

Inputs

A note on language. Event names are returned in the terminal's language and MQL5 offers no way to request another. If you need a key that is stable across languages and installations, use the event_id column — that is exactly why it is there.

If the file comes out empty: MT5 only populates the calendar when the terminal is connected, and some brokers restrict it. Check Tools → Options → Server that the calendar is enabled.