This is fantastic news! 

Will inventory access be restored to v1 post-inventory migration, or will it only be available for v2?

I presume this would fall under the exceptions for V1 changes. 

I know you're waiting on other teams before you can do anything, but any information on when we could expect that inventory selection returning? We get asked this regularly over at PDA and currently my answer is "shrug, I'm not sure"

edit forgot to mention - congrats! Looking forward to the future of torn's api 🎉

Welcome to the Torn dev team!

Looks like a great plan outlined.

Hello!

I suspect I may be preaching to the choir, but I think a properly documented and publicly published roadmap with bugs/issues tagged against key milestones, and a rigorous development process which includes community involvement, might alleviate any "breaking" of changes that you might come across.

We can handle unstable, as long as we know it ahead of time.

 ~ Rich

p.s. I'm an opinionated pain in the ass. I'll apologise in advance if it helps.

Congrats on the new position! Looking forward to updates and increased stability (fingers crossed!).

One feature that would be nice to have is some sort of Forum API - it would create more opportunities for community-run events, such as this one. Something like Poster name, ID, time posted, last edited, post content, likes, dislikes.

Now if you'll excuse me, i'm off to scrape 50+ pages of posts to get the user IDs for the event :D

Yes please, something like this would be awesome. Access to the updates column via api (feed/subs/friends) would be nice too. 

Also wouldn't mind an ability to search the forums but I understand that wouldn't really mix well with the current style of the api.... a duck can dream though. Being able to get notifs for people mentioning my name would be sick

Welcome! Super excited to have a developer focused on API changes.

One thing I think I and almost every developer would love to see is some sort of OAUTH2! 

Welcorme, and nice name! Very excited also to have an independent developer working on the API, and what the future of the API could look like. 

A few useful things off the bat:

• Auction House API
• Standardisation as you mentioned
• Documentation for the new devs

All the best. 

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!  :)

Am I the only one who hates the key value thing I see everywhere in the torn api? 

Happy to see an open api documentation for the V2 version of the API. Code generation is just not a fun experience with the torn api, open api should fix that :)

Is V2 going to be able to tell me how many calls I have left? Should be somewhere in the response body !

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.

Are you referring to JSON? 

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!

Where?

You've probably heard this thousands of times, but an Auction House API would be amazing :D

I think that the crimeHubApi data should also be accessible through the normal player api. (This is data regarding what projects you currently are working on, how your card skimmers are doing, etc.)

The ability to paginate through more than the latest 100 reports on the user report endpoint, would be greatly appreciated.

Congrats, splent!!  I'm so excited for what the future holds reading your inital roadmap.  Amazing news!