Can second that, it's annoying when the key owner goes guesting or inactive and you forget about some tool that was using their key, only realizing once something stops working :(

I had exactly this issue with a module in my bot that reports faction vault transactions in discord. User leaves and joins another faction, we were seeing EVERYTHING that the faction did, especially with larger armounts. 

I think it's a good idea, but it's not entirely up to me.

The question is how would these keys be managed, but I'm guessing it would be a new section here (either in "Control" or "Faction Modification"), called "API Keys"?


And I'm guessing these keys would only have access to non-public faction selections?

Great idea, I also had this issue where key owners have gone guesting and it broke stuff I made.

Putting it in the Control section seems appropriate. Maybe the Faction API perms can also be reworked to instead give access to that section and allow the users to control the API key(s) for the faction instead.

Only issue I could think of is that presumably each faction will be limited to the usual 100 calls per minute (just like a single user would), whereas currently multiple users could contribute to a pool of API keys for members of the faction so it would be possible currently to make more than 100 calls per faction. If this was changed to being per faction rather than per user this would not be possible anymore. But not sure if anyone really would need that many calls specific to the faction.

Maybe as a compromise, given that there aren't as many factions as there are users and given the limitation that a faction API key would only be able to poll faction data, the limit could be increased to 500 or 1000?

This seems like a great idea.  As to the limit, you could make it slightly higher than 100, or maybe even allow factions a handful (5?) of individual keys, each capped at 100, so if necessary, they could be allocated to different apps and one hitting the limit wouldn't break the others - or pooled for a single app like current faction member keys are.

Honestly it would be nice to be able to register our applications with Torn for public access. And then for faction specific things have keys like is being suggested here. It would be nice to be able to pull certain public data without it even being tied to one specific persons key. Maybe with it's own usage tracking. So that it isn't tied to your own accounts 100 calls per minute. 

I hate having to ask for peoples keys to pool just to do public API level things. 

Hold on a second now... You don't want to be talking about things like OAUTH2 round here... Someone might blow an aneurism or something.

Honestly, I have no idea how to even begin to describe how it might work, where it might go or what the logistics would be.

A faction key though, would only have access to the private faction data if that's the role of the key?

+1 here. Lots of boilerplate just to check if the users key is valid, then if the user is in the faction and if the user has faction api permissions and to accurately handle error responses

Should I open this up as a suggestion somewhere else so that we can get some more traction on this and perhaps, some more eyes... Or have you been pointing Ched in the direction of this forum and your suggestions thread?

The general consensus so far is that this would be a Good Thing[tm].

We did talk about it a little bit. The biggest concern is if this is worth the development time as substantial modifications to the existing system are needed (both FE and BE), and the question is how many would benefit from this.

I think it might be a good idea to create a thread in the suggestions forum and see how much traction this gets.

I know this is probably not the answer you were looking for, but hopefully it helps a little. 

I think this is a good idea too, I think it would be important that these keys have properties like:

- Can access public data about the faction the key belongs to (eg faction basic) would work for no ID input or the ID of Faction that owns the key.

- Less cached data - It would be nice for things like the revives or attacks selections to be cached less often (ie less than 30 seconds)

- Lower API request limit per minute - To make up for the shorter cache the number of requests per minute could be less, such 25 or 50.

As someone who only allows for 1 Faction Key to be linked at a time in my bots, I think this would be a huge benefit to all those factions with rotational leaders, meaning they do not need to constantly swap the keys in the bot config to keep it working if they move faction or leadership position.

Have created a thread here:

https://www.torn.com/forums.php#/p=threads&f=4&t=16429732&b=0&a=0

I don't think a lower limit per minute would be good unless that is tied specifically to a faction API limit that is separate from a player limit. I know sometimes just during a chain or event when attacking a lot, you can blow through that limit rather quickly just from regular browser extension style tools. 

I would really love to see the cache on attacks/revives dropped. While running a revive service, a double revive is very common as a person can request a revive, get revived, get killed, and then get revived again because a system is unable to tell they already just received a revive. 

Yes that is what I meant. The lesser limit would only be for the faction key.