Upcoming API changes

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 

It's hard to say right now. That really depends on at what stage will v2 be after the inventory migration.

If there will still be a long way to finish v2, I think it will be reasonable to restore inventory section on v1 until then (provided it won't be too much db heavy). 

As to on when is this going to happen - I can't provide any information there unfortunately.

And thank you!  :)

One of the most important things in my opinion is to streamline the suggestion process for the API. Currently it's driven by someone making a B&I post, Ched responding with "live in production" and that's that (slightly exaggerated of course, but the point is still the same), even if we are talking about breaking changes.

Documentation and an OpenAPI spec would be great, as what we currently have for official documentation doesn't even qualify to be called documentation imo. I'm trying my best to maintain a third-party documentation project, but first-party is always better.

Thank you everyone - there are some solid suggestions and advices here!

I'm still getting familiar with the codebase, but setting up a public project board is also something Chedburn suggested I should probably do, so I'm definitely open to doing that. It will just take some time to structure everything and write everything down, but we'll get there.

@DeKleineKobini - you do have a point. I agree that the current way of how API changes were made wasn't the easiest for those using the API, but considering how many things Chedburn is managing and doing, I think it's great he even managed to update the API at all!
Better documentation and OpenAPI spec is definitely something I see as a priority and must have have in v2.

I'll also set up a separate thread here for suggestions soon. 

@Stig - auction API is something I too asked about a month ago - https://www.torn.com/forums.php#/p=threadsf=19t=16392176b=0a=0start=0to=24644707 and it's definitely something I'll look into at some point, but it might have to wait until the inventory rebuild is completed.

@Omanpx & @Kwack - I'll have to find out what could be done about the forum API, but I wouldn't be too optimistic here, at least not right away. I'm also not saying no, but I'm just seeing many potential issues here, especially considering the amount of data that forums hold.
But, I do like the ideas and especially considering it could enhance community driven events like the one you mentioned I'll investigate!

Thanks!