Currency API

Now 170+ Currencies, Plus Gold and Silver Prices and Bid Spread

Our September 24 release expands what you can build with Currencylayer, Fixer and ExchangeRatesAPI: 170+ fiat currencies, verified gold and silver prices, and optional bid/ask spread data.

This release brings the following updates. All of them are backward compatible, so existing integrations keep working without modification.

Expanded currency coverage: 170+ fiat currencies

We’ve added 8 new ISO 4217 fiat currency codes: BYN, CNH, MRU, MXV, SLE, SSP, STN and XCG, bringing support to 170+ fiat currencies. We’ve also retired 3 superseded codes: EEK, MRO and VEF. Every new currency is available across all endpoints: live rates, historical lookups, conversions and time series.

Product

Endpoints

Currencylayer

/live, /historical, /convert, /timeframe, /change

Fixer

/latest, /YYYY-MM-DD, /convert, /timeseries, /fluctuation, /symbols

ExchangeRatesAPI

/latest, /YYYY-MM-DD, /convert, /timeseries, /fluctuation, /symbols

Historical data for the new currencies is available from August 25, 2026 onward, and earlier dates return a descriptive error. For the full list of supported currencies, see the Currencylayer documentation or call /symbols (Fixer, ExchangeRatesAPI).

Gold and silver prices

XAU (gold) and XAG (silver) are now verified and available on all three products, through the same endpoints listed above. Prices are quoted per troy ounce.

Bid/ask spread data (Professional and above)

A new optional parameter returns bid and ask prices alongside the standard rate, so you can analyze spreads and price more accurately in financial applications. Add &spread=1 to a live rates request:

				
					# Currencylayer
GET https://api.currencylayer.com/live?access_key=YOUR_KEY&spread=1
 
# Fixer
GET https://data.fixer.io/api/latest?access_key=YOUR_KEY&spread=1
 
# ExchangeRatesAPI
GET https://api.exchangeratesapi.io/v1/latest?access_key=YOUR_KEY&spread=1

				
			

With &spread=1, each currency returns an object instead of a single number:

				
					{
  "rates": {
    "EUR": {
      "rate": 0.9214,
      "bid": 0.9212,
      "ask": 0.9216,
      "spread": 0.0004
    }
  }
}

				
			

Without &spread=1, responses are unchanged. A few details to know:

  • Plans: Professional and Enterprise get full bid/ask/spread data. Free and Basic plans receive an error with an upgrade message.
  • Endpoints: /live (Currencylayer) and /latest (Fixer, ExchangeRatesAPI) accept &spread=1.
  • Coverage: where bid/ask isn’t available for a currency, only the standard rate is returned.

Why it matters for developers

More coverage and richer pricing data remove the edge cases that slow teams down.

  • Fewer unsupported-currency errors. Serve customers in more markets without special handling for missing currencies.
  • Precious metals in the same place. Get gold and silver prices from the same service as your currency rates.
  • Better pricing context. Bid/ask spread data supports spread analysis and more accurate pricing.
  • No migration work. Nothing breaks, and nothing needs to change unless you want the new features.

STAY CONNECTED

Related posts
Currency API

How Developers Handle Currency Symbols, Codes & Formatting Using Exchange Rate APIs

Currency APIIP API

Introduction to Fixer.io: The Basics of Forex Rate APIs

Currency API

Build a Real-Time Currency Converter with Fixer API

Currency API

7 Best Free Currency Converter APIs In 2026