These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

API to transfer isk

Author
Protoburger
The Scope
Gallente Federation
#1 - 2014-03-08 19:40:34 UTC
Give the API some love !

Transfer isk thru API would be a really nice feature. Transfer Corp isk to members, to do reimbursement, shop, etc...


Need more automation so we can pew more !! Twisted

C'mon python.... Easyyyy ! =P
FireFrenzy
Cynosural Samurai
#2 - 2014-03-08 21:04:42 UTC
Will prolly never happen because the API is "supposed to be" something you can safely hand out to people...

Granted they might add the functionality to full apis or something but i genuinely dont see why this would be required or even desirable.
Hopelesshobo
Hoboland
#3 - 2014-03-10 05:32:57 UTC
Protoburger wrote:
Give the API some love !

Transfer isk thru API would be a really nice feature. Transfer Corp isk to members, to do reimbursement, shop, etc...


Need more automation so we can pew more !! Twisted

C'mon python.... Easyyyy ! =P


Long story short, let me write a program that will let me run the market in all the major trade hubs...

Lowering the average to make you look better since 2012.

Anhenka
Native Freshfood
Minmatar Republic
#4 - 2014-03-10 05:41:27 UTC
FireFrenzy wrote:
Will prolly never happen because the API is "supposed to be" something you can safely hand out to people...

Granted they might add the functionality to full apis or something but i genuinely dont see why this would be required or even desirable.
This.

API's are used to pull information, the most important use is for handing them out to a corp recruiter during the recruitment process. While I'm fine with having a recruiter be able to see all my transactions/mails/contracts/skills/ques/whatever, I absolutely draw the line at them being able to pull money from my wallet.

Also, nearly all third party programs use the API in some way if they are modded by your characters, this would make it easy for a third party app producer to go ahead and steal all their users isk. Trust and use of third party applications would collapse overnight.
Liafcipe9000
Critically Preposterous
#5 - 2014-03-10 07:18:46 UTC
Protoburger wrote:
Give the API some love !

Steal isk thru API would be a really nice feature. Steal Corp isk from members, to do griefing, etc...


Need more automation so we can cry more !! Twisted

C'mon python.... Easyyyy ! =P


FTFY
Seliah
Blades of Liberty
#6 - 2014-03-10 08:22:09 UTC
Anhenka wrote:

API's are used to pull information


This. API should be only a read-only thing. The moment you introduce a way to modify the information you can read through the API, it's no longer safe to hand it out to people.
Protoburger
The Scope
Gallente Federation
#7 - 2014-03-10 22:49:34 UTC  |  Edited by: Protoburger
I should have explained better...

What I meant wasn't Char to Char transfer, but Corp to Char transfer, so Corp management gets better. Nothing about Char to Char transfer thru API, that would be insane indeed.

And well, as there are Director level API stuff, this could/should be one as well... Since its Director level, you already can transfer isks anyways thru the UI, so.


And about market stuff, how can u manipulate the market just transfering isks around ? Even Char to Char isk transfer....


Just an example, what can be done with this:
You can fetch a KB from a member and automatically reimburse the loss to whatever Corp policy you have.

If you're not a manager of a Corp you really won't see this, but if you have to handle reimbursement, you have to deal with all this checking stuff and transferring isks.


But yea, I know its impossible to happen, but who knows.... I really can't imagine how big Corp/Alliances handle this stuff, its probably the most boring task ever... Or they have a tricky way to do it..... Ugh

PS:
Im a developer so I love these stuff, sorry Roll
Reaver Glitterstim
The Scope
Gallente Federation
#8 - 2014-03-10 23:57:04 UTC  |  Edited by: Reaver Glitterstim
FireFrenzy wrote:
Will prolly never happen because the API is "supposed to be" something you can safely hand out to people...
Anhenka wrote:
I absolutely draw the line at them being able to pull money from my wallet.

He didn't say anything about taking money from an API, he said giving money to the API. There IS a difference.

Let's remove the ability to right-click someone in chat and give them ISK. I don't want people to be able to take my ISK from chat!
^ ^ Reavers foolish scumflinging ^ ^


Protoburger wrote:
I should have explained better...
You explained fine, they didn't read your post before flaming it.

FT Diomedes: "Reaver, sometimes I wonder what you are thinking when you sit down to post."

Frostys Virpio: "We have to give it to him that he does put more effort than the vast majority in his idea but damn does it sometime come out of nowhere."

Anhenka
Native Freshfood
Minmatar Republic
#9 - 2014-03-11 01:01:05 UTC  |  Edited by: Anhenka
Reaver Glitterstim wrote:

Protoburger wrote:
I should have explained better...
You explained fine, they didn't read your post before flaming it.


If what he was looking for was some sort of ability to manually transfer isk to some sort of API key, like some sort of wire transfer to a numbered banking account, then that's fine. It would be complicated, since a single account can have many API keys, and an API key can have up to 3 characters, and they can be deleted and remade with ease, but it would not be gamebreaking. Some sort of inter-character wallet on an account has always been something that sounded interesting, wallets tied to an API key could be a part of that.

But if he's looking for some sort of anonymous wire transfer, then you run into the teeny tiny issue of the location to send the money to "the api" having all the characteristics needed to identify the owner of the account.

If he's looking for some way to use an API key to perform automated isk transfers like simultaneously sending op/rent/monthly payouts on a schedule or whatever from one character to a group of other accounts/people, then we start running into risks with API's being used as auth tools. And as people have said, it's very important API cannot be used to have an effect on an account beyond well... spying on everything they do. (Obligitory ~NSA~, ~Tinfoil hat~, ~1984~)

But frankly, he didn't explain much at all in his OP, so we are all just guessing at that point what his intentions were.

Edit: I completely missed the OP's post right before Reavers foolish scumflinging, give me a few to rework this.


Second edit: Ok, to OP's second post, sure, sounds good. Corps can always use more tools to assist in smooth management. The only difficulty I see is the part with a single API being tied to up to three characters at once.

A lot of the automation for things like reimbursement wouldn't be used because the nullsec reimburse guys need to make sure you lost the correct fit before reimbursement, but extra tools are always to work with are always ok.
SemiSonic Bunny
Center for Advanced Studies
Gallente Federation
#10 - 2014-03-22 03:45:27 UTC  |  Edited by: SemiSonic Bunny
+1 for an API to transfer ISK.

I realise that the earlier responses to the poster reflect the way the vast majority of players would view this. So let me explain in a little more detail.

Use Case
I want to create websites that provide EVE related services and accept in-game currency. There's no problem you say, and that's correct as long as the money always flows to me.

What if I want to create a lottery system, all payments in (to me) are fine, but payments out need human intervention. Ok so I have to make the payments out manually, but this means a delay and as soon I go on holiday or similar then I need to trust someone else to make the payments out. That's where I get ripped off.

There are probably other use cases around corp management too.

Proposal:
Create a multi-step process for a corporation to be able to have an API key that allows for the transfer of ISK.

Step 1: A director of the corp would raise a support ticket with CCP requesting that this feature be enabled for the corp. The director would have to provide a reason why they wanted this to be enabled. CCP would consider and any reason such as "my renter alliance requires this of my corp" would be rejected. Only a legitimate corp management or business reason that is in the corp's best interests should be accepted.

Step 2: Upon CCP accepting the request, any other directors of the corp would be notified via eve mail and given an opportunity to countermand the request. For example this might be a 5 day activation delay. (If the corp had no other directors then activation would be immediate)

Step 3: Once the activation stage was completed then the directors would have an additional bitmask that could be selected when generating corp api keys. Each time a key with the Make ISK Payment bitmask set was generated then all the directors would receive a notification eve mail (to prevent an unscrupulous director from having a backdoor to the corp wallet).

Step 4: Use the api key. Profit from simplified management / new business opportunities.
Reaver Glitterstim
The Scope
Gallente Federation
#11 - 2014-03-22 03:58:14 UTC
I think it's best to keep the description simple: it lets people send ISK to a character by selecting from a list that is pulled up with an API tool. That way you don't give them time to fly off the handle with their weird fantasy scenarios before you dispel all of the rumors. Then again, in practice it never works, because for some reason the less text you write, the more determined your readers will be to not read it properly when they reply.

FT Diomedes: "Reaver, sometimes I wonder what you are thinking when you sit down to post."

Frostys Virpio: "We have to give it to him that he does put more effort than the vast majority in his idea but damn does it sometime come out of nowhere."

Flay Nardieu
#12 - 2014-03-22 12:59:05 UTC
Out of client corporate administrative of isk transfers would be handy to have specifically for corporations that pay their members for mining and such. However, as I understand it the current API setup is a read only access. This would have to wait until the next gen API system is complete which is supposed to have limited write abilities. Of course safe guards and limits would be needed to ensure continued trust in 3rd party utilities.

IMHO outside of corp management functions which are clumsy in game at times the need for this feature in honest play is not needed
Reaver Glitterstim
The Scope
Gallente Federation
#13 - 2014-03-22 20:07:25 UTC
Flay Nardieu wrote:
However, as I understand it the current API setup is a read only access. This would have to wait until the next gen API system is complete which is supposed to have limited write abilities.
Why are write abilities needed to read API?

FT Diomedes: "Reaver, sometimes I wonder what you are thinking when you sit down to post."

Frostys Virpio: "We have to give it to him that he does put more effort than the vast majority in his idea but damn does it sometime come out of nowhere."

SemiSonic Bunny
Center for Advanced Studies
Gallente Federation
#14 - 2014-03-22 21:11:57 UTC
Reaver Glitterstim wrote:
Flay Nardieu wrote:
However, as I understand it the current API setup is a read only access. This would have to wait until the next gen API system is complete which is supposed to have limited write abilities.
Why are write abilities needed to read API?


Write abilities aren't needed to READ the API, but to change in game data i.e. transfer ISK, would be a WRITE.