Congrats on the job.
One thing I would LOVE to see, if a person's revive status is anyone, friends / faction or none.
At present, its yes or no and a yes doesnt say who can revive so when checking faction members during a RW, unless we ask someone outside of the faction, who is not a friend, we dont know what the status really is
Upcoming API changes
Started by splent [2088243] Admin on in API Development.
Posts archived: 381 / 381 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
I'm mostly excited to see and use the openapi specs!
Would the new v2 be like the current HTTP API or would it be a RESTful one? Also have you also considered using GraphQL? Depending on how the backend is structured it might make it more lightweight.
I hope you bring back the inventory API. It was really useful, even if it serves cached results that updates once a day.
Additionally, I would love to be able to see forums in the API; things like if you have any unreads in a topic you participated or any replies to your posts etc.
Fantastic news!
Congrats on this new assignment. I'm sure you will receive a lot of support from the community on the way.
I will follow it's development with excitement and am looking forward to it.
I don't think GraphQL is an option given the Torn's project structure (without major refactoring), and tbh, I worked a lot with GQL in the past 5 years, and I can't really say I liked it very much. 😅
Between the current API and RESTful API (although, in a way, the current API is RESTful), the structure will likely stay the same.
There's one big advantage in the current setup, and that's combining multiple selections (e.g. https://api.torn.com/user/1?selections=profile,personalstats&key=) inside of one API call, which makes things easier for some people.
As for inventory and forums API, I've already covered these topics in my previous posts, but how/why/when will be much clearer once I'm done with the public board! :)
Amazing, thank you!
I don't think anyone likes GQL if they are honest with themselves :D But it's convenient sometimes, and it kinda does the selections thingy in a more structured way. But that's not important! Happy to get a better API one way or another.
As a side note, something that might be helpful is an additional field in the json specifying when this data was cached (or if it was cached at all). As sometimes different tools request end points and the tools aren't synced with each other, so one of them gets the results way later than the other, but if we get the cache info, the tool that is getting info later can adjust its timing. This might be overengineering it but if it's not hard to implement in v2 I would love to have it.
Also, not sure if it was mentioned, but number of remaining calls until rate limit would be amazing! Would help a lot with load balancing when using multiple keys on heavy tasks.
I feel like a cache hit header would be preferable to a JSON key-value pair given it wouldn't need to be serialized and de-serialized constantly and cache hit headers are somewhat "standardized".
If I may ask, what does this mean for us laymen, what sort of enhancements and benefits could we see perhaps in our day to day experience?
Well, if you have friends/faction mates that work with Torn’s API, you’ll see their sanity improve dramatically.
Anyways, with the API being more approachable, you’ll start seeing more tools from new developers. Existing tools will become faster, have more features that weren’t previously possible, break less often and inevitably you’ll see more people complain about “the API being overpowered”.
Welcome!!!!!
This is amazing!
Hello everyone,
I would like to inform you about an upcoming minor change in the API v1.
Per Ched's comment on this popular suggestion and following up on internal discussions, we have decided to remove the 'tokenrefills' and 'traveltime' fields from the 'user' -> 'personalstats' section.
However, please note that these fields will only be removed from being visible to other players. You will still be able to access these fields for your own account using your own API key.
The primary reason for this change is that these fields have been exploited in various mugging scripts, leading many players to believe that their API keys were leaked when, in fact, they were not.
We understand that this change might not be welcomed by everyone, but it is necessary to ensure a fair gameplay experience for all.
This change will likely take effect in the latter half of this week (this Thursday or Friday).
Thank you for your understanding.
Mauro
RIP token refill muggers!
Also, I thought the v1 api was being frozen, with changes being made to v2?
Perhaps I have misread?
Took you bastards long enough. How many TRILLIONS have been stolen by illegal scripts abusing this? They should ALL be fedded.
Something like a year and half or two years to do it after Chedburn said it? What the hell?
It's frozen, but exceptions are made. splent said he'd do bug fixes and things like removing unfair advantages.
Trash
Might as well remove mugging altogether now
No more simulating sitting outside a casino waiting for ppl to go to the ATM.
R.I.P. pvp rimes in crime game
add this to the ever growing list of things removed from torn lol
remove christmas town next, its a source of cans into the economy and this is eating into donator pack sales
While I agree that Xmas town is a little ridiculous due to it's can influx. This is honestly a half hearted updated to a serious problem. It should be removed completely.
g8 b8 m8, I r8 8/8