Create TeamAdd Your APIDocs
Log In
Sign Up
Rapid account: tank01

tank01 / tank01

Real Time Sports Data

    Discussions

    189
    Title
    		Created at (Click to sort ascending)
    A
    2
    		 Hi Actually it ended up being pretty simple to re-use the code from NBA and I have all injuries updated now. Take a look and let me know what you think! Wed 7:07 1/5/24
    A
    2
    		 Hi Actually it ended up being pretty simple to re-use the code from NBA and I have all injuries updated now. Take a look and let me know what you think! Wed 7:07 1/5/24
    A
    2
    		 Hi sznholds, Projections for past weeks don't change, and our database only updates projections for "future" weeks once in every morning. The "current" week is updated every hour. So with that context, it would be efficient for you to keep and store locally all past week projections, and never update them. It won't be necessary. For future week projections, just call those once in the morning, store them locally as well, (they are updated between 6-7am Eastern), and for current week projections you can feel safe calling and storing once per hour. Also, you don't need to parse the file as the weekly projections come back as a json map. I don't know what language you're coding in, but for example let's say you're coding in python and you wanted Kirk Cousin's projections for week 1. If you called the api with week=1 into a variable called "response", then you could simply use the following to grab his week 1 projections: projections=json.loads(response.text) cousinsProjections=projections["body"]["playerProjections"].get("14880") Step 1 is grabbing only the text from the response with ".text", and then loading the response into a json object with json.loads() Step 2 is just calling .get() using the player's playerID. If the playerID doesn't exist for that week then it would return None. No need to do any real parsing. Hope this helps!!! Mon 5:17 22/4/24
    A
    3
    		 Ok Sznholds, we do think we have this 100% now. Thanks for your patience! Sat 3:14 13/4/24
    A
    3
    		 Ok Sznholds, we do think we have this 100% now. Thanks for your patience! Sat 3:14 13/4/24
    A
    3
    		 Ok Sznholds, we do think we have this 100% now. Thanks for your patience! Sat 3:14 13/4/24