2025 API Request - Furthering Game Logs API
-
Hey SDS/MLB The Show team,
I'm sure your team saw the popularity of Showzone Savant beta. We accumulated over 8 million at bats from your Game Logs API based on the request of our users. We were extremely grateful to get the Game Logs API and want to thank you again to help me create this - which has been a dream of mine.
As we mentioned last time we requested this, it was in passing, so with the game being 2 months out we want to circle back to it:
We absolutely need the card IDs for the cards used in the game log/box score. We've developed an extremely.. impressive script of trying to create assumptions of what card users are using to try and speed up their matching process.
We're having to match a variety of the last name (because that's all we get), position and created quick features to apply assumptions to all box scores with that name and position but... it's tough. It's all tough. And we're seeing about an 80% application of our assumptions, but it's clearly a feature the fanbase wants, and the lack of card ID makes it an extremely limiting factor for who will use it.
The problem is, if you're truly dropping Sets & Seasons, this gets way harder. We were effectively using the Sets and card debut date to try and assume what card you were using when names matched.
In short, we want to help users play your game more competitively, to improve and grow as players and have deep stats.
We want to and are excited to basically the "Savant" to your "MLB" but to take a step forward, we desperately need this. We have so many directions we want to take Savant but when users find savant in August, and have to spend 4 hours filling in our assumptions, and guessing who was in their BR lineup with "Smith" as the last name in March, it makes it impossible.
My requests could go further, but I understand limitations. I will settle for this, but going to write out some of the extras that would help make this even cooler:
- pitch location data in a JSON format - to find strikeout tendencies that are not guestimated by the written box score
- exit velo data with pitch location in a JSON format - to find hitters strongest swing areas (aka where they should look or do look to do damage)
We're excited to help empower your community to truly digest their weakness, formulate action plans from their strength and continue to push the userbase to take competition seriously.
With love,
Shane
