---
title: "Upcoming data release calendar"
method: GET
path: "/api/v1/macro/releases"
tags: ["Economics"]
---

# Upcoming data release calendar

`GET /api/v1/macro/releases`

FRED data release schedule - when CPI, jobs report, GDP, and other key economic data will be published. Returns the next scheduled releases in chronological order; set upcoming=false for the most recent past releases. Narrow it to one release with release=cpi, release=50 or release=employment; /macro/releases/catalog lists what can be named.

## Query parameters

- `limit` integer — Maximum number of records to return.
- `offset` integer — Pagination offset (zero-indexed).
- `release` string, nullable — Narrow the calendar to one release: an id (10), a short alias (cpi, nfp, fomc), or part of a name (consumer price). See /macro/releases/catalog.
- `release_ids` string, nullable — Narrow the calendar to SEVERAL releases: a comma-separated list of ids, aliases or name fragments (each resolved like `release`), up to 10 entries. Mutually exclusive with `release`.
- `start` string, nullable — Window lower bound, YYYY-MM-DD inclusive. With `start`/`end` the calendar is served ascending inside the window; `upcoming` cannot be combined with an explicit window.
- `end` string, nullable — Window upper bound, YYYY-MM-DD inclusive. See `start`.
- `upcoming` boolean, nullable — True returns releases scheduled from today onward, soonest first - the default. False returns the most recent past releases, newest first. Cannot be combined with an explicit `start`/`end` window.
- `include_empty` boolean, nullable — Include release dates that carry no data yet. Scheduled future dates are always in this state, so it defaults to true when upcoming=true and false otherwise.

## Response `200`

FRED data release calendar entries.

- EnvelopeMacroReleasesData
  - `data` MacroReleasesData, required
    - `total` integer, required — Rows the upstream query matched across all pages, BEFORE the calendar window is applied. Not the number of upcoming releases.
    - `returned` integer, required — Release dates in this page after the calendar window is applied.
    - `filtered_out_before_today` integer, nullable — Rows this page dropped as already past; present only when non-zero.
    - `offset` integer, required — Pagination offset this page starts at.
    - `release_dates` ReleaseDate[], required — Release date entries.
      - `date` string, required — Observation date (YYYY-MM-DD).
      - `release_id` integer, required — FRED release identifier.
      - `release_name` string, required — FRED release name.
    - `source` string, required — Upstream data source identifier.
    - `fetched_at` string, required — When this payload was retrieved upstream (also in meta.data_time).
    - `release_id` integer, nullable — Release the calendar was narrowed to; absent when unfiltered.
    - `release_name` string, nullable — Name of that release; absent when unfiltered.
    - `filtered_out_outside_window` integer, nullable — Rows this page dropped as outside the explicit start/end window; present only when non-zero. The windowed sibling of filtered_out_before_today.
    - `release_ids` ReleaseIdEcho[], nullable — What the comma-separated `release_ids` tokens RESOLVED to, in canonical id order; absent unless the parameter was used.
      - `release_id` integer, required — Resolved FRED release identifier.
      - `release_name` string, nullable — Name from the release catalogue; null when the id is not in it.
    - `window` ReleaseWindowEcho
      - `start` string, nullable — Window lower bound as requested (YYYY-MM-DD), null when only `end` was given.
      - `end` string, nullable — Window upper bound as requested (YYYY-MM-DD), null when only `start` was given.
  - `meta` SugraMeta, required — Metadata attached to every /api/v1/* response envelope.
    - `endpoint` string, required — Requested endpoint path.
    - `data_time` string, required — ISO 8601 UTC timestamp of the source data, not of the request.
    - `response_time` string, required — ISO 8601 UTC timestamp when this response was produced.
    - `provider` string, required — API name and version.
    - `source` string, nullable — Identifier of the primary upstream source used for this response.
    - `attribution` string, nullable — Human-readable attribution mandated by an upstream source (e.g. a securities regulator or self-regulatory organization). Present only on responses whose source requires the owner and source to be clearly identified. Do not remove or alter it when using the response.
    - `fallback_used` boolean, nullable — True when the primary source failed and a fallback produced the data.
    - `fallback_chain` string[], nullable — Ordered list of sources attempted, in the order they were tried.
    - `cached` boolean, nullable — True when this response was served from the internal cache.
    - `stale` boolean, nullable — True when the cached response was returned after the upstream rate-limited or errored. Clients can use this to detect degraded data.

## Other responses

- `401` — Missing or invalid `x-api-key` header. JSON body with a stable `code` distinguishing `missing_api_key` (no header sent) from `invalid_api_key` (header sent, key not accepted); any other 401 source carries the generic `unauthorized` with its detail as `reason`. Plus `hint`. `plan` is always null on 401 - an unauthenticated request has no plan; quota exhaustion is 429, not 401.
- `422` — Validation Error
- `429` — Daily rate limit exceeded. Check `X-RateLimit-Reset` for the next window.
- `503` — Upstream source is temporarily unavailable. Retry after a short delay.

---

[API](https://skmtc.net/sugra/apis/sugra-api.md) · [All operations](https://skmtc.net/sugra/apis/sugra-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sugra/sugra-api/versions/4c4530760ba1/schema)