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

Suggestion: Use exchangeratesapi.io API to convert money #47

Closed
JBey4you opened this issue Jun 25, 2018 · 4 comments
Closed

Suggestion: Use exchangeratesapi.io API to convert money #47

JBey4you opened this issue Jun 25, 2018 · 4 comments

Comments

@JBey4you
Copy link

Hi,

May I suggest you to use https://exchangeratesapi.io API? It's free, has no limit and is based on the European Central Bank's service. Users wouldn't have to create an account on openexchangerates.org to get an App ID and they could convert currencies with no limit.

@deanishe
Copy link
Owner

deanishe commented Jun 25, 2018

I actually looked at the ECB when I originally wrote the workflow, and rejected it as a source due to the very limited number of currencies it has rates for. OTOH, Yahoo! Finance was an option at that time (and is what I originally went with).

EDIT: This is actually a lie. The first version of the workflow did use the ECB data. I dumped it for Yahoo! Finance in v2.0 #1

I think the request limits of Open Exchange Rates' free tier are moot in the context of your suggestion. The workflow caches the rates rather than hitting OER's API every time you do a conversion, so the number of conversions you do is irrelevant. Only the frequency with which you update rates matters. The free tier's limit of 1000 requests/month allows for hourly updates. If that's not frequently enough for you, then the ECB is certainly no good as a data source, as their rates are only updated once a day.

Using exchangeratesapi.io strikes me as pointless: The rates can easily be retrieved directly from the ECB site, and I have more confidence in the ECB's site staying up than in a free site with no apparent business model.

All that said, it is a PITA having to get an API key in order to perform currency conversions.

Using the ECB data by default would eliminate that: folks who need exchange rates the ECB doesn't provide would have to sign up with Open Exchange Rates, but the workflow could work "out of the box" for a lot of people (certainly, I've personally never needed a rate the ECB doesn't provide).

But I think a better solution might be to cache the OER rates in some form on my own server, eliminating the need for users to sign up for their own access.

I'll ask OER if that's acceptable.

@m-baumgartner
Copy link

All that said, it is a PITA having to get an API key in order to perform currency conversions.

Using the ECB data by default would eliminate that: folks who need exchange rates the ECB doesn't provide would have to sign up with Open Exchange Rates, but the workflow could work "out of the box" for a lot of people (certainly, I've personally never needed a rate the ECB doesn't provide).

Hey, any updates on this?
I'm presonally favorable to a simple solution based on ECB as I don't need more currencies than the ones supported there.
Maybe a good workaround for folks who DO need more currencies would be to keep the current 'openexchangerates' based solution as a fallback.

@cataclysmicvoid
Copy link

Screen Shot 2020-02-19 at 10 24 52 PM

Stumbled across this suggestion from before — and now since I can't get the api key to work with NIS currency it seems relevant again. Conversions work just fine with other currencies though! Tried a new api key to no avail.

Thanks again for great workflow.

@deanishe
Copy link
Owner

I can't get the api key to work with NIS currency

The symbol has changed. Israeli shekel is now ILS

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

No branches or pull requests

4 participants