Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚨 Information for exchangerate.host users - this repository is dead 🚨 #245

Open
Rory-Reid opened this issue Oct 5, 2023 · 8 comments

Comments

@Rory-Reid
Copy link

Rory-Reid commented Oct 5, 2023

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:

dannyp11 added a commit to dannyp11/exchangerate-python-client that referenced this issue Oct 13, 2023
@Powerstone-gh
Copy link

Thanks for the update, it's true!

@rusq
Copy link

rusq commented Nov 1, 2023

For those searching for alternatives: https://github.com/fawazahmed0/currency-api

  • you will still have to rewrite your intergration.

@The-Compiler
Copy link

If you open an account for the new exchangerate.host, note that you will get spam to the email address you give them. And I don't just mean the 3 onboarding mails ("50% off"), but also:

  • Spam from APILayer itself ("What’s the Difference Between IP Geolocation and GPS-Based Location Services", "Sticky vs. Rotating Sessions Proxy: What Is the Best for Web Scraping")
  • Spam from third parties (!). To an email address I exclusively used for the new exchangerate.host page, I got an invitation for the Swiss Delphi Programmers Meetup (!?!), sent from Embarcadero Technologies, which just happens to have their address at the same place as Idera Inc. / APILayer.

@Rory-Reid
Copy link
Author

Thanks for that info, have added it to the key takeaways

@emanuellopess
Copy link

For anyone needing a API with a standard response I recommend this one. Below is a example of return:

URL: GET https://v6.exchangerate-api.com/v6/YOUR-API-KEY/latest/USD

{
	"result": "success",
	"documentation": "https://www.exchangerate-api.com/docs",
	"terms_of_use": "https://www.exchangerate-api.com/terms",
	"time_last_update_unix": 1585267200,
	"time_last_update_utc": "Fri, 27 Mar 2020 00:00:00 +0000",
	"time_next_update_unix": 1585353700,
	"time_next_update_utc": "Sat, 28 Mar 2020 00:00:00 +0000",
	"base_code": "USD",
	"conversion_rates": {
		"USD": 1,
		"AUD": 1.4817,
		"BGN": 1.7741,
		"CAD": 1.3168,
		"CHF": 0.9774,
		"CNY": 6.9454,
		"EGP": 15.7361,
		"EUR": 0.9013,
		"GBP": 0.7679,
		"...": 7.8536,
		"...": 1.3127,
		"...": 7.4722, etc. etc.
	}
}

@CheckSanity
Copy link

I am currently working on similar to the exchagerate.host API. The data taken from different free sources and central banks and provided as it is. All API completely free and without request limits, at least for now..
The project in the active development, so would appreciate for testing and giving feedback.
Thanks!

Official website
Repository

@sal0max
Copy link

sal0max commented Feb 5, 2024

I am currently working on similar to the exchagerate.host API. The data taken from different free sources and central banks and provided as it is. All API completely free and without request limits, at least for now.. The project in the active development, so would appreciate for testing and giving feedback. Thanks!

What do you mean by "at least for now.."?

It is be total understandable if you need to make money with the API in the long term. But this issue is the best example why you should communicate your plans straight ahead. It's not a good move, to bait people with a free API, only to pull the trigger at some point.

@CheckSanity
Copy link

I am currently working on similar to the exchagerate.host API. The data taken from different free sources and central banks and provided as it is. All API completely free and without request limits, at least for now.. The project in the active development, so would appreciate for testing and giving feedback. Thanks!

What do you mean by "at least for now.."?

It is be total understandable if you need to make money with the API in the long term. But this issue is the best example why you should communicate your plans straight ahead. It's not a good move, to bait people with a free API, only to pull the trigger at some point.

I totally agree, this will be a rat move.

The problem here is that I really don't have any plans. I am a single developer working and hosting this API and its infrastructure. The more people use the API, the greater the load will be and at some point I will not be able to support the project for free.

Right now, I don't have any plans to add monetization for the API and hope that monetization from the mobile app will cover all the stuff.

In any case, I will always inform about the future of the project via GIthub/website.
As far as this is a free service, anything can happen at any time and no one can give any guarantees

Thanks for the question and I hope I was able to answer it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants