You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be worth considering using a combination of the GC match details call and the match metadata blob to assemble a similar API response as GetMatchDetails if Valve does not fix this endpoint soon.
However this means making a GC call for each match to backfill which might be a lot.
The text was updated successfully, but these errors were encountered:
Another possibility is to use GetMatchHistoryBySequenceNum on a single match. However this may be subject to rate limits--it is primarily useful for allowing users to request matches to update visibility.
It may be worth considering using a combination of the GC match details call and the match metadata blob to assemble a similar API response as GetMatchDetails if Valve does not fix this endpoint soon.
However this means making a GC call for each match to backfill which might be a lot.
The text was updated successfully, but these errors were encountered: