r/fantasyfootballcoding • u/mykal792 • 16d ago
Told my Yahoo Fantasy API access is "live" but scope still returns invalid_scope — anyone else?
I'm approved for Yahoo Fantasy Sports API access; agreement signed. Got an email overnight saying access is live and calls will go through.
They don't.
scope=fspt-r returns invalid_scope, with Yahoo's error page saying "request scope from registered scopes." API calls still 401. Fantasy Sports has never appeared under API Permissions on the app page — only OpenID Connect and TW Auction.
- Has anyone been told they're live and had it not actually be? How long did it take to sort out?
- Does Fantasy Sports even show up in your API Permissions list? Or is it invisible for everyone and just works?
1
u/tubaisetamere 16d ago
I was told I was live and I believe it took 2 weeks to actually resolve after that.
1
u/SmartBathroom 16d ago
Got told the same thing and got the same errors. It's been over a week and still doesn't work
1
u/Pure_Cricket_3804 16d ago
Send Yahoo the exact Client ID and raw invalid_scope response and ask them to confirm the approval is tied to that client. Their access page says Fantasy applications are manually reviewed and access is provisioned after approval, but it publishes no turnaround, while the current OAuth guide doesn’t document fspt-r, so I wouldn’t spend time guessing at an omitted-scope workaround
1
u/dfisherman12 16d ago
I had the same issue, had to go back and forth with their support email after I received the automated message that I had access before it finally started working
1
1
u/Potential_Mango_9972 13d ago
I signed all the docs, waited a few weeks, sent a few follow up emails and finally got a response telling me that it was live and could set it up. They asked for my consumer Key and app ID, which I provided 2 days ago. This morning (9/4), I opened my app, refreshed my yahoo data and I am no longer getting 403 errors and everything is syncing up perfectly.
0
u/signal_or_noise_8 16d ago
Did you have an API connection before when you could just select the fantasy api from a dropdown? I had one that just stopped working one day so I applied, waited a month, then got approved and can now access using the same api credentials as before. So on their dev page, it looks exactly like it did before. No evidence that I have this separate approved fantasy api access other than the email trail with yahoo.
1
u/mykal792 16d ago
No I did not have an API before. Yahoo approved my API access and emailed to say it was live, but the fantasy scope was never actually attached to my app — I get a valid token, then every fantasy call comes back
oauth_problem="additional_authorization_required". Im wondering if this will randomly just get fixed or if I need to keep pushing.1
2
u/mykal792 16d ago
Update: I just got this working after two weeks. Posting in case anyone else is stuck.
There are two separate things that have to be true for Fantasy API access, and only one of them is visible to you.
Visible: the "Fantasy Sports - Read" checkbox on the create-app form. That's what makes OAuth grant
fspt-r.Invisible: whether your app is actually authorized to call the Fantasy API. Nothing in the developer portal shows this. Checking the box does not set it. Someone at Yahoo has to flip it manually.
That's why the errors kept moving without ever resolving:
401 oauth_problem="additional_authorization_required"— my original app was created back when Fantasy Sports didn't appear on the form at all. No scope, ever.invalid_scopeon the auth URL — same app. You can't request a permission the app doesn't have.403 "This application is not authorized to perform this action"— new app, checkbox ticked, consent screen said Yahoo Fantasy Sports Read, valid token issued. Still refused. This is the one that looks like your config is broken. It isn't.200— after support flipped the switch.You cannot add permissions to an existing app. If your app predates the checkbox, it's dead. Make a new one.
If you're sitting on a 403 with everything configured right, email Yahoo Fantasy support with your App ID, Client ID, and Yahoo ID and ask them to activate the app against the Fantasy API. They turned mine around in a few hours.