Hello,

I help moderate a speedrun.com site. I was wondering if it's possible to view ALL rejected runs over the entire course of the game's page.

As of right now, when I go to the rejected runs section it only shows the latest 11 rejected runs (which are all 3 or less weeks old). If I click the "Show Old" button, it shows the first 30 or so rejected runs (all of which are from 3 years ago).

I would like the rejected runs in between these time periods... But I can't find them. Is this possible, or am I missing something obvious?

If you have access to the Audit Log for the game you can filter for run-reviewed and then ctrl-F for "rejected".

The problems is that the audit log is specific to one game (can't show all rejected runs by user), and also that the audit log is terrible for searching stuff.

Yeah the current rejected runs tab is completely useless, because when the list is full, it only shows rejected runs from 2-3 weeks ago, so you have to wait 2-3 weeks to see the most "recent" at that point already very old rejected runs.

Easiest way to get it would be through the API, like so: https://www.speedrun.com/api/v1/runs?game= [game-id] &status=rejected

And to get the Game ID for a specific game, you can do this: https://www.speedrun.com/api/v1/games?name= [Game Name Here]

that is definitely much worse than audit log. I don't even know where to start xD Also it's showing verified runs? And definitely not all of them there are only a few

edit: for seterra I only see a bunch of verified runs from may 2019 in here https://www.speedrun.com/api/v1/runs?game=k6q4rqzd

If you use Firefox it shows up in a way that's significantly easier to read. It's more for programmatic use though rather than reading, so yeah audit log might be a little easier to parse.

It's showing verified runs because you didn't include this part at the end: &status=rejected

Ah ok, but it still shows only a bunch of rejected runs from 2019

@dha All calls to the API are limited in the amount of data elements they return. The default limit is 20. To do an API call with a higher limit, you should also add a "max" parameter. The maximum value for that parameter is 200.

So you can do this: https://www.speedrun.com/api/v1/runs?game=k6q4rqzd&status=rejected&max=200

Now, since there is a limit, to get the next batch of elements after the current batch you should also add an "offset" parameter, which is the index of the starting element in the batch. The default for that parameter is 0.

So you can do this to see all 376 rejected runs of Seterra: https://www.speedrun.com/api/v1/runs?game=k6q4rqzd&status=rejected&max=200&offset=0 https://www.speedrun.com/api/v1/runs?game=k6q4rqzd&status=rejected&max=200&offset=200

ah, thank you oreo, that is too complicated for me xD

hopefully new elo team will improve that aspect too

I mean it's an API, it's set up the way it is for a reason (like I said, programmatic, not necessarily reading it directly). I only brought it up because it's another somewhat overlooked way you can get all the rejected runs. If it's too complicated then yeah just use the audit log.