-
Notifications
You must be signed in to change notification settings - Fork 33
Description
It looks like people have been submitting and discussing a few issues here ever since it went down, then went back up with the API key constraint. I'm submitting this information just as an observer.
From my understanding, this github project is dead and so is the original exchangerate.host service you relied on. It appears to have been acquired by APILayer who have binned it off and pointed the domain to their own api. They seem to have a few of these all implemented the same (even the response body for this api now references "currencylayer") e.g.:
It looks like they are in the process of setting up a public github repository for this specific service here: https://github.com/apilayer/exchangerate-API (as linked from https://exchangerate.host/documentation) where I imagine support will be addressed
I don't think there's any point raising new issues here.
The most valuable takeaways if you use this service:
- You need an API key now
- The API request and response has changed, you'll have to rewrite your integration
- Issues submitted in this github repository will not be addressed. This repository may even disappear.
- Sign up with an email address for an inbox you don't value