Beerson [1576144]

This shows you don't understand the mechanic at all

30 second delay on a per-minute API call does nothing most of the time.

 

This isn't a solution, it's an excuse to pretend you "solved" the issue.

 

Turn off public bazaar API or set the delay to 30 minutes at the very least.

Show post

_SCOFIELD_ [1441750]

If people are lazy to be online when they sell shit, then they better sell in hosp.

 

If people cant come online to safekeep their cash before their hospital time ends, they better not sell through bazaar and should instead go to traders or auction (for rw stuff).

 

 

You want to completely destroy a method of mugging because the seller is lazy? Wtf seriously? The delay itself should've never been implemented in the first place.

splent [2088243]

This change isn't about traders being "lazy".

If someone is not careful enough about how they handle money while they're doing bazaar sales, they should definitely be punished for that, there's plenty of ways to store money safely.

But the punishment needs to come from players actually playing the game, those checking the markets or a few selected targets actively, and not from someone driving a car and clicking a link on a Discord bot seconds after a sale.

Personally, I'm hoping with this change traders will become more relaxed and as a result will make more mistakes that actual muggers will be able to benefit from.  

_SCOFIELD_ [1441750]

I completely agree with your viewpoint. What I do disagree with is the fact that this delay has only been placed on bazaars. why?

 

Isn't your exact argument true for people putting players on stakeouts and getting notified through said pings to come online and hosp them/ mug them or whatever? or even in wars people using bots to be alerted soon as a player meds out? Shouldn't people actually stalking the war page be rewarded then?

 

I don't mind the 30 second delay being put into place if this 30 second delay was for every single datapoint on API and not just bazaars.

Allenone [2033011]

This is a good point- I wouldn't be opposed to a 30 second activity/status delay to prevent API stakeouts.

_SCOFIELD_ [1441750]

don't get me wrong. I am not a fan of this 30 second delay. I wouldn't want the delay anywhere tbf. but it is not fair to put the delay in one place and not others.

 

This is yet another "lazy" fix by the dev team and we have seen a lot of those recently.

splent [2088243]

Hello everyone, 

There are now several new selections available in the new API v2 category 'Racing'.
They can all be accessed with "Public Access" keys:

• 'racing' -> 'cars' which returns information about cars available for racing
• 'racing' -> 'carupgrades' which returns all possible car upgrades for a car
• 'racing' -> 'tracks' which returns details for each race track
• 'racing' -> 'races' which returns the list of "open", "in_progress" and "finished" custom races
• 'racing' -> 'race' which returns details about a specifc "in_progress" or "finished" race

There will be more 'racing' selections added in the near future:

• 'racing' -> 'records' which will return a list of records for each track & class
• 'racing' -> 'hof' which will return a list of racing fall of fame rankings
• 'user' -> 'races' which will return a list of a user completed races (you can only see yours)
• 'user' -> 'enlistedcars' which will return a list of an enlisted user cars and upgrades (you can only see yours)
  
  

As always with the new API v2, these selections can be tried through Swagger (if you're not seeing them, make sure to clear cache on both Swagger page and openapi.json file).

Additionally, there was a small change on API v1 'user' -> 'bazaar' selection.
Following on this bug report, It is now possible to bypass cache when requesting data for yourself with your own API key.
This works only if you're using an API key with "Custom", "Limited" or "Full" access type (also make sure to utilize "timestamp" or any other query parameter to bypass request cache).

I hope these new selections will help with various racing competitions and statistics!

In case you notice any irregularities or bugs, please don't hesitate to let me know!


Thanks!

 

splent [2088243]

Hello everyone, 

There are now several new selections available in the new API v2 category 'Racing'.
They can all be accessed with "Public Access" keys:

• 'racing' -> 'cars' which returns information about cars available for racing
• 'racing' -> 'carupgrades' which returns all possible car upgrades for a car
• 'racing' -> 'tracks' which returns details for each race track
• 'racing' -> 'races' which returns the list of "open", "in_progress" and "finished" custom races
• 'racing' -> 'race' which returns details about a specifc "in_progress" or "finished" race

There will be more 'racing' selections added in the near future:

• 'racing' -> 'records' which will return a list of records for each track & class
• 'racing' -> 'hof' which will return a list of racing fall of fame rankings
• 'user' -> 'races' which will return a list of a user completed races (you can only see yours)
• 'user' -> 'enlistedcars' which will return a list of an enlisted user cars and upgrades (you can only see yours)
  
  

As always with the new API v2, these selections can be tried through Swagger (if you're not seeing them, make sure to clear cache on both Swagger page and openapi.json file).

Additionally, there was a small change on API v1 'user' -> 'bazaar' selection.
Following on this bug report, It is now possible to bypass cache when requesting data for yourself with your own API key.
This works only if you're using an API key with "Custom", "Limited" or "Full" access type (also make sure to utilize "timestamp" or any other query parameter to bypass request cache).

I hope these new selections will help with various racing competitions and statistics!

In case you notice any irregularities or bugs, please don't hesitate to let me know!


Thanks!

 

splent [2088243]

Hello everyone, 

There are now several new selections available in the new API v2 category 'Racing'.
They can all be accessed with "Public Access" keys:

• 'racing' -> 'cars' which returns information about cars available for racing
• 'racing' -> 'carupgrades' which returns all possible car upgrades for a car
• 'racing' -> 'tracks' which returns details for each race track
• 'racing' -> 'races' which returns the list of "open", "in_progress" and "finished" custom races
• 'racing' -> 'race' which returns details about a specifc "in_progress" or "finished" race

There will be more 'racing' selections added in the near future:

• 'racing' -> 'records' which will return a list of records for each track & class
• 'racing' -> 'hof' which will return a list of racing fall of fame rankings
• 'user' -> 'races' which will return a list of a user completed races (you can only see yours)
• 'user' -> 'enlistedcars' which will return a list of an enlisted user cars and upgrades (you can only see yours)
  
  

As always with the new API v2, these selections can be tried through Swagger (if you're not seeing them, make sure to clear cache on both Swagger page and openapi.json file).

Additionally, there was a small change on API v1 'user' -> 'bazaar' selection.
Following on this bug report, It is now possible to bypass cache when requesting data for yourself with your own API key.
This works only if you're using an API key with "Custom", "Limited" or "Full" access type (also make sure to utilize "timestamp" or any other query parameter to bypass request cache).

I hope these new selections will help with various racing competitions and statistics!

In case you notice any irregularities or bugs, please don't hesitate to let me know!


Thanks!

 

GreenNipple [2563870]

Is racing -> records and racing -> hof working? 
It is not in Swagger, and I can't seem to get it to work.

Thanks for all the updates btw

splent [2088243]

Hello,

Due to concerns of unfair advantages being gained through mug scripts as well as complaints from players worried about their API keys being linked (please note that this is an unfounded complaint, but was worth addressing), we have added a global 30-second cache to the 'user' -> 'bazaar' section in API v1.
This change applies to all requests, regardless of which query parameters are sent or which API keys are used.

We hope this change will provide better experience and enhanced gameplay for everyone.

For those who might attempt to bypass this change by scraping data, please ensure you do not violate the rules, especially those regarding page scraping: 
https://www.torn.com/rules.php

Thanks.

splent [2088243]

Hello,

Due to concerns of unfair advantages being gained through mug scripts as well as complaints from players worried about their API keys being linked (please note that this is an unfounded complaint, but was worth addressing), we have added a global 30-second cache to the 'user' -> 'bazaar' section in API v1.
This change applies to all requests, regardless of which query parameters are sent or which API keys are used.

We hope this change will provide better experience and enhanced gameplay for everyone.

For those who might attempt to bypass this change by scraping data, please ensure you do not violate the rules, especially those regarding page scraping: 
https://www.torn.com/rules.php

Thanks.

SirJux [2695126]

08:10:59 - 06/08/24 You opened your bazaar

 

08:11:08 - 06/08/24 You sold a Small Arms Cache on your bazaar to Guimz13 at $12,120,000 each for a total of $12,120,000

08:11:18 - 06/08/24 You sold a Small Arms Cache on your bazaar to Guimz13 at $12,120,000 each for a total of $12,120,000

 

my question is... where the f**k is 30 sec API delay because Guimz confirmed that he bought the items via bot ping.

Omanpx [1906686]

Again, you are confusing endpoints. The 30 sec delay is for personal bazaars, not the market endpoint. Even if it had a 30 sec delay though, you could have just had bad luck and placed them right before the global 30 sec refresh. It's not a 30 sec delay, but a 30 sec global update interval anyway.

Omanpx [1906686]

Again, you are confusing endpoints. The 30 sec delay is for personal bazaars, not the market endpoint. Even if it had a 30 sec delay though, you could have just had bad luck and placed them right before the global 30 sec refresh. It's not a 30 sec delay, but a 30 sec global update interval anyway.

SirJux [2695126]

then whats the f**king point of that delay :D CHANGES NOTHING.

Wolverine [1971836]

can you add the "is_shit_post" field to filter the posts to skip?

 

sorry, I could not resist, I'm joking :-P

Wolverine [1971836]

can you add the "is_shit_post" field to filter the posts to skip?

 

sorry, I could not resist, I'm joking :-P

splent [2088243]

I don't understand...why would you want all of your posts to be skipped? :P

 

 

splent [2088243]

I don't understand...why would you want all of your posts to be skipped? :P