Upcoming API changes

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.