Details
-
Type: Story
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.2.0-b1
-
Component/s: None
-
Labels:None
Description
The exchange rate processors that we have/had (Yahoo Finance, Google Finance, etc.) can be unreliable as they may scrape a website for the exchange rate (and the page can change, breaking the scrape), the accuracy may not be accurate, or in the case of Yahoo Finance, the service can be discontinued abruptly without notice.
It would be better to also support a dedicated exchange rate processing service that provides an API and API key for fetching rates. These services can require a paid subscription, so they should be added in addition to the free (but potentially unreliable) ones that currently exist in Blesta. Because of the necessity to support an API key, exchange rate processors should be able to inject a set of fields to save as settings for the processor.
Consider the following new exchange rate processors:
- Currency Layer
- Free version supports up to 1000 API calls per month, updated hourly
- Open Exchange Rates
- Free version supports up to 1000 API calls per month, updated hourly.
- Free version is LIMITED TO USD AS BASE CURRENCY! We may be able to work-around this by converting the rate with respect to the base currency configured in Blesta.
- European Central Bank
- Data is provided via XML on a daily work-day-basis after 4 PM CET
- XML available @ http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml
- CURRENCIES ARE LIMITED
- Fixer.io (
CORE-2536)- Example: http://api.fixer.io/latest?base=USD
- CURRENCIES ARE LIMITED
- X-RATES (
CORE-2534)- Example: http://www.x-rates.com/calculator/?from=GBP&to=USD&amount=1
- CURRENCIES ARE LIMITED
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Issue Type | Story [ 7 ] | Epic [ 6 ] |
Epic Name | Exchange Rate Processors |
Epic Color | ghx-label-9 |
Issue Type | Epic [ 6 ] | Story [ 7 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Description |
The exchange rate processors that we have/had (Yahoo Finance, Google Finance, etc.) can be unreliable as they may scrape a website for the exchange rate (and the page can change, breaking the scrape), the accuracy may not be accurate, or in the case of Yahoo Finance, the service can be discontinued abruptly without notice.
It would be better to also support a dedicated exchange rate processing service that provides an API and API key for fetching rates. These services can require a paid subscription, so they should be added in addition to the free (but potentially unreliable) ones that currently exist in Blesta. Because of the necessity to support an API key, exchange rate processors should be able to inject a set of fields to save as settings for the processor. Consider the following new exchange rate processors: # [Currency Layer|https://currencylayer.com/product] #* Free version supports up to 1000 API calls per month, updated hourly # [Open Exchange Rates|https://openexchangerates.org/signup] #* Free version supports up to 1000 API calls per month, updated hourly. #* Free version is LIMITED TO USD AS BASE CURRENCY! We may be able to work-around this by converting the rate with respect to the base currency configured in Blesta. # [European Central Bank|http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml] #* Data is provided via XML on a daily work-day-basis after 4 PM CET #* XML available @ http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml #* CURRENCIES ARE LIMITED # [Fixer.io|http://fixer.io/] #* Example: http://api.fixer.io/latest?base=USD #* CURRENCIES ARE LIMITED # [X-RATES|http://www.x-rates.com/calculator] #* Example: http://www.x-rates.com/calculator/?from=GBP&to=USD&amount=1 #* CURRENCIES ARE LIMITED |
The exchange rate processors that we have/had (Yahoo Finance, Google Finance, etc.) can be unreliable as they may scrape a website for the exchange rate (and the page can change, breaking the scrape), the accuracy may not be accurate, or in the case of Yahoo Finance, the service can be discontinued abruptly without notice.
It would be better to also support a dedicated exchange rate processing service that provides an API and API key for fetching rates. These services can require a paid subscription, so they should be added in addition to the free (but potentially unreliable) ones that currently exist in Blesta. Because of the necessity to support an API key, exchange rate processors should be able to inject a set of fields to save as settings for the processor. Consider the following new exchange rate processors: # [Currency Layer|https://currencylayer.com/product] #* Free version supports up to 1000 API calls per month, updated hourly # [Open Exchange Rates|https://openexchangerates.org/signup] #* Free version supports up to 1000 API calls per month, updated hourly. #* Free version is LIMITED TO USD AS BASE CURRENCY! We may be able to work-around this by converting the rate with respect to the base currency configured in Blesta. # [European Central Bank|http://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html] #* Data is provided via XML on a daily work-day-basis after 4 PM CET #* XML available @ http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml #* CURRENCIES ARE LIMITED # [Fixer.io|http://fixer.io/] #* Example: http://api.fixer.io/latest?base=USD #* CURRENCIES ARE LIMITED # [X-RATES|http://www.x-rates.com/calculator] #* Example: http://www.x-rates.com/calculator/?from=GBP&to=USD&amount=1 #* CURRENCIES ARE LIMITED |
Story Points | 8 |
Rank | Ranked higher |
Remaining Estimate | 0 minutes [ 0 ] | |
Time Spent | 30 minutes [ 1800 ] | |
Worklog Id | 10530 [ 10530 ] |
Time Spent | 30 minutes [ 1800 ] | 48 minutes [ 2880 ] |
Worklog Id | 10532 [ 10532 ] |
Description |
The exchange rate processors that we have/had (Yahoo Finance, Google Finance, etc.) can be unreliable as they may scrape a website for the exchange rate (and the page can change, breaking the scrape), the accuracy may not be accurate, or in the case of Yahoo Finance, the service can be discontinued abruptly without notice.
It would be better to also support a dedicated exchange rate processing service that provides an API and API key for fetching rates. These services can require a paid subscription, so they should be added in addition to the free (but potentially unreliable) ones that currently exist in Blesta. Because of the necessity to support an API key, exchange rate processors should be able to inject a set of fields to save as settings for the processor. Consider the following new exchange rate processors: # [Currency Layer|https://currencylayer.com/product] #* Free version supports up to 1000 API calls per month, updated hourly # [Open Exchange Rates|https://openexchangerates.org/signup] #* Free version supports up to 1000 API calls per month, updated hourly. #* Free version is LIMITED TO USD AS BASE CURRENCY! We may be able to work-around this by converting the rate with respect to the base currency configured in Blesta. # [European Central Bank|http://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html] #* Data is provided via XML on a daily work-day-basis after 4 PM CET #* XML available @ http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml #* CURRENCIES ARE LIMITED # [Fixer.io|http://fixer.io/] #* Example: http://api.fixer.io/latest?base=USD #* CURRENCIES ARE LIMITED # [X-RATES|http://www.x-rates.com/calculator] #* Example: http://www.x-rates.com/calculator/?from=GBP&to=USD&amount=1 #* CURRENCIES ARE LIMITED |
The exchange rate processors that we have/had (Yahoo Finance, Google Finance, etc.) can be unreliable as they may scrape a website for the exchange rate (and the page can change, breaking the scrape), the accuracy may not be accurate, or in the case of Yahoo Finance, the service can be discontinued abruptly without notice.
It would be better to also support a dedicated exchange rate processing service that provides an API and API key for fetching rates. These services can require a paid subscription, so they should be added in addition to the free (but potentially unreliable) ones that currently exist in Blesta. Because of the necessity to support an API key, exchange rate processors should be able to inject a set of fields to save as settings for the processor. Consider the following new exchange rate processors: # [Currency Layer|https://currencylayer.com/product] #* Free version supports up to 1000 API calls per month, updated hourly # [Open Exchange Rates|https://openexchangerates.org/signup] #* Free version supports up to 1000 API calls per month, updated hourly. #* Free version is LIMITED TO USD AS BASE CURRENCY! We may be able to work-around this by converting the rate with respect to the base currency configured in Blesta. # [European Central Bank|http://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html] #* Data is provided via XML on a daily work-day-basis after 4 PM CET #* XML available @ http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml #* CURRENCIES ARE LIMITED # [Fixer.io|http://fixer.io/] ( #* Example: http://api.fixer.io/latest?base=USD #* CURRENCIES ARE LIMITED # [X-RATES|http://www.x-rates.com/calculator] ( #* Example: http://www.x-rates.com/calculator/?from=GBP&to=USD&amount=1 #* CURRENCIES ARE LIMITED |
Sprint | 4.2.0 Sprint 3 [ 48 ] |
Rank | Ranked higher |
Fix Version/s | 4.2.0-b1 [ 11014 ] |
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Time Spent | 48 minutes [ 2880 ] | 1 hour, 48 minutes [ 6480 ] |
Worklog Id | 10552 [ 10552 ] |
Status | In Review [ 5 ] | Closed [ 6 ] |