You have not supplied an API Access Key error

[over-engineer]

You have not supplied an API Access Key error

[kwerty]

If the https://ratesapi.io/ and https://exchangerate.host/ APIs are able to provide the exact same API responses, perhaps @over-engineer might consider making a one line fix to switch to one of these?

[over-engineer]

Hey @mickyjohnstonmonotype, thanks for bringing this to my attention! It's unfortunate that exchangeratesapi.io (afaict) changed without any prior notice.

Likely, this wrapper works with pretty much any Fixer.io-compatible API. That means, switching to ratesapi.io was a drop-in replacement, like @kwerty suggested.

I just pushed an update to npm, so it now uses ratesapi.io by default. 😄

You just have to update to the latest version (1.1.0) and everything will be back to normal. No breaking changes.

---

I've also added a new setApiBaseUrl() function, which allows you to use a different API (any Fixer.io-compatible API will probably work).

See Using a different API.

For example, you can switch to exchangerate.host like this:

const { exchangeRates } = require('exchange-rates-api');

(async () => {
    await exchangeRates()
        .setApiBaseUrl('https://api.exchangerate.host')
        .latest()
        .fetch();    // {THB: 34.978, PHP: 58.159, …, HUF: 323.58}
})();

[kwerty]

The alternative API is now blocking CORS also.

Good thinking ahead @over-engineer ! Switched to another API with ease

await exchangeRates().setApiBaseUrl('https://api.exchangerate.host').