splent: forum

Given the increasing importance of nerve within the new crimes system, it would be great if we could have an item that completely refills our nerve bars (or at least natural nerve bars).

We could have a new booster item : 

The Massage Center Coupon is a Booster Item.

A coupon to fully relax your nerves the fastest way possible with Leslie's help in the Happy Endings Oasis.

Effect: Refills nerve. Increases happiness by 500 and booster cooldown by 6 hours.

--------

Some background : 

At the moment, we have 2 nerve related stocks :
- [CBD] Herbal Releaf Co. - 50 nerve
- [ASS] Alcoholics Synonymous - 1x Six-Pack of Alcohol

But, we have 3 energy related stocks :
- [MCS] Mc Smoogle Corp - 100 energy
- [MUN] Munster Beverage Corp. - 1x Six-Pack of Energy Drink
- [FHG] Feathery Hotels Group - 1x Feathery Hotel Coupon

There could be another stock which provides this new item or it the item could be added as a reward to the FHG stock alongside FHC's? 

Adding a new stock also makes the Monopoly merit harder to obtain.

--------

Potential downside is that this change could decrease the price and amount of sales of alcoholic beverages.

That said - we don't have any nerve boosters! :D 

Hello everyone,

Some of you may know me already, but for those who don’t, let me briefly introduce myself.

I’m Mauro, senior backend engineer and a long-term Torn player (I’ve been playing this game for more than 10 years). I’m excited to announce that I will be working on and managing Torn’s API from this point onwards.

I look forward to working closely with everyone here to make Torn’s API more robust, standardized and better documented.

In the upcoming months, plan is to…
      *  Freeze v1 completely (except for any critical issues, exploits or if serious optimizations are needed)
      *  Work on v2 and refactor some of the codebase
      *  Standardize v2 to follow up the same standard on naming conventions, types, etc.
      *  Fix various bugs
      *  Introduce OpenAPI specification (now available here: https://www.torn.com/swagger/index.html#/) 
      *  Introduce API v2 playaground (now available here: https://api-playground.torn.com/)

      *  Enhance existing features
      *  Add new features
      *  Optimize some of the more heavy requests
      *  Publicly release v2 once it is in a meaningful state

If you have any suggestions, improvements, criticism or any (constructive) feedback at all - I’m more than happy to hear it!

Also, If you suspect any kind of abuse or think any part of the API might be abused, don’t hesitate to let me know.

Please note that once v2 is released, it will be still be unstable and there will be breaking changes from time to time. I will try to communicate such changes upfront, but I can’t promise anything at this moment.

Thank you,

Mauro

--

Recent API changes summarized can be found on API docs page: https://www.torn.com/api.html 

Hello everyone,

I'm excited to announce the launch of our public board for the upcoming API v2 changes!
You can access the board here: API v2 Changes Board

At any time you will be able to see which parts of the API v2 are in progress or completed. You will also see what is the priority for each section.

Currently, new sections and very much needed improvements have the highest priorities, followed by various bug fixes and then just general v2 refactoring.

On all sections I'm looking to make bug fixes and add various small enhancements where needed (such as adding attacker/defender level to 'user'->'attacks' & 'faction'->'attacks' sections).

Here are the key takeaways ~

User API

   *  add  search  section which allows searching players by their username

   *  replace  crimes  section to return statistics for a specific crimes 2.0 crime (including information about uniques)

   *  fully restore  inventory  section after the system migration is complete

   *  add  forumUpdates  section which returns a list of forum updates for the user (new posts in subscribed threads, likes/dislikes, replies etc.)

   *  add  races  section which returns a list of the the user's completed races

   *  add  enlistedCars  section which returns the list of the user's enlisted cars and their upgrades

   *  add  contacts  section (friends/enemies/blocked users), to the Full Access category

   *  add  pointsBuilding  section to show a list of unlocked sections & costs (e.g. merit reset cost)

   *  add  calendar  section which returns currently set event start time

   *  add  competition  section which returns the competition status for users

   *  add  itemMarket  section which returns a list of the user's item market listings (to complement 'User' -> 'Baazar' section, likely to be done after item market 2.0)

   *  add  auctionHouse  section which returns a list of the user's auction house listings

   *  add  propertyMarket  section which returns a list of the user's property market & property loan market listings

Faction API

   *  add search  section  which allows searching factions by their name

   *  add  hof  section for factions

   *  add player revivable status to 'Faction' -> 'Basic' section for members of your faction (if you're a leader/co-leader or have sufficient API privileges)

Company API

   *  add  search  section which allows searching companies by their name

   *  add value to 'company' -> 'employees' section for owner who have a secretary in their company

Market API

   *  possibly add item uid and item stats to bazaar / itemMarket sections

   *  add  auctionHouse  section to return a list of items based on the item id/category/bonus

   *  add  property  &  propertyLoan  sections

Torn API

   *  add  calendar  section to return a list of all events & competitions for the running year

   *  add  hof  section to return a list of 100 members per category (one category at the time)

   *  add  crimesList  section which returns a list of crimes (so you know which sections to pull in 'user' -> 'crimes' section)

   *  remove  organizedCrimes  section because it will no longer be necessary once OC 2.0 are released

Property API

   *  no major changes

Racing API (new)

   *  new section  racesCurrent  which returns a list of custom non-started races

   *  new section  races  which returns a list of finished races

   *  new section  race  which returns details of a race (participants, result, etc.)

   *  new section  records  which returns current records for each track and each car class

   *  new section  hof  which returns a racing hall of fame

Forum API (new)

   *  new section  categories  which returns a list of possible categories (e.g. General Discussion, Non-related, etc.)

   *  new section  threads  which returns a list of threads ordered by the latest post

   *  new section  thread  which returns posts with information about the poster

   *  new section  search  which allows searching posts for specific keywords or by a specific player etc.

General API improvements

   *  add the amount of the remaining API calls to every response

   *  add new dedicated section which returns a list of active users in the last 24 hours (updated once a day)

   *  fields across all endpoints will be revisited & renamed/restructured to follow a more standardized REST API naming convention

--

There are some improvements that we can't add just yet, but I'll be glad to have them revisited once the majority of the work on this public board is complete.

I would also like to thank everyone for writing down the suggestions (major or minor). It really helped to see what the community needs and why, so please keep sharing your feedback!

Thank you,

Mauro

YouTube video mYU4XhCJT7I

Hey, 

Thanks for the report. 

That's fixed now!

Hey,

I think there was a bit misunderstanding and the patch notes should've said it only concerns the items which you have taken with yourself abroad (if I remember correctly, one player was wearing faction clothing item, bought another clothing item which unequipped that faction item and then retrieved it, which shouldn't have been possible).
This bug fix is more relevant for the upcoming Phase 3 of traveling updates.

For normal items which are not taken overseas, retrieving should work as it normally does. 

Thanks! 

Hey,

That should be fixed now. 

Thanks for the report!

Hey everyone, 

A few smaller changes were done to the API in the last few days (including today):

• [API-v2] Added 'participants_left' in 'torn' -> 'elimination' 
• [API-v2] Added 'attacking_summary' in 'torn' -> 'elimination' - this contains all outgoing attacks against all other teams made in the last completed minute. E.g. if it the current time is 15:34:22, this will show show all attacks made between 15:33:00 and 15:33:59.
• [API-v2] Added missing 'description' field to Swagger in 'user' -> 'trades'
• [API] Fixed leaking HTML in user messages for elimination mass mails 
• [Playground] Added auto-refresh to 'user' -> 'key' to prevent stale permissions
• [API-v2] Added missing root field 'competition' in 'user' -> 'competition' for Elimination competition
• [API] Fixed elimination team leak on 'user' -> 'profile' in both API v1 & API v2 for future competitions
• [API] Fixed API caching bug allowing access to higher tier information with lower tier keys (e.g. accessing cached 'user' -> 'log'cached  responses with custom keys which only have limited selection of categories
• [API-v2] Fixed various Swagger issues
• [API-v2] Enabled elimination endpoints - more details here: https://www.torn.com/forums.php#/p=threads&f=19&t=16599245&b=0&a=0&to=27858024 

Deprecation warning reminders!

The 'user' -> 'attacks' & 'faction' -> 'attacks' selections will be returning null instead of 0 value for 'chain' field, starting January 1st, 2027. The Swagger schema was updated to allow for 'null' values already.

[API-v2] The 'faction' -> 'warfare' is now deprecated. It is replaced by other warfare selections and will be removed on 1st of January 2027.

[API-v2] The 'torn' -> 'itemdetails' selection will stop returning TornItemDetails schema response on January 1st, 2027. Instead, it will return an array of  TornItemDetails schemas.

As always, let me know if you experience any issues with the API anywhere. 

--

The Swagger schema is now bumped to the version 6.13.5 (if you're not seeing changes make sure to hard-refresh the openapi.json file).

Please let me know if you encountered any bugs by creating a new thread in the Bugs & Issues forum.

If you would like to have something improved or just share your thoughts, please write so in this discussion thread, otherwise feel free to try this in the API v2 playground.

Hey, 

This should be fixed now. 

Thanks for the report!

This should be fixed in API v1 now as well, both for 'user' -> 'messages' & 'user' -> 'newmessages', so I think even the push notifications in the android app should work properly now.

Please let me know if it's still not working.

Thank you! 

Yeah, the fix was applied to v2 only.

The v1 has uhmm, a “bit” more complicated way to resolve this issue, but I suppose I can hardcode the fix tomorrow to API v1 too.

Hey,

This should be fixed now with the type showing correctly.

Please let me know if something is still not working.

Thanks!

Sometimes it's a little bit hard to test all of these cases without examples, however, I've made some changes:

• GET /company/applications (schema CompanyApplicationsResponse) - stats will now default to 0 instead of null
• GET /torn/hof (schema TornHofResponse) - I don't believe this to be a schema issue. The 'value' in schema is one of: 'string' | 'integer' | 'float'. I believe this one to be an issue entirely with your wrapper (as some other oneOf issues)
• GET /user/equipment (schema UserEquipmentResponse) - Schema updated to reflect this
• GET /user/missions (schema UserMissionsResponse) - I believe this to be an issue with your wrapper again. I think your wrapper might be incorrectly detecting the oneOf schemas
• GET /user/stocks (schema UserStocksResponse) - values will now fallback to 0 instead of null
• Content-type mismatch (3 endpoints) - this one was fixed recently I believe
• Low priority — enum fields that also allow any string (23 endpoints) - unfortunately, I'm not willing to turn these into just enums - sometimes these value change and the Swagger schema is not updated automatically, so at best I can turn these just into "string", but in that case there won't be any pre-populated values available. 

Thanks!

Hmmm, now that you mentioned this. I suppose it's possible that new selections won't work on old keys (since 'key' -> 'info' is automatically fetched only when you add the key). 

You can however use 'refresh' button, and it should refresh key permissions as well. 

I added auto-refresh for all keys you have saved every time you open the website, so hopefully that will prevent this from happening again in the future.

Thanks!

Thanks - that's now fixed as well for 'user' -> 'competition' in API v2.

Hey, 

From what I can see, Full Access keys do have access to 'faction' -> 'inventory', but if you're trying to access it with a key which doesn't have faction API access, you'll get the same error.

My API key (with faction access):

Another API key without faction access (but the player is in a faction):

I hope that helps! 

But please confirm that was the issue.

I will leave the bug report open and change the message (you don't have the required faction/company API access). 

Hey, 

I enabled the elimination endpoints, and updated the Swagger schema. The API playground catalogs were updated as well. 

Some things to note: 

• v2/torn/elimination - is now enabled + there were smaller schema changes. The 'leaders' array is split into 'captain' object and 'vice_captains' array. These still contain the same information as previously
• v2/torn/{id}/eliminationteam - returns a different error message now and will automatically start working at the same second the attacking period starts. The Swagger schema has not changed.
• v1/v2/user/competition - by accident, this year, users team names were leaked before the attacking period started. I've now disabled team names for all future years, but decided to leave this as is since the majority of players have joined already anyway. I also added 'team_id' to the response (I know ideally, 'team' would be an object containing 'id' & 'name' fields, but it is what it is)
• there's still torn/competition in both API v1 & v2 - you can continue using it as you wish, but the Swagger schema won't be created for it (and it mostly contains the same information as v2/torn/elimination)

Sorry about the delay, and happy coding & fighting!!

Hey, 

I'm on vacation until tomorrow, but this will be one of the first things I'll fix tomorrow. 

I didn't account that my vacation will overlap with the start of the Elimination and honestly forgot about re-enabling the endpoints before I went on vacation, but everything will be certainly ready before the attacking period starts. 

Thanks for understanding!

b

Hey everyone, 

Today's changes include:

• [API] set chain value to 0 in 'user' -> 'attacks' & 'faction' -> 'attacks' in both API v1 & v2 if the attacker is not the user or from the faction
• [Swagger] Added 'torn' -> 'rockpaperscissors' - no changes to this response in API v2
• [API-v1] Set the 'first_owner' & 'first_faction_owner' to 0 for all items  
• [API-v2] Refactored 'torn' -> 'itemstats' - this selection now also accepts multiple uids (up to 25 uids). This selection doesn't contain information about "First Owner' & "First Faction Owner". This information is now completely removed from the API, to further reduce the impact of mug bots. 
• [API-v2] Removed non weapons & non armour from 'torn' -> 'itemdetails' & 'torn' -> 'itemstats'
• [API-v2] Refactored 'torn' -> 'stats' - city stats now have improved format, reflecting the data in the City Hall. This selection will also return new error with the code '31' and the message "Cron failed, no city stats for this date" if there were no city stats updates for a specific date (API v1 will return data for one day before or after)
• [API-v2] Fixed snapshot selections headers being set as application/json instead of text/csv
• [API-v2] Disabled 'user' -> 'publicStatus'

Important deprecation warning!

The 'user' -> 'attacks' & 'faction' -> 'attacks' selections will be returning null instead of 0 value for 'chain' field, starting January 1st, 2027. The Swagger schema was updated to allow for 'null' values already.

Other deprecation warning reminders!

[API-v2] The 'faction' -> 'warfare' is now deprecated. It is replaced by other warfare selections and will be removed on 1st of January 2027.

[API-v2] The 'torn' -> 'itemdetails' selection will stop returning TornItemDetails schema response on January 1st, 2027. Instead, it will return an array of  TornItemDetails schemas.

Important note!

Please note that the upcoming API work will likely much slower in the upcoming several weeks. I'll be vacating and mostly focused on the upcoming Travel changes, so apologies if I end up being slow with replies or bugs.

Thanks! 

--

The Swagger schema is now bumped to the version 6.13.0 (if you're not seeing changes make sure to hard-refresh the openapi.json file).

Please let me know if you encountered any bugs by creating a new thread in the Bugs & Issues forum.

If you would like to have something improved or just share your thoughts, please write so in this discussion thread, otherwise feel free to try this in the API v2 playground.

Hey everyone, 

Late update today: 

• [API-v2] Added 'faction' -> 'inventory'. This selection requires Limited access key and shows armoury items for the chosen category. All of the items are cached at once for the duration of 1 hour, just like 'user' -> 'inventory'. This selection shows all item uids given to each member (weapons/armour only) and all available uids for weapons & armour. Other stackable items only show "max" uid. I decided against adding item details to this selection since that would massively increase bandwidth (over long periods of time), for information that is basically static, so you'll have to get item details for each item separately. However, before you raise your pitchforks..
• [API-v2] Improved 'torn' -> 'itemdetails' to accept multiple uids. This selection now accepts up to 25 item uids, and will return an array of TornItemDetails schema. The individual object response is now deprecated, and will be removed along with other deprecated changes on January 1st, 2027. However, there was no changes to the current behaviour, but please update your code to prepare for this change to avoid your app from crashing!
• [API-v2] Added 'faction' -> 'crimeexp' to Swagger. There were no changes to this selection.
• [API-v2] Removed 'faction' -> 'weapons', 'armor', 'boosters', 'cesium', 'drugs', 'medical', 'consumables', 'utilities', 'temporary' & 'caches'. All of these are now replaced by 'faction' -> 'inventory'

These were the last remaining changes for the 'faction' module in API v2, and I'm happy to close that down.

Once the internal site-wide inventory refactor is complete, we'll likely fully remove 1 hour cache both from 'faction' -> 'inventory' & 'user' -> 'inventory' and also possibly increase the number of uids accepted in the 'torn' -> 'itemdetails' call.

If everything goes well with this 'faction' -> 'inventory', I'll be open to reducing the cache TTL even before site wide inventory refactor is complete. 

Important deprecation warning!

The 'torn' -> 'itemdetails' selection will stop returning TornItemDetails schema response on January 1st, 2027. Instead, it will return an array of  TornItemDetails schemas.

Other deprecation warning reminders!

Important upcoming changes for this Friday, August 21st 2026!

We'll be setting the chain value to zero (0) for all incoming attacks (both stealth and un-stealth attacks) in 'user' -> 'attacks' & 'faction' -> 'attacks' both in API v1 & API v2. 
This change will also affect all existing records retroactively.

[API-v2] 'faction' -> 'warfare' is now deprecated. It is replaced by other warfare selections and will be removed on 1st of January 2027.

As always, let me know if you experience any issues with any of these changes.

Thanks!

--

The Swagger schema is now bumped to the version 6.12.0 (if you're not seeing changes make sure to hard-refresh the openapi.json file).

Please let me know if you encountered any bugs by creating a new thread in the Bugs & Issues forum.

If you would like to have something improved or just share your thoughts, please write so in this discussion thread, otherwise feel free to try this in the API v2 playground.

Interesting, 

I'm specifically setting the content-type header as text/csv, and it worked that way when I tested things (though testing is done slightly differently), so it's possible reverse proxy is overriding this. 

I'll check this out. 

Thanks!

Hey everyone, 

Several changes today: 

• [API-v2] Refactored 'torn' -> 'pokertables' - same response as in API v1, just formatted differently and added to Swagger/Playground
• [API-v2] Refactored 'torn' -> 'cards' - same as above
• [API-v2] Refactored 'torn' -> 'bank' - same as above
• [API-v2] Refactored 'torn' -> 'cityshops' - this selection will now always show all items including default restock amounts. It's also possible to pass an ID to just get items from a specific shop
• [API-v2] Added 'shops' array to 'value' object in 'torn' -> 'items' - this array shows all locations where items can be bought or sold from. Prices for 'Black Market' items are set as null. This change also deprecates the following fields in the 'value' object: 'vendor', 'buy_price', 'sell_price'. These fields will be removed on 1st of January 2027.
• [API-v2] Disabled 'torn' -> 'pawnshop' - the Donator pack sell price is now available in 'torn' -> 'items' with the above change, so this selection is no longer necessary

Important upcoming changes for this Friday, August 21st 2026!

We'll be setting the chain value to zero (0) for all incoming attacks (both stealth and un-stealth attacks) in 'user' -> 'attacks' & 'faction' -> 'attacks' both in API v1 & API v2. 
This change will also affect all existing records retroactively.

After an internal discussion it was decided this value should not be shown for incoming attacks to make the attack logs more consistent with the site and also (for stealth attacks) reduce the ability to discover the attacker. 

Let me know if you discover any issues or if you have any thoughts about these changes. 

Thanks!

--

The Swagger schema is now bumped to the version 6.11.0 (if you're not seeing changes make sure to hard-refresh the openapi.json file).

Please let me know if you encountered any bugs by creating a new thread in the Bugs & Issues forum.

If you would like to have something improved or just share your thoughts, please write so in this discussion thread, otherwise feel free to try this in the API v2 playground.

Appreciate all of the details! 

I've been able to find the bug and squash it! :)

Thanks.