Now no other profile than the own one by the ticker who requested it can be retrieved. This makes the whole API useless… Not sure why to have an API like this
Monthly Archives: September 2013
And the Empire Avenue API is broken again. The profile info request used to allow a list of 100 tickers and would respond with the 100 responses in one call. However, apparently since today, there is no list anymore, just one ticker. With this it would take 720 hours to retrieve the info for each ticker available on Empire Avenue. So, it does not make sense to write any application using the API anymore. Why bother anymore with Empire Avenue… Empire Avenue is dead!
This is one of the most annoying deficiencies in the Empire Avenue API. The Oauth authentication does not provide automatically an UID which makes it inconsistent with any other OAUTH2.0 provider.
Furthermore, since the ticker can be changed, there is no way to track ticker changes. Hence after a ticker change, for the purpose of the API, one ticker got deleted, and another one just arrived out of thin air
The results from the API are not typed correcty. Lots of cases numbers are presented as strings, which in turn messes up calculation if no explicit type casting is done.
One of the biggest issue with the EAv API is that there is no bulk buying. Profiles can be retrieved up to 100 tickers in one call. However, each buy needs its own call plus another to retrieve the current trade price.
It would be ok to make the trade price optional, so if people want to buy for a particular price and otherwise want to let the purchase fail, however, it should not be mandatory since most people probably do not care if it is a fraction of an eave higher or lower.