Yahoo Fantasy Sports

### App
Yahoo Fantasy Sports

### Summary:
No Authorization for 2026

### Details:
My Yahoo Fantasy Sports workflows are now receiving HTTP 403 errors after previously working correctly.

After troubleshooting with Pipedream AI, we confirmed that even a basic request to:

`/fantasy/v2/games;game_codes=nfl`

returns:

**403 — "This application is not authorized to perform this action."**

We tested this independently of my league key, so this does not appear to be caused by my new 2026 league ID or an incorrect season/game key.

In researching the issue, I found that **Yahoo appears to have changed its Fantasy Sports API access requirements in 2026 and now requires applications to be specifically approved for Fantasy API access**. Existing developers have also reported previously working applications beginning to receive similar 403 authorization errors following these changes.

Since Pipedream's `@pipedream/yahoo_fantasy_sports` integration uses a Pipedream-managed Yahoo OAuth application, the testing indicates that this OAuth application may no longer have authorization for Yahoo Fantasy API endpoints.

Could you please confirm:

* Whether Pipedream's Yahoo Fantasy Sports OAuth application currently has Yahoo's required Fantasy API approval/access for 2026.
* Whether Pipedream is aware of the recent Yahoo Fantasy API authorization changes.
* Whether access can be restored for the existing integration or if there is a way for me to use my own Yahoo Developer credentials with Pipedream.

This integration worked for me previously, and the current failure appears to be at the Yahoo application/OAuth authorization level rather than within my workflow code.

### Screenshots:
No screenshots included

Start by reproducing the 403 response from `/fantasy/v2/games;game_codes=nfl` and inspect the `@pipedream/yahoo_fantasy_sports` integration's OAuth configuration. Confirm whether the Pipedream-managed application has Yahoo Fantasy API approval for 2026 and whether existing access can be restored or user-supplied credentials are supported.

Written by the indexing model from the issue text.