Skip to main content
Coverage is more than a list of currencies or countries. Before using a rate, confirm three things: your plan can query it, it has a publishable observation, and history exists for the required date.

Current coverage

A rate can be registered without having an observation available at this instant. Always check the rate resource before displaying or calculating with a value:
  • In V2 multi-market, GET /v2/fx/{CC}/rates lists the rates available for a country. Its V2 catalogue explains published IDs, and the per-plan matrix shows access to each one.
  • In deprecated V1, GET /v1/fx/rates lists the rates available to your API key. The dashboard export section also shows historical coverage for the series available to your account.
Do not construct an ID from a commercial name or replace a rate with another just because both share a currency.

Historical coverage

The maximum lookback is the more restrictive of your plan’s retention and the series’ actual history. A start date applies to every series in both V1 and V2: a series can have started later, have gaps, or not publish data on weekends and holidays. These limits apply to historical endpoints. If a date or range start exceeds retention, the API returns 403 history_out_of_retention; error details identify the applied limit. A known series without history can return 404 history_not_available; a date without an observation can return 404 rate_not_found.

Availability by market

Coverage varies by country, rate, and plan. Check the V2 catalogue and per-plan matrix; use the ID returned by the API to check the current observation and the historical range you need. A series may not publish on weekends, holidays, or other days without a capture.

Checking an integration

  1. Request available rates through the endpoint for your version.
  2. Retain the exact ID and inspect updated_at; when available, inspect effective_date, stale, and staleness_sec as well.
  3. Request history with that same ID and the needed range. Do not fill days that the series did not publish in your application.
  4. Treat 402 as missing plan access, 403 history_out_of_retention as a disallowed range, and historical 404s as an absent series or observation; retries do not resolve them.
See V2 history or, if you maintain an older integration, deprecated V1 history.