Using the quicklook API? Please switch to ESI or CREST if possible

[Yann Ramin]

Hi!

Are you currently using the quicklook API (the one that returns all the market orders) on api.eve-central.com? 

If so, CCP has official support for market orders (and has for quite some time), and this particular APIs is pretty heavyweight on EVE-Central's bandwidth usage. I would like to sunset the quicklook API (and only the quicklook API call, I'm expanding the marketstat API) by end of January 2017, there are better alternatives for up to date market orders from CCP directly.  The bulk of calls to this endpoint come from Python and Go applications, which can easily switch to either market interface (i.e., https://github.com/evecentral/esiapi )

If you can't use either CREST or ESI market endpoints, please let me know so I can possibly make alternative arrangements to keep your systems working.

[Eve Market Noob]

I had been using QuickLook.  How would I do this in CREST or ESI?  I'm so lost.

https://api.eve-central.com/api/quicklook?typeid=9941&regionlimit=10000002

[Clifton Wood]

Hi,

I do understand your wishes, but would hope that you might see that you provide a valid service and alternative to that which is being supplied by CCP.

One of the largest barriers to entry for the use of CREST or ESI is JSON. Many of the Google Sheets that use your API would be unable to retrieve data from these services because I am unaware of any ability to take JSON data and link it to a Google Sheet. If someone knows of a way to do this, I would be glad to hear it.

Another large inconvenience is CCPs insistence to not give us usable multi-region data. Looking at both CREST and ESI, I would have to make several requests (and custom code) to get the data I need, where your resource provides one complete resource.

In the end, if things are becoming hard for you to maintain, I understand the need to cut back. However if there is something I can offer you (assistance? code donations?) to keep things going, please let me know.

- X