1. Erik Berg 16/May/2013 at 5:50 PM EDT
Yes, you are right, the players do have a unique ID now. It has not been encouraged or advertised for use because it is a stopgap solution until a permanent ID scheme is developed. See /api/issues/127 In the next update of the website (1 AM ET), I will add a rosters method that can be accessed at nba/team/TEAM_ID/roster.json and will add the player ID later when /api/issues/127 is closed.
2. Davide Tarasconi 17/May/2013 at 6:26 AM EDT
Good, I was tracking issue 127 but I preferred opening a new one - I didn't know if and how the two issues could be related. Thanks.
3. Davide Tarasconi 20/May/2013 at 6:34 AM EDT
I've seen the roster JSON file, it's a welcomed improvement (thanks!): - you should add documentation; - no unique IDs (linked to issue 127); - no player availability data (is there a way to grab an add status like "injured" "illness" "day-to-day"?). In terms of building a generic data scheme I understand that player availability is not a priority and you could consider it a custom request - I'm just making assumptions on my simplified fantasy league use case in mind.
4. Erik Berg 21/May/2013 at 8:49 AM EDT
Just wanted to add the rosters method so you could try it out for now. When the ID issue is settled, I will officially add the rosters method and documentation for it. Player transactions and injury tracking is in the works.
5. Davide Tarasconi 21/May/2013 at 8:53 AM EDT
6. Davide Tarasconi 20/Jun/2013 at 3:00 PM EDT
Hi, it seems that the above mentioned roster method (e.g. /api/nba/team/indiana-pacers/roster.json) is not working anymore, could you give me an update on that, please?
7. Davide Tarasconi 20/Jun/2013 at 3:15 PM EDT
Gosh, I'm an idiot, I got the URL wrong. Everything works file, sorry for the warning.