API Limitations

[everly]

Hello,
I have bought Pro subscription to find out that:
1) A few currencies from our sales are not supplied in API. They are: NOK, SAR, AED.
It would be good to supply them in general feed, otherwise I need to use some other APIs for rates and it is very annoying.
2) API has limited historical data, just from Jan 2, 2016. Any troubles adding rates for prior dates?

[everly]

And yet another issue. It seems that rates does not correspond to the ones, used by Steam.
I am comparing Steam monthly report with data provided for each transaction. Data for each transaction has amount in payee's currency and I convert it to USD using rates provided by Steamlytics API. The number of transactions is the same, but gross amount after rates conversion is different for about 10%. This conversion error is very big, given that some payments are already in USD and they are not converted. If USD payments are subtracted, the error in remaining payments is 27% which is very high.

[waylaidwanderer]

Apologies for the late response, I only saw this now.

1) I track currency exchange rates by looking at market sales. If no items are sold on the market in those currencies, it won't be recorded in the Steamlytics database. This may be the cause.

2) I only started tracking this data on that date. If you need data before then, I can't really do anything about it.

3) The rates are extrapolated from market sales. Not sure how often it changes though. Are you using the same rate for every transaction, or are you using that specific day's exchange rate for the transaction?

[everly]

Reply for 3 - I download rates for each date from your API (full history) and then convert each sale from original currency to USD using rate for specific date. I have compared a couple of months with monthly reports.

Additional note: I was trying to use different sources for rates:
* Pure FX rates available in some APIs. They give biggest error.
* We have our own Steam sales. They are not in-game sales, they are DLCs. I have extracted exchange rates from there and used for conversion. Error was still bigger, comparing to using your API.

So, your API gives best results, but error is still huge. It would be so nice of Steam to provide this data in native API. But that seems hopeless dream.