Find FOMC meeting dates and minutes

The next FOMC rate decision is Wednesday, 28 October 2026 at 18:00 UTC, with the minutes on Wednesday, 18 November 2026 at 19:00 UTC. The economic calendar lists US rate decisions under topic policy_rate and the minutes under policy_minutes, about three weeks after each decision, so you filter it for those two topics. The October and December 2026 decision and minutes pairs each have a 21-day gap.

Find decisions and minutes with the API

Use the economic calendar when you need the release dates in a model. Request US releases for a date range, then keep both policy topics so the decision and its minutes remain separate entries. Narwhal uses one account and one API key across its data APIs, and REST and MCP share that key.

  1. Put your API key in the environment Get a free API key and store it in NARWHAL_API_KEY. The request sends that value in the Authorization: Bearer YOUR_KEY header.
  2. Set the country and date range Use countries: "USA" for the US entries. The example requests 24 October 2026 through 31 January 2027, a range that includes decisions and minutes across the year boundary.
  3. Read the policy entries in date order Run the Python request with your environment variable set. It sorts the releases by at, or date when at is absent, and prints the topic, release time, name and status for policy_rate and policy_minutes.
    Python, FOMC decisions and minutes
    import os
    import requests
    
    r = requests.get("https://api.narwhalapi.com/v1/economics/calendar", timeout=10,
                     params={"countries": "USA", "start_date": "2026-10-24", "end_date": "2027-01-31", "limit": 100},
                     headers={"Authorization": f"Bearer {os.environ['NARWHAL_API_KEY']}"})
    r.raise_for_status()
    for x in sorted(r.json()["releases"], key=lambda x: x.get("at") or x.get("date", "")):
        if x.get("topic") in ("policy_rate", "policy_minutes"):
            print(x["topic"], x.get("at") or x.get("date"), x["name"], x["status"])
  4. Keep each timestamp with its topic In the printed result, retain the date together with its UTC time and topic. For the October 2026 decision, keep 28 October 2026 at 18:00 UTC with policy_rate; for the October 2026 minutes, keep 18 November 2026 at 19:00 UTC with policy_minutes.

The names are "Policy rate decision" and "Monetary policy minutes". Keep the topic alongside the time in your model so each entry retains its meaning. The country and date range go into the request parameters; the topic filter is in the loop that reads the response. Keep both topic values in that condition when your model needs decisions and minutes.

Keep the end date in mind when you want the minutes for a decision near the end of your range: the minutes have their own release date.

Read the dates or use a calendar feed

Open Central bank meetings to read meeting dates by month. The guide lists meetings for seven banks. Use the month view when your task is to find a meeting date and you want to read it without making an API request.

For a calendar app, use a calendar feed with families: ["policy_rate"]. That family puts rate decisions in your calendar app. If your task also needs the minutes, use the API filter for policy_minutes; the feed selection given here is for decisions. Decide whether you need a meeting date to read, an entry in your calendar app, or release data for a model before choosing the route.

Which option to use when

SituationBest optionWhy
Reading meeting datesCentral bank meetings guideLists dates by month for seven banks
Putting decisions in a calendar appFeed with the policy_rate familyPuts rate decisions in your calendar app
Using release dates in a modelEconomic calendar APIFilters US decisions and minutes by topic

For a model that needs both kinds of release, preserve the separate topics from the API response. A decision date and a minutes date answer different scheduling questions, even when they refer to the same meeting.

When are FOMC minutes published?

The October and December 2026 minutes are each scheduled three weeks after the corresponding decision. The October 2026 decision is 28 October 2026 at 18:00 UTC, and its minutes are 18 November 2026 at 19:00 UTC. The December 2026 decision is 9 December 2026 at 19:00 UTC, and its minutes are 30 December 2026 at 19:00 UTC.

Each pair is 21 calendar days apart. Use the separate policy_minutes entry for the publication time when you need the minutes in a schedule. The calendar also lists the January 2027 decision for 27 January 2027 at 19:00 UTC.

Why does the FOMC decision time change in UTC?

The decision time stays at 14:00 in New York, so its UTC time moves by an hour when US clocks change. The October 2026 decision is 28 October 2026 at 18:00 UTC while US daylight saving time lasts. The December 2026 decision is 9 December 2026 at 19:00 UTC in winter.

Use the timestamp attached to each calendar entry when you work in UTC. Carrying the October UTC hour over to the December decision would put that decision at the wrong time. The calendar time is the statement time.

Does the calendar include unscheduled FOMC meetings?

Only scheduled releases are in the economic calendar. Prediction markets track emergency cuts separately. For meeting odds, the meeting events include usa-fed-2026-10, usa-fed-2026-12 and usa-fed-2027-01. Use Read Fed rate odds when your question concerns the odds attached to a meeting.

Worked example: October 2026 meeting

Start with the October 2026 decision entry: Wednesday 28 October 2026 at 18:00 UTC. Read that timestamp as 14:00 on 28 October 2026 in New York. In Jakarta, the same statement time is 01:00 on 29 October 2026, so use the Jakarta date when you put the release into a Jakarta schedule.

Then take the minutes from the separate release entry, 18 November 2026 at 19:00 UTC. Count from the decision date, 28 October 2026, to the minutes date, 18 November 2026: the gap is 21 calendar days. Keep the minutes timestamp with that entry rather than copying the decision hour, because the October 2026 decision and its November 2026 minutes have different UTC times.

EntryDate and time
October 2026 decision in UTC28 October 2026 at 18:00 UTC
October 2026 decision in New York28 October 2026 at 14:00
October 2026 decision in Jakarta29 October 2026 at 01:00
October 2026 minutes in UTC18 November 2026 at 19:00 UTC
Gap between release dates21 calendar days

Published .