FRED — Get Dates for Release

Retrieve release dates for a release of economic data with the FRED API. The request takes a release ID and a file type. Build a market research view or track changes over time. The GET request schema also lists release_id, file_type, realtime_start.

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
The id for a release. integer, required
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 (6)
The start of the real-time period. For more information, see Real-Time Periods. YYYY-MM-DD formatted string, optional, default: 1776-07-04 (earliest available)
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 10000, optional, default: 10000
non-negative integer, optional, default: 0
Sort results is ascending or descending release date order. One of the following strings: 'asc', 'desc'. optional, default: asc
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. One of the following strings: 'true', 'false'. optional, default: false

Sample response

{
  "count": 17,
  "limit": 10000,
  "offset": 0,
  "order_by": "release_date",
  "realtime_end": "9999-12-31",
  "realtime_start": "1776-07-04",
  "release_dates": [
    {
      "date": "1997-02-10",
      "release_id": 82
    },
    {
      "date": "1998-02-10",
      "release_id": 82
    },
    {
      "date": "1999-02-04",
      "release_id": 82
    },
    {
      "date": "2000-02-10",
      "release_id": 82
    },
    {
      "date": "2001-01-16",
      "release_id": 82
    },
    {
      "date": "2002-02-06",
      "release_id": 82
    },
    {
      "date": "2003-02-07",
      "release_id": 82
    },
    {
      "date": "2004-02-09",
      "release_id": 82
    },
    {
      "date": "2005-02-17",
      "release_id": 82
    },
    {
      "date": "2006-02-13",
      "release_id": 82
    },
    {
      "date": "2007-02-16",
      "release_id": 82
    },
    {
      "date": "2008-02-11",
      "release_id": 82
    },
    {
      "date": "2009-03-03",
      "release_id": 82
    },
    {
      "date": "2010-02-11",
      "release_id": 82
    },
    {
      "date": "2011-02-23",
      "release_id": 82
    },
    {
      "date": "2012-10-24",
      "release_id": 82
    },
    {
      "date": "2013-04-10",
      "release_id": 82
    }
  ],
  "sort_order": "asc"
}

Response result

Response structure

Inferred from examples
  • countinteger
  • limitinteger
  • offsetinteger
  • order_bystring
  • realtime_endstring
  • realtime_startstring
  • release_datesobject[]
    • datestring
    • release_idinteger
  • 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 — Get Dates for Release with your agent

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