Torn API keys & factions
The bot reads your faction's chain status, recent attacks and member list through a Torn API key. Keys are submitted on the website, encrypted, and never shown again.
Submitting a key
A server manager submits keys on /guild/{server id}/torn-key.
The faction is determined by the key itself, submitting a key for a faction
that isn't known on the server yet creates it. One key per Torn account per
server: submitting a new key from the same account replaces the old one.
Multiple keys, multiple factions
A faction can have several keys, up to 25, from different accounts. The bot rotates between them, which spreads out Torn's per-account call limit and keeps things running if one account has a problem. A server can host up to 10 factions, each running its own, separate chain.
Which access level to choose
Torn has four key levels: Public Only, Minimal Access, Limited Access and Full Access (plus custom keys). Chaining Tatum rejects Full Access keys. For your safety it only accepts keys with less access, and a rejected key is never stored. Create a new key under Torn Settings → API Key with Limited Access (or lower), or use the custom key from the “Create the key on Torn” button on the key pages. This applies to every way of handing in a key: server keys, member keys and the key for mercenary or revive work. If the bot cannot read the access level of a key right now (for example Torn is not answering), the key is rejected too, with a hint to try again in a minute. Keys that were stored before this rule stay until the operator or you remove them.
What a key needs
For the queue and rotation itself, a basic key is enough. For precise hit detection during a chain watch or any mercenary work, the account behind the key needs the Torn position permission Faction API Access. Without it, chain watch falls back to a less precise counting mode (see Chain watch), and mercenary work refuses to start at all, there is no fallback for it.
Member keys
Anyone on the server, not just managers, can submit their own key without
handing it to anyone: through the Discord command /keys (which
links to the right page) or directly at
/guild/{server id}/my-key. This needs a Discord login but no
manager rights, and only works for a faction the server already knows about.
Managers and the owner never see the raw key of a member, only that it
exists, which Torn account and faction it belongs to, and the date; they can
remove it, and the member can remove it themselves too. Only manager-
submitted keys count toward matching an incoming Xanax payment to your
server, a member key does not.
See also: Chain watch, Mercenary work, FAQ / troubleshooting