Skip to content
TORNLIFE More

API Key Pausing / Unpausing / Renaming

Started by Stig [2648238] on in Bugs & Issues.

25 replies · 420 views · thread synced · 6 days ago · View on torn.com
About this thread

Posts archived: 26 / 26 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
26
Discussion span
→
Authority score
59 / 100
Historical score
40 / 100
Story score
52 / 100
Engagement score
69 / 100

People posting, likes and official posts are not counted for this thread yet: on threads longer than one page they come from a periodic pass over the archive, which has not covered it.

Most-liked replies

Mentioned in this thread

Stig [2648238] ×1

Stig [2648238]
Hi, I put together a proof of concept for an idea that a lot of people might find quite useful.

Use Case:

You are using certain scripts or websites, such as TornStats, TornTools, YATA, BSP, some of these can use between 5 - 10 API Requsts per minute each.

You may not be actively using one or more of these tools, however they can and will continue to use your API Key, unless you either A, delete the key or B go through each site and manually remove your Key. For some sites this may not even be possible.

Pausing the API key would allow the Player to control who can access their account data using their key(s) and when. For example, BSP has been using my API Key to pull random players, however I do not even have the BSP script installed on my current browser, nor have Torn open on any browsers with it installed! So I would like to have the option to pause this API Key temporarily, then once I am using it or need it again I can re-enable it without the need to generate a new key and add it to the script.

Edit: It would also be extremely useful to be able to rename API keys without the need for removal and recreation.

[image: cdn.no1irishstig.co.uk]

Heres how that could look, a simple Pause and Unpause button with some CSS to show that one is currently paused (grayed out)
GenShinigami [2664617] Reporter
+1 to anything that gives users more granular control and influence over their own API keys. Definitely would love to see this.
DeKleineKobini [2114440] Committee Committee
While I don't think it's a bad idea, this is simply not the place for such suggestions. They don't get picked up here. You'll either need to paste in suggestions, or potentially in B&I directly as it's API related. You could also ask CloudJumper if you can post this there, or if this should be moved to suggestions and get 250R+.