Economic calendar data for trading tools
Bring upcoming economic releases, central bank decisions and source context into your bots, dashboards and market briefings.
Choose a plan, create and confirm your account, complete payment, then generate your key. Creating an account does not charge you.
curl --fail-with-body \
"https://www.financecalendar.com/wp-json/fc/v1/calendar?country=US,GB&impact=high&limit=5" \
-H "X-API-Key: $FC_API_KEY"FC_API_KEY privately on your machine or server.Add calendar context to your workflow
Use the API from software that supports authenticated HTTPS requests. Start with the recorded schedules and check the coverage of the events you need.
Release watchlists
Collect upcoming announcements by country, series or importance. Show the recorded release time and flag dates that remain estimated or unknown.
Alerts and news windows
Give your own tool the scheduled events it needs for alerts or a news-risk filter. Keep source timing and stale-data states visible when deciding how to use a record.
Dashboards and briefings
Combine release schedules with your own analysis, or add exchange closures to a market briefing. A shared server cache can serve the same view to multiple visitors.
Run a calendar watchlist
Choose Python or Node.js. Both examples request a seven-day, high-impact calendar, keep the complete event records and use a private 15-minute cache. They fetch data and print a watchlist; they do not place trades.
Clone the public examples once, then open their folder:
git clone https://github.com/awarenessdays/financecalendar-api.git
cd financecalendar-api/integrations/examples/trading-toolsSet FC_API_KEY in your private environment before running an example. The setup guide includes terminal instructions. Keep keys out of browser JavaScript, URLs and source control.
Python
Fetch a recorded calendar for a research script, scheduled report or custom trading-tool backend.
python3 python/calendar_watchlist.pyRequires Python 3.10 or newer and uses the standard library. See the setup guide for configuration options.
JavaScript with Node.js
Load the same calendar from a Node process. Keep your key in that process when adding a browser dashboard.
node node/calendar-watchlist.mjsRequires Node.js 20 or newer and uses built-in APIs. See the setup guide for configuration options.
The examples preserve source staleness fields, stop on authentication or access errors and honour Retry-After when rate-limited. A failed refresh stops the command without printing a watchlist. Read the setup guide before scheduling repeated runs.
Connect with your own paid API key
Build is the starting point for an ongoing automation or app. Compare the current plans against how often your software fetches data and any other integrations on the same account.
Plan for your refresh schedule. One continuously used 15-minute cache has up to 96 refresh opportunities a day, about 2,880 in 30 days before pagination and other account activity.
Starter is suited to occasional use and has a monthly allowance. Check the current daily and monthly limits before scheduling a tool.
- Choose a paid plan. The signup link selects Build. Review its price and billing period before continuing.
- Create and confirm your account. Follow the email confirmation steps, or sign in if you are already registered.
- Complete payment, then create a key. Finish secure checkout in your account. Once paid access is confirmed, choose “Create API key” and keep the full key when it is shown.
- Run your example. Add the key to your private environment or terminal settings, fetch a calendar and inspect the results. Read the API key setup guide.
Before you connect a tool
What if my existing integration keeps receiving an error?
HTTP 401 means the key is missing or invalid. Check your configured key and send it in the X-API-Key header. HTTP 402 means account activation or payment is required; HTTP 403 can indicate an access or verification problem. Stop repeated requests while fixing the account or configuration. For HTTP 429, wait for the response’s Retry-After period and check your shared account allowance. Open the key setup guide.
How should I handle unknown times and missing values?
Preserve null values and inspect status, time_precision, recorded time windows and data_stale. An unknown release time is not midnight, and a missing actual is not zero. Your local cache timestamp does not establish when a publisher last verified a record. Check the measured coverage and source status.
Is this a live trading signal or a complete backtesting database?
The API supplies recorded schedules and available observations. Coverage varies by source and series; some dates are estimated and some figures remain missing. It is not a promise of instantaneous release delivery, trading performance or a complete point-in-time first-print archive. Inspect the data you need before choosing a workflow.
Can I use the calendar in a commercial tool?
Commercial use is welcome with visible Finance Calendar attribution and the applicable publisher credits and reuse terms. Retain event and observation source notices when passing records into another system. Your subscription does not grant additional rights to third-party material. Read the API service terms.
Give your tool a recorded calendar to work with
Start with a paid API key, run an example and check the source context of the events your workflow needs.