Your Torn API keys

The bot uses a server key, which an admin provides during setup, and a personal key from each member who uses a feature that acts on their behalf.

The server key

The server key covers everything that concerns the faction as a whole: finding the faction, reading its members and chains, and checking which Discord accounts are linked to which Torn players.

It needs Limited Access. The wizard’s Create a Limited key button opens Torn with that key ready to confirm, or you can make it in Torn’s settings, under Preferences, then API. The bot takes only Limited keys: a Custom key, whose reach differs from key to key, or a Full key, which reads far more than the bot needs, is refused. These are the parts of Torn it reads:

Needed by	Torn API section	Selections
Core	key	info
Core	user	basic, discord
Core	faction	basic
Chain	faction	chain, chains, chainreport, members

A member’s own key

Some actions are done on behalf of one member, such as joining a chain or asking for a target to save a chain. For those the bot asks the member for their own key once and keeps it until they remove it. A member has one key, shared by every server running the bot.

Needed by	Torn API section	Selections
Core	key	info
Core	user	basic
Stat tracker	user	bars, battlestats, gym, perks

A member’s key must also be a Limited Access key, and the Create a key button on the key prompt makes one in a click. The bot only accepts a key that belongs to the Torn account the member verified with, so nobody can store someone else’s key.

/key shows the member whose key it is, whether it still works and since when, but never the key itself. From there they can replace or remove it.

Stat tracker and TornStats

/progress reads your battle stat history from TornStats, using your own key. You need a TornStats account for that key: sign up there with the key you gave the bot. The first time you open /progress, the bot checks for one by sending your key to TornStats, which stores it on your account there if you already have one. It does this once. /gains doesn’t need TornStats.

Save chain and FFScouter

Save chain suggests a target the member can hit right now, using targets from FFScouter. FFScouter requires each person to use their own key and agree to its data policy. The bot shows the policy once and registers the key with FFScouter only if the member agrees. A member who says no can still join chains, without suggested targets.

How keys are stored

Stored	Encrypted in the bot’s database, for as long as the server uses the bot or the member keeps the key stored.
Shared with	Torn’s own API. A member’s key also goes to FFScouter if they agreed to Save chain, and to TornStats if they use /progress. Nobody else.
Used for	Verification, chain tools, lottos and the stat tracker.

Taking access back

Tip

Delete or regenerate a key in Torn’s settings (Preferences, then API) and the bot loses access immediately. Torn also keeps an access log for each key, so you can see every call made with it.

• Server key: an admin can replace it in the wizard’s API key step. If you remove the bot, it stops using the key, but the server’s settings, including the encrypted key, are kept so that adding the bot back is easy. To have them deleted, ask the developer (see Privacy).
• Member key: a member replaces or removes theirs with /key.