Public Wallet Information

Hey guys I’m trying to make my Wallet balance and journal publicly posted, viewable on a website or spreadsheet. I’ve tried GESI with google sheets and this is pretty close to what I’m looking for but it doesn’t update as frequently as I’d need it to, or I don’t know how to get it to update as frequently as I’d need it to. Basically I would need for people to be able to send a character isk, and then get confirmation that it was sent on the spreadsheet/website within a minute or two. Is this possible, and what would I need to do this?

Thanks!

https://esi.evetech.net/ui/#/

You would probably have to create a refresh button so it can be refreshed. Like on evanova. The wallet and journal of corp or char has a refresh button.

Then, there used to be several different sites corps would use that they would include the wallet scope, so when a potential new corpmate signed in, the corp could see their wallet.

Youll have to build on the eve online sso so you can sign in. As far as sending isk, youll have to set that in game as a bill payment. But i dont think you can send isk outside the game.

If you explained what youre wanting to accomplish someone may be able to help you further

I know when someone pays our corp for our services, i can refresh it 2 minutes after its sent and see it, on evanova

Thanks for the response Geo. Yeah what I am looking for is basically in that ESI link, the get request that is:

/characters/{character_id}/wallet/journal/

I need the output of this, ran on my character (halfdone12) printed to anywhere public that somebody can easily refresh it/re-run the command to pull the most up to date wallet journal on me.

I’m pretty sure GESI allow you to update as soon as there is new data in ESI (but, It’s possible I’m wrong). The endpoint have a cache time of 120 seconds, which means new data is only available after waiting 120 seconds since the last request (that didn’t hit the cache), if you try to update before that, you will get a cached result AKA hit the cache - hitting the cache is generally consider bad, as it’s wasting eve resources, so most thing will limit users so they can only update when there is new data in ESI.

If you’re looking to code your own solution, I would suggest looking at the libraries at eve awesome. so you don’t have to reinvent the wheel - writing a OAuth implementation for EveSSO, is fun, but will take time and if you don’t know what you’re doing, it could be a potential security risk: