FRED — List Release Dates

Get release dates for all releases of economic data. Note that release dates are published by data sources and do not necessarily represent when data will be available on the FRED or ALFRED websites. Free API access requires a registered FRED API key. Documentation prepared only; business responses have not been runtime-verified.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
A key or file extension that indicates the type of file to send. string, optional, default: xml One of the following values: 'xml', 'json' xml = Extensible Markup Language. The HTTP Content-Type is text/xml. json = JavaScript Object Notation. The HTTP Content-Type is application/json. OpenAny import profile requires json explicitly; original XML/download formats remain in official documentation.
Optional parameters (7)
The start of the real-time period. For more information, see Real-Time Periods. YYYY-MM-DD formatted string, optional, default: First day of the current year
The end of the real-time period. For more information, see Real-Time Periods. YYYY-MM-DD formatted string, optional, default: 9999-12-31 (latest available)
The maximum number of results to return. integer between 1 and 1000, optional, default: 1000
non-negative integer, optional, default: 0
Order results by values of the specified attribute. One of the following strings: 'release_date', 'release_id', 'release_name'. optional, default: release_date
Sort results is ascending or descending release date order. One of the following strings: 'asc', 'desc'. optional, default: desc
Determines whether release dates with no data available are returned. The defalut value 'false' excludes release dates that do not have data. In particular, this excludes future release dates which may be available in the FRED release calendar or the ALFRED release calendar. If include_release_dates_with_no_data is set to true, the XML tag release_date has an extra attribute release_last_updated that can be compared to the release date to determine if data has been updated. One of the following strings: 'true', 'false'. optional, default: false

Sample response

{
  "count": 1129,
  "limit": 1000,
  "offset": 0,
  "order_by": "release_date",
  "realtime_end": "9999-12-31",
  "realtime_start": "2013-01-01",
  "release_dates": [
    {
      "date": "2013-08-13",
      "release_id": 9,
      "release_name": "Advance Monthly Sales for Retail and Food Services"
    },
    {
      "date": "2013-08-13",
      "release_id": 262,
      "release_name": "Failures and Assistance Transactions"
    },
    {
      "date": "2013-08-13",
      "release_id": 25,
      "release_name": "Manufacturing and Trade Inventories and Sales"
    },
    {
      "date": "2013-08-13",
      "release_id": 92,
      "release_name": "Selected Real Retail Sales Series"
    },
    {
      "date": "2013-08-13",
      "release_id": 188,
      "release_name": "U.S. Import and Export Price Indexes"
    },
    {
      "date": "2013-08-12",
      "release_id": 183,
      "release_name": "Gasoline and Diesel Fuel Update"
    },
    {
      "date": "2013-08-12",
      "release_id": 18,
      "release_name": "H.15 Selected Interest Rates"
    },
    {
      "date": "2013-08-12",
      "release_id": 269,
      "release_name": "National Accounts of Japan"
    },
    {
      "date": "2013-08-12",
      "release_id": 71,
      "release_name": "Weekly Treasury Inflation-Indexed Securities"
    },
    {
      "date": "2013-08-09",
      "release_id": 122,
      "release_name": "H.4.1 Factors Affecting Reserve Balances (data not included in press release)"
    },
    {
      "date": "2013-08-09",
      "release_id": 22,
      "release_name": "H.8 Assets and Liabilities of Commercial Banks in the United States"
    },
    {
      "date": "2013-08-09",
      "release_id": 63,
      "release_name": "M2 Related Series"
    },
    {
      "date": "2013-08-09",
      "release_id": 61,
      "release_name": "Money Zero Maturity (MZM)"
    },
    {
      "date": "2013-08-09",
      "release_id": 236,
      "release_name": "Monthly Housing Affordability Index"
    },
    {
      "date": "2013-08-09",
      "release_id": 78,
      "release_name": "St. Louis Monthly Reserves and Monetary Base"
    },
    {
      "date": "2013-08-09",
      "release_id": 105,
      "release_name": "St. Louis Weekly Reserves and Monetary Base"
    },
    {
      "date": "2013-08-08",
      "release_id": 255,
      "release_name": "Bank Rate Monitor's Weekly Survey"
    },
    {
      "date": "2013-08-08",
      "release_id": 53,
      "release_name": "Gross Domestic Product"
    },
    {
      "date": "2013-08-08",
      "release_id": 19,
      "release_name": "H.3 Aggregate Reserves of Depository Institutions and the Monetary Base"
    },
    {
      "date": "2013-08-08",
      "release_id": 283,
      "release_name": "H.3 Aggregate Reserves of Depository Institutions and the Monetary Base  (data not included in press release)"
    }
  ],
  "sort_order": "desc"
}

Response result

Response structure

Inferred from examples
  • countinteger
  • limitinteger
  • offsetinteger
  • order_bystring
  • realtime_endstring
  • realtime_startstring
  • release_datesobject[]
    • datestring
    • release_idinteger
    • release_namestring
  • sort_orderstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use FRED — List Release Dates with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.