API Suggestions & Improvements
Suggestion type:
Something else
What needs to be done:
I’m not sure if this falls under your purview, but support for IPv6 access to the Torn API.
Why is this needed:
Support for IPv6 in the API would allow developers to reduce costs (with AWS currently charging $3.65 a month for an IPv4 address). IPv6 support would also allow for greater accessibility in regions/ISPs switching to IPv6 and CGNATs (especially given the substandard quality of and the difficulty in using publicly accessible NAT64/DNS64 providers).
Drawbacks:
None that I can think, of although Ched has said that they’ll work on this in the future but I’m not sure if that applies to the API.
Suggestion type:
New feature request
What needs to be done:
Expose the attacklog endpoint to the API. Given the UUID of an attack, return the attackLog detail in a JSON structure.
Why is it needed:
It's not presently possible to perform any significant analysis on historical attacks, not to mention being able to accurately estimate assistance value for assists etc
Drawbacks:
No obvious drawbacks. The attacklog can be viewed by anyone if they have the ID.
~ P
Support my suggestions: Faction API Keys
Would that lead to attack logs not being deleted anymore?
Also, Loot Rangers would probably like that suggestion too, tho we have our workarounds
Hello,
This has now been implemented. Please see this post for more information:
https://www.torn.com/forums.php#/p=threads&f=63&t=16401584&b=0&a=0&start=40&to=24948515
I know I didn't implement everything that you suggested (and what MightyGoober asked in this thread), but I might add additional information to 'user' -> 'crimes' & 'torn' -> 'subcrimes' sections in the future (such as recommended items, the amount of items user has, etc.).
Suggestion type:
New feature request
What needs to be done:
New selection for players to get the current bounties on them.
Why do you need this:
Currently the only way to know if a player has bounties on them is through their icons, but that doesn't show all the bounties on them.
Consider any drawbacks of your suggestion:
No clear drawbacks to me.
Example:
{
"bounties": [
{
"lister_id": integer | null, // Null when anonymous.
"lister_name": string | null, // Null when anonymous. Not necessarily for me, depending on how though it would be.
"reward": integer,
"reason": string | null,
"quantity": integer,
"placed": EpochTimestamp, // Not necessarily for me, depending on how though it would be.
"expires": EpochTimestamp, // Not necessarily for me, depending on how though it would be.
},
]
}
Not sure if that info is available anywhere, but
"expire": integer
could be added
also, you switched up the types in lister_id and _name
Addressed on the post, thanks :D
Switched id and name types and added "expired" and "placed".
Thank you for the new crime API, they are useful to know the user crime uniques obtained instead of scanning all their crime logs.
I can call
https://api.torn.com/v2/torn/?selections=crimes
to obtain
{
"crimes": [
{
"id": 1,
"name": "Search for Cash",
"category_id": 2,
"category_name": "Theft",
"enhancer_id": 564,
"enhancer_name": "Glasses",
"unique_outcomes_count": 34,
"unique_outcomes_ids": [
786,
Right now I don't see a way to obtain information about that 786.
Skeletron provided me a file made manually by scanning the crime logs of many players that contains the meaning of that 786:
"786": {
"target": "Trash",
"imageIDs": [
66
],
"name": "Morphine x10",
"skill": 25
},
My request is to get a way to obtain, by using Torn API 2.0, information about "unique_outcomes_id = 786", in particular the list of image IDs, the minimum crime skill level needed to obtain that unique outcome, the requirements (i.e. Cameras disabled)
Suggestion type:
New feature request
What needs to be done:
New selection for player rank in city jobs.
https://api.torn.com/user/?key={KEY}&selections=jobranks
Why do you need this:
A player can leave a city job and return to the same rank, but this information is not displayed anywhere
Consider any drawbacks of your suggestion:
No clear drawbacks to me.
Example:
![tiksan [2383326]](/images/honors/1118/h.png)
![pobk [3171827]](/images/honors/129/h.png)
![Hemicopter [2780600]](/images/honors/1104/h.png)
![splent [2088243]](/images/honors/843/h.png)
![DeKleineKobini [2114440]](/images/honors/700/h.png)
![Wolverine [1971836]](/images/honors/690/h.png)
![DieselBlade [1701621]](/images/honors/481/h.png)
{
"jobranks": {
"medical": 1,
"education": 6,
"law": 0,
"grocer": 3
}
}
Suggestion type:
- New feature request
What needs to be done:
- add API to get Auction House Data
- this could potentially go under https://api.torn.com/torn/?selections=AuctionHouse and take the Item ID(s) as parameter(s), to filter, or provide all of ite
Why do you need this:
To allow for easier integration into discord. I would like the ability for users to track, and obtain pings for auctions nearing its end so they can decide whether or not to bid on it.
I'm also sure bzimor may thank us for this endpoint as well to stop him trawling through Auctions.
Consider any drawbacks of your suggestion:
- None that I'm aware of
Example:
{
"AuctionHouse": [
{
"AuctionID": number,
"results": [
{
"TornWeaponID": number,
"Accuracy": number,
"Damage": number,
"Armor": number,
"Quality": number,
"Bonus1": string,
"Bonus2": number,
"owner_id": number,
"high_bidder_id": number,
"price": number,
"endTime": time/string,
},
},
]
}
Edit--- Apologies, I just noticed it on the miro board. That being said, it's not a terrible change to add. A lot of people use bzimor frequently and this will only aid in its use.
This would be awesome for bazaar and item market listings as well. Giving us the Item ID for unique items like weapons and armour would allow to stats to be retrieved much easier
https://www.torn.com/forums.php#/p=threads&f=63&t=16399202&b=0&a=0
This is from a while ago but haven't been doing much dev work so I didnt see this thread. Would love if you could take a look at this request for adding turn by turn attack logs to the API
To extend this: an API for normal armory logs would be useful. Same as attacks and revives etc.
Also include if the item was donated, loaned, consumed, given or filled
Suggestion type:
- New feature request
What needs to be done:
Add users bookie bet data to user section.
Why do you need this:
Allows players who use the bookie a lot to analyse their betting patterns, winning areas, etc
Consider any drawbacks of your suggestion:
Limited set of users would have interest in this data
Example:
(Finally, provide an example of the API change)..
no idea on the data stored and I’m on mobile.. so.. meh
{
"Bets": [
{
"Bet_id",
"Bet_category_id",
bet type
bet value
Wager,
outcome,
etc..
},
...
]
}
Ranked war auction service:-
Just 5m per day per listing
Chat for details
Hi Splent,
in our personal stats we see energy drinks, refills, alcohol, any different drug taken, but we don't see FHCs because they are included in the generic "boosters" category together with other stuff like lawyer business cards and erotic dvds.
Do you think that FHCs could have their own section in personal stats?
And if they are stored separately in the database (or they simply increase a booster counter in the database, in that case it would be impossible even for a developer to know how many fhcs a player used).
Sounds like what you want is boosters to be divided into "energy", "nerve", and "other" categories.
no, I would like to FHC in "personal stas > Items" tab.
We have Easter eggs found, Easter eggs used and Stat enhancers who are all boosters but have their own section, but we don't see FHC: why?
Suggestion type:
New feature request / Minor Improvement
What needs to be done:
Add new information in faction API section to indicate the faction is enlisted.
This should only be available for the own faction via the AA permision.
Why do you need this:
The information is currently only available in the faction mainnews. Instead of pulling these regularly to check the news text, a simple flag could reduce the load on the API.
Use case: We have an information dashboard to inform our members of the RW status, starting with the enlistment.
Consider any drawbacks of your suggestion:
No clear drawbacks to me.
Suggestion type:
- Minor improvement
- Optimization / Performance
What needs to be done:
- Add attacker level and defender level to faction > attacks endpoint
Why do you need this:
- Currently the attack log object has the attacker and defender: name, id, faction id, and faction name. If you want to also get their level, you currently need to make two additional API calls to the user > basic endpoint, one for each participant, just to get their level.
Consider any drawbacks of your suggestion:
- No real drawbacks, this is information that is already available in another endpoint, this suggestion just reduces the needed API calls by 66%, from 3 to 1. Torn will likely save a little money.
Example:
![Brizo [2715469]](/images/honors/1166/h.png)
![KingLouisCLXXII [2070312]](/images/honors/786/h.png)
![L4suicide [15699]](/images/honors/42/h.png)
![JKyte [2417425]](/images/honors/210/h.png)
![byrod [1132772]](/images/honors/309/h.png)
![Bardicer [553834]](/images/honors/1031/h.png)
"attacks": {
"123": {
"code": "a6032a48e3874f06ed004701511f5327",
"timestamp_started": 1725714474,
"timestamp_ended": 1725714475,
"attacker_id": 3269692,
"attacker_name": "Test1",
"attacker_faction": 36691,
"attacker_level": 100,
"attacker_factionname": "Rabid Chihuahuas",
"defender_id": 1785484,
"defender_name": "Test2",
"defender_faction": 16628,
"defender_factionname": "Chain Reaction",
"defender_level": 46,
"result": "Lost",
"stealthed": 0,
"respect": 0,
"chain": 0,
"raid": 0,
"ranked_war": 0,
"respect_gain": 0,
"respect_loss": 0,
"modifiers": {
"fair_fight": 1,
"war": 1,
"retaliation": 1,
"group_attack": 1,
"overseas": 1,
"chain_bonus": 1,
},
}
}
Don't think level is very relevant when it comes to attack info (when level holders are a thing), unless you are making a leveling list. Also not sure how many people pull that data alongside attack info. Sounds pretty specific for your use case and creates a bad precedence (what if i need their max hp or age?).
![Omanpx [1906686]](/images/honors/131/h.png)