apilayer
Bug in currency service
I actually tried to open a support ticket about this right now, but I get an error saying the support ticket cannot be opened? So figured I would post it here:
Your currency service broke this morning and suddenly started returning a non 1.0 value for USD -> USD. Actually I think until now it never returned that in the response but today it started returning a non parity number of 1.000268. Now I know inflation is a bit nuts, but that is crazy :)
We had a bug on our end in that we were requesting rates against itself so it messed some stuff up on our end, so I will fix that. But you may wan to fix the service on your end.
{
success: true,
terms: "https://currencylayer.com/terms",
privacy: "https://currencylayer.com/privacy",
timestamp: 1657814824,
source: "USD",
quotes: {
USDUSD: 1.000268,
USDEUR: 0.996755,
USDGBP: 0.84608,
USDCAD: 1.31048,
USDPLN: 4.79665
}
}
I had the same problem as well. (both, not being able to leave a ticket and the 1.000268). I sent a message to apilayers.com, which might be their parent company. No response from them yet. I'll comment back here if I get any information.
@mike-robinson @kendallb My company is having the same problem and I'm wondering if the optimal solution is to hard code the value of USD to 1, but that brings into question the conversion equation being based on USD at the rate being sent.
Was wondering, have you found a solution to the issue yet?
The solution we took was to simply never ask for USD->USD again, and just leave it set to 1:1 in our currency tables.
That is exactly what I did at first. Then I decided, due to the poor technical support from currencyApi, to look at other apis and found RapidApi currency converter. https://rapidapi.com/natkapral/api/currency-converter5/
The first run last night was without any problems. Also saves me $15/month
On Wed, Jul 20, 2022 at 9:29 AM Kyle Medbery @.***> wrote:
@mike-robinson https://github.com/mike-robinson @kendallb https://github.com/kendallb My company is having the same problem and I'm wondering if the optimal solution is to hard code the value of USD to 1, but that brings into question the conversion equation being based on USD at the rate being sent.
Was wondering, have you found a solution to the issue yet?
— Reply to this email directly, view it on GitHub https://github.com/apilayer/currencylayer-API/issues/14#issuecomment-1190498143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPCHLDQHYJ4CP3UJPEL7B3VVASO7ANCNFSM53SZI4YQ . You are receiving this because you were mentioned.Message ID: @.***>