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
Yahoo Fantasy API has a rate limit of 2,000 unsigned API calls per hour and 20,000 signed calls per hour. It might be something on my end, but the oauth.session.get() doesn't seem to be sending signed requests. I've tested on single-calls and get a Response 999 (rate limit) error about very 15 minutes which amounts to between 450-550 calls. This rate is roughly 2,000/hr.
It seems like the credentials file might need an 'id_token' field (see the OAuth 2.0 Authorization Endpoint section of the Yahoo Dev documents and this part detailing the id_token. I'm not certain about this though because the Yahoo Fantasy Sports guide has sample PHP code that creates a "_make_signed_request()" function that creates/uses a HMAC-SHA1 signature. Maybe you need both? I'm not totally sure.
The text was updated successfully, but these errors were encountered:
Yahoo Fantasy API has a rate limit of 2,000 unsigned API calls per hour and 20,000 signed calls per hour. It might be something on my end, but the oauth.session.get() doesn't seem to be sending signed requests. I've tested on single-calls and get a Response 999 (rate limit) error about very 15 minutes which amounts to between 450-550 calls. This rate is roughly 2,000/hr.
It seems like the credentials file might need an 'id_token' field (see the OAuth 2.0 Authorization Endpoint section of the Yahoo Dev documents and this part detailing the id_token. I'm not certain about this though because the Yahoo Fantasy Sports guide has sample PHP code that creates a "_make_signed_request()" function that creates/uses a HMAC-SHA1 signature. Maybe you need both? I'm not totally sure.
The text was updated successfully, but these errors were encountered: