Some ideas for API 2.0
49 views
Skip to first unread message
kevinu
Mar 19, 2012, 2:35:17 PM3/19/12
to empireave-ap...@googlegroups.com
Here are a few suggestions to improve API 2.0.
1. Do away with the paging technique in the portfolio/get (and all the other get methods too). Or at least provide the option to return the entire list in a single API call. This will go a long way to help people with large portfolio lists by avoiding burning 10's of API calls just to get a list. This would be a HUGE improvement.
2. Do away with the last_trade parameter in the shares/buy or shares/sell methods.
3. In every API call to get a list or profile, return the number of shares you are allowed to own in the person. And if the number of shares you each own in each other isn't already there, add that too.
4. Of course I have already mentioned this 100's of times before, provide a way to SEND SHOUTS!!!
5. Keep the API limit per hour HIGH! OMG I would just love if it was 500/hr or higher!!!! I'd even pay for an EAV upgrade to increase the API limit for my account. Not too much though :)
As a last note, I wish the API would consider this for the data returned by EVERY API call: How many shares do I own in the person, how may do they own in me, how many am I allowed to buy, what is the commission rate. Some of these details are in API 1.0 already, but it is incomplete.
Regards,
Kevin
nixkuroi
Mar 19, 2012, 4:18:35 PM3/19/12
to empireave-ap...@googlegroups.com
I don't mind the last_trade requirement. It ensures that your information is current. It sucks to have to "pay" for a call to get the information though.
Kevin Umbach
Mar 20, 2012, 3:06:38 PM3/20/12
to empireave-ap...@googlegroups.com
It could be useful. Would be nice to have the option to buy no matter
what the price :) Or, don't charge an API call if the transaction
fails.
what the price :) Or, don't charge an API call if the transaction
fails.
david sanger
Mar 20, 2012, 5:50:08 PM3/20/12
to Empire Avenue API Discussion
Including a GET command for the Network Scores ( EA, Twitter, Facebook
etc.) would be really helpful in providing a way to giver users
enhanced intelligence on shares
etc.) would be really helpful in providing a way to giver users
enhanced intelligence on shares
Kevin Umbach
Mar 20, 2012, 7:13:07 PM3/20/12
to empireave-ap...@googlegroups.com
And a SEARCH method with lots of criteria to help find people.
Xav.
Mar 25, 2012, 10:33:20 AM3/25/12
to empireave-ap...@googlegroups.com
That's the wish-list for Christmas ? ;-)
Everything will be released for April 1st
nixkuroi
Mar 27, 2012, 12:56:38 AM3/27/12
to empireave-ap...@googlegroups.com
Kyberten, do you work for Eave, or is that an April Fools joke? :)
Xav.
Mar 27, 2012, 8:15:44 AM3/27/12
to empireave-ap...@googlegroups.com
The second option ;-) Don't forget that old EmpireAvenue saying : "
All things come to those who wait. And API 2.0 will be released ,
when pigs fly ! " ::smile::
2012/3/27 nixkuroi <nixk...@gmail.com>
txwikinger
Aug 19, 2012, 2:24:00 PM8/19/12
to empireave-ap...@googlegroups.com
I thought they are busy with their gaming thing now.. Seems Empire Avenue development is dead
kevinu
Aug 19, 2012, 2:43:01 PM8/19/12
to empireave-ap...@googlegroups.com
I agree on that.
Tellez
Aug 23, 2012, 1:58:24 PM8/23/12
to empireave-ap...@googlegroups.com
How about we get together and put together an API. Many of the results are retrieved via POST/GET ajax calls. We might be able to get some of the features we've wanted., although I think it might be against the TOS...
Thoughts? Anyone up for collaboration?
Reply all
Reply to author
Forward
0 new messages