1. Erik Berg 26/Jul/2016 at 8:57 PM EDT
Endpoints that return data for specific players will be added when there is a solution for player IDs. What is the problem with player IDs? Well, I would like to partner with the greater sports community, other sports data services, etc. to create an open, non-proprietary, completely free database that contains basic biographical information for professional athletes (e.g., names, birthdate, birthplace). This would reduce typographical errors, help disambiguate players with the same names, eliminate duplication of efforts, and provide an easy way to cross reference players between different services.
2. Tim Young 7/Oct/2016 at 9:15 AM EDT
I would love to see this too. Is there something in the works for this common database? I can understand why you'd want that. If this is not even close though then I'd still like to have access to a player game log (for example /mlb/player/5474). Is this player id unique to xmlstats?
3. Erik Berg 9/Oct/2016 at 11:43 AM EDT
The player ID database persists as an idea only. I'll write a document that outlines the benefits and goals of a central free, open player ID database and post it on xmlstats and link to it from Twitter. Let's see if it gets any traction. I hope the community sees the benefit of having a free sports data API! And yes, the ID in your link is an auto incrementing number specific to the xmlstats database.