Exchange-Rate API Monitoring in 2026: Freshness Checks, Cache State, and Incident Runbooks

What to Monitor

Step-by-Step Workflow

API Examples for the Runbook

curl -i "https://api.currency-exchange.app/v1-get-currency-exchange-rate?from=USD&to=EUR&skipCache=true&cacheTimeSeconds=0" \
  -H "x-api-key: YOUR_API_KEY"

curl -i "https://api.currency-exchange.app/v1-convert-currency?from=USD&to=GBP&amount=2500&getPerformanceData=1" \
  -H "x-api-key: YOUR_API_KEY"

curl "https://api.currency-exchange.app/v1-convert-currency?from=USD&to=EUR&amount=980&date=2026-04-30" \
  -H "x-api-key: YOUR_API_KEY"

curl "https://api.currency-exchange.app/v1-download-api-usage?from=2026-05-01&to=2026-05-20&service=currency&format=csv" \
  -H "x-api-key: YOUR_API_KEY"

TypeScript Freshness Check

type RateProbe = {
  requestedAt: string;
  from: string;
  to: string;
  exchangeRate: number;
  rateTime: string;
  provider?: string;
  cached?: boolean;
  ageSeconds: number;
  rateLimit: {
    limit: string | null;
    remaining: string | null;
    reset: string | null;
  };
};

function secondsBetween(leftIso: string, rightIso: string) {
  return Math.abs(Date.parse(leftIso) - Date.parse(rightIso)) / 1000;
}

export async function probeExchangeRate({
  from,
  to,
  maxAgeSeconds,
}: {
  from: string;
  to: string;
  maxAgeSeconds: number;
}): Promise<RateProbe> {
  const requestedAt = new Date().toISOString();
  const url = new URL('https://api.currency-exchange.app/v1-get-currency-exchange-rate');
  url.searchParams.set('from', from);
  url.searchParams.set('to', to);
  url.searchParams.set('skipCache', 'true');
  url.searchParams.set('cacheTimeSeconds', '0');

  const response = await fetch(url, {
    headers: { 'x-api-key': process.env.FX_API_KEY ?? '' },
  });

  const rateLimit = {
    limit: response.headers.get('X-RateLimit-Limit'),
    remaining: response.headers.get('X-RateLimit-Remaining'),
    reset: response.headers.get('X-RateLimit-Reset'),
  };

  if (!response.ok) {
    throw new Error(`Rate probe failed with status ${response.status}`);
  }

  const data = (await response.json()) as {
    from: string;
    to: string;
    exchangeRate: number;
    rateTime: string;
    provider?: string;
    cached?: boolean;
  };

  if (!data.rateTime || Number.isNaN(Date.parse(data.rateTime))) {
    throw new Error('Rate probe returned no parseable rateTime');
  }

  const ageSeconds = secondsBetween(requestedAt, data.rateTime);

  if (ageSeconds > maxAgeSeconds) {
    throw new Error(`Rate age ${ageSeconds}s exceeded policy ${maxAgeSeconds}s`);
  }

  return {
    requestedAt,
    from: data.from,
    to: data.to,
    exchangeRate: data.exchangeRate,
    rateTime: data.rateTime,
    provider: data.provider,
    cached: data.cached,
    ageSeconds,
    rateLimit,
  };
}

The example is intentionally small. In production, write successful probes to your logging platform or warehouse and route failures into the same on-call or finance-ops queue that handles payment and pricing incidents. For large catalogs or backfills, repeat documented calls through your own queue and throttle from the rate-limit headers rather than assuming a native batch endpoint.

Decision Matrix: One Freshness Policy Is Not Enough

Alert Rules That Actually Help

Commercial Review Questions

Monitoring also belongs in the buying conversation. A low entry price or generous monthly credit pack can be a good fit, but procurement should still ask how the service behaves when a rate becomes a customer-visible number. The commercial risk is not only the invoice. It is the cost of explaining a conversion after the business has already acted on it.

This is where rate-language discipline matters. "Live", "real-time", "updated every second", and "60-second updates" are not the same operational promise unless the vendor defines them in the contract or response evidence. For Currency-Exchange.app, the safer implementation path is to store rateTime and verify the observed freshness in your own logs.

FAQ