GetMatchDetails API endpoint stopped to provide any result

[Dmytro4]

Description

After the release of 7.36 "GetMatchDetails" does not provide any result on any match, just an empty array. Many sites like Stratz and Opendota are affected as well so new matches can not be parsed.

https://api.steampowered.com/IDOTA2Match_570/GetMatchDetails/v1?key=#&match_id=#

[Froctnow]

The endpoint https://api.steampowered.com/IDOTA2Match_570/GetMatchDetails/v1 for web API stem also doesn't work

[Dmytro4]

i would like to add that it returns 500 error for any match_id

Status Code:
500 Internal Server Error

[ikonduktor]

Any decisions?

[a361570441]

same issue , any solutions? TOT

[daveknippers]

please come back API

[ralfizzle]

Having the same issue

[eremenko1]

up

[ikonduktor]

It doesn't work 5 days already

[statdota]

Same, up

[ikonduktor]

I see that dotabuff and opendota somehow can parse finished matches. Anyone know how do they do that?

[statdota]

I see that dotabuff and opendota somehow can parse finished matches. Anyone know how do they do that?

IDOTA2Match_570/GetMatchHistoryBySequenceNum

[dota-coach]

@Valve: Shall we all migration to GetMatchHistoryBySequenceNum?

[Dmytro4]

@Plagman @danieljennings @casieber @bgilmore @charleslvalve @kisak-valve
Hey, the main basic Dota 2 API for tracking matches has not been working for two weeks already. This API endpoint is essential for any functionality that involves data from matches. It highly impacts any software that works with Dota 2 stats, trackers, wikis, and more.
The absence of this method is prompting most developers to come up with specific methods that might create a higher load on the system or go against the ToS. Please fix this issue or provide some details.
Thanks

[Noxville]

@dota-coach That means keeping up with that endpoint, which is pretty annoying to do on a single IP; and you won't get a bunch of the data (draft info, ability upgrade info, etc).

[snudel]

thats sad. did you guys migrate?

[roserens]

@dota-coach That means keeping up with that endpoint, which is pretty annoying to do on a single IP; and you won't get a bunch of the data (draft info, ability upgrade info, etc).

Yes. You need 2 IPs for full parsing. I have 2 for loading the ca. 1 mn matches per day and then I can scale up to 8 IPs, if I need to catch-up (for whatever reason).

[roserens]

thats sad. did you guys migrate?

I'm working on a migration to the Game Coordinator now. Which is not ideal, but probably the way to go.

If you have any other options, please let me know.

[snudel]

Did you guys manage to migrate?
I tried calling GetMatchHistoryBySequenceNum but it seems to ignore start_at_match_seq_num when handing over the matchid. or is this sequence another number than the matchid?

nevermind: checked the return of GetMatchHistory for a player-id. its in there. sequence number is a different id than matchid

[eremenko1]

Up

[roserens]

Yes, I migrated to the game coordinator. But as @Noxville pointed out there is some information missing, e.g. ability upgrades.

Therefore I first fetch the data from the game coordinator and then fetch the meta data from the valve server. A little cumbersome, but it works.

I also published the meta data fetcher & parser as npm package, if you use javascript you can reuse it. It's quite lean: https://www.npmjs.com/package/dota-meta-parser

[ikonduktor]

@snudel i've migrated to GetMatchHistoryBySequenceNum API. But need to parse all entire matches... Sad.

[roserens]

@snudel i've migrated to GetMatchHistoryBySequenceNum API. But need to parse all entire matches... Sad.

Yes, that's true. And then if you want to store all the matches, it will consume a lot of disk space, too.