EURIBOR 6M Rate API: 6-Month EURIBOR as JSON

Your app needs the current 6‑month EURIBOR to price loans, build amortization schedules, or compare funding costs, but you don’t want to scrape screens or maintain a data pipeline. By the end of this guide you will fetch EURIBOR 6M as clean JSON under the symbol EURIBOR_6M, read its effective date correctly, handle cache and business days, and compute a spread or monthly payment from the returned value.

What you get under EURIBOR_6M and when to use it

EURIBOR 6M is the 6‑month Euro Interbank Offered Rate. In the Interest Rates API, this tenor is available under the symbol EURIBOR_6M. It is returned as a numeric rate in percentage points (for example, 3.12 means 3.12% per annum), delivered as JSON via HTTPS with a simple api_key parameter.

Developers typically use EURIBOR 6M to:

Price floating‑rate mortgages or loans indexed to 6‑month EURIBOR.
Compute term funding costs and transfer pricing in treasury systems.
Calculate spreads to other benchmarks for hedging or analytics.

Important: you do not set a base currency for EURIBOR. Do not send a base parameter like base=USD. Request EURIBOR_6M directly.

How to call the API for EURIBOR 6M

The latest 6‑month EURIBOR is exposed by a single GET endpoint. You pass your API key as api_key and specify symbols=EURIBOR_6M. Starter is $19/month (1 symbol per latest request) with a 7‑day trial, and you can register for an API key here: Register.

To see the official latest request for EURIBOR_6M and its JSON response, use the following block exactly as shown below.

curl "https://interestratesapi.com/api/v1/latest?api_key=YOUR_API_KEY&symbols=EURIBOR_6M"

Reading the JSON

In the JSON above you will typically rely on:

The top‑level success flag to detect errors. If it is false, inspect the accompanying error fields (as shown in the same payload) and do not use the rate.
The effective date provided in the payload (look for fields labeled date, effective_date, or a similar key shown in the sample) to understand the business day the rate applies to.
The numeric value under the EURIBOR_6M key in the rates or data object shown. That number is a percentage value (e.g., 3.12 means 3.12% per annum, not a decimal like 0.0312).

When persisting this result, store both the numeric value and the effective date to avoid mixing rates across days in downstream calculations.

Python example: fetch EURIBOR_6M and compute with it

The following Python example calls the same latest endpoint for EURIBOR_6M, checks for errors, and demonstrates how to compute a spread and a monthly payment using the returned value. Replace YOUR_API_KEY with your actual key from the registration page.

import requests
from math import pow

API_KEY = "YOUR_API_KEY"
URL = "https://interestratesapi.com/api/v1/latest"
params = {
    "symbols": "EURIBOR_6M",
    "api_key": API_KEY,
}

resp = requests.get(URL, params=params, timeout=10)
resp.raise_for_status()
data = resp.json()

# Basic validation
if not data.get("success", True):
    # Inspect error structure present in the payload and handle/log accordingly
    raise RuntimeError(f"API error: {data}")

# Extract the effective date field shown in the payload
effective_date = data.get("date") or data.get("effective_date") or data.get("timestamp")
# Extract the 6M EURIBOR numeric rate (percentage value)
euribor_6m = None
if "rates" in data and isinstance(data["rates"], dict):
    euribor_6m = data["rates"].get("EURIBOR_6M")
elif "data" in data and isinstance(data["data"], dict):
    euribor_6m = data["data"].get("EURIBOR_6M")

if euribor_6m is None:
    raise ValueError("EURIBOR_6M not present in response")

print(f"EURIBOR_6M={euribor_6m}%, effective_date={effective_date}")

# Example 1: compute a spread to an internal funding rate (both as percentages)
internal_funding_rate = 2.00  # e.g., your internal transfer price in %
spread_bps = (internal_funding_rate - euribor_6m) * 100  # basis points
print(f"Spread vs internal funding: {spread_bps:.1f} bps")

# Example 2: compute a monthly payment for an interest-only accrual or annuity
principal = 250000.00  # loan principal in EUR
annual_rate_pct = euribor_6m + 1.50  # add a 150 bps margin, for example
annual_rate = annual_rate_pct / 100.0
monthly_rate = annual_rate / 12.0

# Annuity payment formula (fixed-rate approximation over one month step)
months = 360  # 30-year schedule
if monthly_rate == 0:
    payment = principal / months
else:
    payment = principal * (monthly_rate * pow(1 + monthly_rate, months)) / (pow(1 + monthly_rate, months) - 1)

print(f"Monthly payment (approx): {payment:.2f} EUR")

Notes on units and formulas:

The API returns a percentage value for EURIBOR_6M. Convert it to a decimal for math by dividing by 100.
For interest‑only accruals, the monthly interest is principal × annual_rate_decimal / 12.
For floating loans that reset every six months, recalculate schedules when you refresh EURIBOR_6M on its reset date.

Two‑symbol spreads using convert

If your application needs a direct two‑symbol comparison (e.g., to compute a loan spread between two benchmarks within one request), use the convert endpoint. The official example below shows a request involving EURIBOR_3M and SOFR. This is a different tenor than EURIBOR_6M, but it demonstrates the mechanics of convert and how dual‑symbol outputs are returned. When you need a spread involving EURIBOR_6M, first fetch EURIBOR_6M with /api/v1/latest as shown above and then use /convert where appropriate in your workflow.

curl "https://interestratesapi.com/api/v1/convert?from=SOFR&to=EURIBOR_3M&amount=500000&term_months=24&api_key=YOUR_API_KEY"

The example prints a EURIBOR_3M value alongside SOFR on their respective effective dates. Do not treat this 3‑month rate as a 6‑month value. To work specifically with EURIBOR_6M, keep your latest request scoped to symbols=EURIBOR_6M and, when comparing against another benchmark, ensure both symbols are clearly defined in your logic.

Operational details that save you time

Publication cadence and business days

Interbank benchmarks like EURIBOR are business‑day series. Expect updated values on applicable business days, with no new values on weekends and market holidays. Your application should:

Display the effective date from the payload to clarify which business day the rate applies to.
Carry forward the most recent business‑day rate when the market is closed, unless your policy requires otherwise.

Units and base currency

EURIBOR_6M is returned as a percentage value per annum (e.g., 3.12 means 3.12% per year).
There is no base currency parameter to set for EURIBOR. Do not add a base=… query string for this endpoint.

Dates and time zones

Use the effective date field supplied in the response as the canonical “as‑of” date for storage and display.
If a timestamp is present, treat it as the server’s publication time; the effective business date is what matters for financial calculations.

Caching and refresh policy

Cache the latest response for the current calendar day and re‑fetch on the next business day, or at your morning batch time.
For intraday processes that can tolerate stale data when markets are closed, revalidate on a schedule that aligns with your SLAs (e.g., hourly on business days, daily on weekends).

Error handling: success=false and missing fields

Always check the success flag in the JSON. If false, inspect the accompanying error details included in the same payload and retry or surface a clear message to the user.
If EURIBOR_6M is missing from the data structure (e.g., rates or data object), treat the response as incomplete and do not calculate with it.
Implement a fallback: keep the most recently stored valid EURIBOR_6M until the next successful refresh, and log anomalies for review.

End‑to‑end: from sandbox to production

You can go live in minutes using this checklist:

Register for an API key (7‑day trial).
Copy your api_key from the dashboard.
Call GET /api/v1/latest with symbols=EURIBOR_6M and api_key=YOUR_API_KEY.
Persist both the numeric rate and the effective date in your datastore.
When you need a two‑benchmark spread in one flow, use /convert. For full request/response details and model coverage, see MCP.
Set a refresh schedule aligned with business days and your downstream batch windows.

How to compute with EURIBOR_6M safely

Many production mistakes come from unit mismatches or timing assumptions. These tips help avoid them:

Always treat EURIBOR_6M as a percentage. Convert to a decimal (divide by 100) before applying compounding or discounting.
Document the reset convention in your product code. If a loan resets semi‑annually off EURIBOR 6M, use the latest rate only at reset dates; otherwise continue with the locked‑in coupon until the next reset.
When quoting customer rates, separate benchmark and margin clearly (e.g., coupon = EURIBOR_6M + margin). Store both components.
For back‑testing or analytics across days, key joins on the effective date from the payload rather than local system time.

Troubleshooting common integration issues

Getting a USD‑based response: remove any base parameter; it is not needed for EURIBOR_6M.
Empty rate on weekends: that is expected for a business‑day series. Use the last valid business‑day value and the effective date to label it.
success=false: read the error object returned in the same payload, correct the request (e.g., symbol typo, missing api_key), and retry with backoff.
Drift between your stored date and the API’s date: always rely on the effective date from the API when writing to your database.

FAQ

Q: What symbol should I request to get the 6‑month EURIBOR?
A: Use symbols=EURIBOR_6M with the latest endpoint. Do not include a base currency parameter.

Q: What does the numeric value represent?
A: It is a percentage value per annum (e.g., 3.12 means 3.12% yearly). Convert to a decimal by dividing by 100 before running interest or discount formulas.

Q: How do I know which day the rate applies to?
A: Use the effective date field present in the JSON payload (as shown in the official sample). Store and display this date alongside the rate.

Q: How should I compute a spread to another benchmark?
A: If both benchmarks can be retrieved together, use /convert. Otherwise, fetch EURIBOR_6M with /api/v1/latest and subtract it from the other benchmark, keeping both in percentage points and aligned on the same effective date.

Q: Can I cache the result?
A: Yes. Cache the latest response for the current day and refresh on the next business day or at your batch window. On weekends or holidays, carry forward the last business‑day value if your policy allows.

Ready to plug the 6‑month EURIBOR into your pricing engine? Start your 7‑day trial and get your API key: Register. For endpoint coverage and model references, see MCP.