API Bouncer

Buy me a coffee

FRED

Economic data from the Federal Reserve Bank of St. Louis

FinanceAuth: API KeyHTTPS: YesCORS: yesStatus: alive

Last verified: April 1, 2026

Getting Started

This API requires an API key for authentication. Here's how to get started:

  1. Sign up — Visit the API's website and create a free account.
  2. Get your key — After signing up, you'll receive a unique API key (usually found in your dashboard or account settings).
  3. Include it in requests — Add your API key to each request, typically as a query parameter (?api_key=YOUR_KEY) or in the request header (Authorization: Bearer YOUR_KEY). Check the API's documentation for the exact format.

API keys are free for most public APIs. They're used to identify your application and enforce rate limits — not to charge you.

CORS Support

This API supports CORS (Cross-Origin Resource Sharing), meaning you can call it directly from browser-based JavaScript applications without running into cross-origin errors.

Quick Example

// Using cURL curl -H "Authorization: Bearer YOUR_API_KEY" https://fred.stlouisfed.org/docs/api/fred/
// Using JavaScript fetch() const response = await fetch(apiUrl, { headers: { 'Authorization': 'Bearer YOUR_API_KEY' } }); const data = await response.json();

About FRED

FRED is a free API in the Finance category. It requires a free API key, which you can obtain by signing up on their website. This API supports HTTPS for secure connections and supports CORS, making it suitable for direct browser-based requests.

What You Can Build With FRED

FRED fits naturally into projects that touch the Finance space. Here are a few directions developers commonly take when working with APIs in this category — any of them could be a fit depending on the specific endpoints FRED exposes:

  • Stock price trackers — pull data from FRED, transform it into a UI-friendly shape, and surface it to users in a dashboard, mobile app, or browser extension.
  • Portfolio management dashboards — pull data from FRED, transform it into a UI-friendly shape, and surface it to users in a dashboard, mobile app, or browser extension.
  • Financial news aggregators — pull data from FRED, transform it into a UI-friendly shape, and surface it to users in a dashboard, mobile app, or browser extension.
  • Banking and payment integrations — pull data from FRED, transform it into a UI-friendly shape, and surface it to users in a dashboard, mobile app, or browser extension.

If a specific use case isn't listed, scroll back to the code examples above and adapt the request shape to match the endpoint you need. Most Finance APIs follow similar request/response patterns, so the snippet that works for one endpoint usually works for the rest with small tweaks.

Integrating FRED Step by Step

1. Skim the documentation first. Open the link above and look for two things: the base URL pattern and a list of available endpoints. Knowing both up front saves you from guessing parameter names or formats. Most providers also publish example responses next to each endpoint — copy one into your editor as a reference for the JSON shape your code will be parsing.

2. Get an API key. FRED uses API key authentication. Sign up on the provider's site, look for a developer dashboard or API section in your account settings, and copy your key somewhere safe. Treat it like a password — don't paste it into a public repo or a client-side bundle that ships to a browser. Read our API security guide if you're unsure how to keep keys out of source control.

3. Make a request from the command line. Before wiring an API into your application, send a single request with curl or your HTTP client of choice. Confirm that the response shape matches what the docs promised. If it doesn't, your application code would have hit the same surprise — better to find out now while you only have one terminal window to debug.

4. Wire it into your code. Once a manual request works, copy that request into your application as a function. Add error handling: APIs return 4xx and 5xx codes for client and server errors respectively, and your code needs to behave reasonably when one comes back. Our error-handling guide covers the patterns that make this less painful.

5. Calling from the browser is fine. FRED supports CORS, so a frontend-only project can hit it directly with fetch(). Watch out for two gotchas: never embed an API key in client-side code (anyone can read it from devtools), and remember that browser requests count against the same rate limit as server requests.

Common Issues and How to Fix Them

  • "401 Unauthorized" or "403 Forbidden": the most common cause is a missing or incorrectly placed API key. Check whether FRED expects the key as a query string parameter, an Authorization header, or a custom header — every provider does it slightly differently. The official docs will say which.
  • The key works in curl but not in your app: almost always a header-encoding bug. Print the exact request your client sends and compare it to your working curl command. Look for missing quotes, extra spaces, or a header name typo.
  • "CORS policy" error in the browser: FRED is listed as supporting CORS, but headers can change. If you hit a CORS error, double-check that you're sending only allowed headers (no custom X- headers unless documented) and that you're not setting credentials: 'include' unnecessarily.
  • Rate limiting (429 Too Many Requests): if you start seeing 429s, you've crossed the API's per-minute or per-day quota. Add exponential backoff with retries, cache responses where possible, and consider whether a paid tier or alternative API is warranted. Our rate limit guide covers this in depth.
  • Inconsistent response shape: if FRED's response sometimes includes a field and sometimes doesn't, that's normal — APIs often omit null values. Defensive code that checks for property existence before reading it survives schema changes far better than code that assumes everything is always present.

FRED in the Finance Ecosystem

Finance APIs deliver stock prices, market data, banking information, and financial analytics. Build trading dashboards, portfolio trackers, or fintech applications with real-time financial data.

FRED is one of dozens of free Finance APIs we've catalogued. Some are nearly interchangeable; others have distinct strengths and weaknesses that only become clear when you read their docs side-by-side. If FRED doesn't quite fit your project, the Finance category page lists every alternative we know about, with auth and CORS columns so you can compare at a glance.

When evaluating Finance APIs, the criteria that matter most are typically: rate limits on the free tier, freshness of the underlying data, regional coverage (does it work for your users' geography?), and how active the provider's maintenance schedule is. APIs that haven't been updated in years tend to drift out of sync with the underlying data sources, even if they technically still respond.

Frequently Asked Questions

What financial data can I access through FRED?

FRED is a finance API that may provide data such as stock prices, exchange rates, market indices, cryptocurrency values, or economic indicators. The specific data depends on the API's focus area. Review the endpoint documentation to see which financial instruments and data points are covered.

Does FRED provide real-time market data?

Real-time data availability varies across finance APIs. Some provide live streaming prices, others offer data with a 15-minute delay (common for free tiers), and some focus on end-of-day summaries. Check FRED's documentation to confirm the data latency and whether real-time feeds are available on the free plan.

Can I use FRED to track cryptocurrency prices?

Whether FRED covers cryptocurrency depends on its specific focus. Some finance APIs specialize in crypto, others cover traditional markets, and some handle both. Visit the API documentation to see if crypto endpoints are available. You can also browse our Finance APIs for other options that may cover digital assets.

Is FRED free to use?

Yes, FRED is listed as a free public API. You will need to create a free account to get an API key, but the key itself is free. Some APIs have rate limits on their free tier, so check the official documentation for current limits.

Is FRED still working in 2026?

Yes! According to our most recent health check (FRED's last ping: 2026-04-01 13:39:46), this API is responding normally. We periodically verify all listed APIs to ensure they are still online and functioning.