#fantasysports API returning persistent 403/401 on roster endpoint since July 24
I'm the developer of a registered Fantasy Sports API application (Client ID: dj0yJmk9TmtQaVFTZE16NVNEJmQ9WVdrOVJWZDFZMGcwY1c0bWNHbzlNQT09JnM9Y29uc3VtZXJzZWNyZXQmc3Y9MCZ4PTYw). Since July 24, 2026, roster requests (GET /fantasy/v2/team/{team_key}/roster) have been intermittently, then consistently, returning 403 Forbidden (occasionally 401). As of July 28 this is happening on essentially every request, across all 3 linked accounts and all teams.
This isn't a stale token issue. My logs show a completely fresh access token, issued moments earlier via a successful oauth2/get_token refresh grant (200 OK), being immediately rejected by the roster endpoint. Request volume is very low (roughly 200-250 requests/day across 3 users), well below anything that should trigger rate limiting. I don't see any warning or flag on the app in the Developer Console.
Affected teams: 469.l.2072.t.12, 469.l.203368.t.5, 469.l.234519.t.1
Could someone look into whether this Client ID has any restriction in place? Happy to provide more logs/timestamps if useful.