-
Notifications
You must be signed in to change notification settings - Fork 9
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
Real time API #23
Comments
Thank you for your suggestion. I previously overlooked a similar request (#14) because I prioritized caching. However, I now believe that adding multiple APIs as a feature for users to choose from would be beneficial. BitPay has limitations with the available conversions, so I will explore other free and open APIs that we can utilize. |
Hi, I have added support for additional API options. You can read more about them here. Currently, the free tier for all the suggested APIs updates only once a day, while the premium tiers are updated more frequently. I welcome any other API suggestions you may have. I also looked into the BitPay API that you suggested, but I found that this API only supports the base currencies of BTC or BCH. Alternatively, it would be beneficial if someone could independently manage a fork of fawazahmed0/exchange-api that updates approximately every 60 minutes. The same technology stack (Cloudflare Workers and GitHub Actions) could be used to make this possible. I am attaching the zip files containing the latest changes so you can test them out and provide your feedback. CurrencyConverter-1.5.2-x64.zip |
Hello, this plugin is really useful. The only thing I would improve is using a more up-to-date API. I believe the current one updates once a day. For users who really need to make conversions constantly, I think having updated information is essential.
I made a PoC (https://github.com/cospin/PowerToys-Run-Currency-Converter) with the BitPay API. It would be perfect to explore other free APIs or use BitPay (limited to USD and cryptos) as first choice to USD/crypto.
Regards!
The text was updated successfully, but these errors were encountered: