Sleeper Fantasy NFL Trending Players Scraper
Pricing
from $0.80 / 1,000 results
Sleeper Fantasy NFL Trending Players Scraper
Collects Sleeper Fantasy NFL trending player adds or drops over a configurable lookback window and returns each player as a flat row with trend count and player ID.
Pricing
from $0.80 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Sleeper Fantasy NFL Trending Players Scraper
Scrape Sleeper fantasy NFL trending players, most added or most dropped, with add/drop counts and player details. Get the players your league is chasing or cutting, ranked over any lookback window from 1 to 168 hours. No login, no API key. Export to CSV, JSON, Excel, or XML.
Sleeper's public fantasy API returns raw trend IDs, but turning them into actionable player data means extra calls and joins. This Actor pulls the trending adds or drops for NFL fantasy football, enriches each player with their name, position, team, and add/drop counts, and returns one flat row per player. It is built for waiver-wire research, trade analysis, and league-mate behavior tracking.
| Who uses it | What they scrape Sleeper for |
|---|---|
| Fantasy football managers | Which players to target on the waiver wire this week |
| DFS players | Which players are gaining or losing roster share before lock |
| Fantasy analysts | Which adds and drops are moving the market across leagues |
| Sports bettors | Which player trends signal public sentiment shifts |
What it does
This Actor collects Sleeper NFL trending players by add or drop trend, enriches them with player details, and returns each player as one flat row.
- ๐ Most added: the players fantasy managers are adding to rosters right now, ranked by add count over your lookback window.
- ๐ Most dropped: the players being cut most, ranked by drop count over the same window.
- โฑ๏ธ Configurable lookback: set any window from 1 to 168 hours to catch short-term spikes or longer trends.
- ๐ข Trend limit: request up to 200 trending players from Sleeper before enrichment, so you control the candidate pool.
- ๐ฆ Flat output: every player comes back as one row with name, position, team, and add/drop counts, ready for CSV or a spreadsheet.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Sleeper data
๐ Waiver wire targets.
A fantasy manager runs the Actor for most added players over the last 24 hours to see who is being picked up before waivers clear.
๐ Drop candidates.
A manager checks most dropped players over 48 hours to decide which of their own players are losing trust across leagues.
๐ Market sentiment.
An analyst pulls both add and drop trends over a week to compare roster churn and write a weekly waiver column.
๐ฐ DFS ownership shifts.
A DFS player monitors adds over the last few hours before lock to spot chalk and pivot options.
Why choose this scraper
| What you get | |
|---|---|
| No API key | Reads Sleeper's public JSON endpoints directly, no registration or OAuth. |
| Enriched players | Each trend row includes player name, position, team, and add/drop counts. |
| Flexible lookback | Rank trends over 1 to 168 hours to match your waiver or DFS window. |
| Add or drop | Switch between most added and most dropped with one input. |
How it compares
This Actor focuses on enriched NFL trending players, while the competitors below either return raw IDs or cover broader Sleeper data.
| Feature | ParseForge | Sleeper NFL Trending Players Scraper - Fantasy Data | Sleeper Fantasy Sports Scraper |
|---|---|---|---|
| Enriched player details (name, position, team) | Yes | Not listed | Yes |
| Add/drop counts | Yes | Yes | Yes |
| Configurable lookback window | Yes | Yes | Not listed |
| Trend limit control | Yes | Not listed | Not listed |
| NFL only | Yes | Yes | Not listed |
| No login required | Yes | Not listed | Yes |
Configure the run
Drive the Actor with a trend type, a lookback window in hours, and a trend limit, and it returns the top trending players with their details. The Input tab lists every parameter.
A first run with the defaults:
{"maxItems": 10}
A larger pull:
{"maxItems": 200}
Pricing
Pay-per-result: $0.001 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.10 |
| 1,000 results | $1.00 |
| 10,000 results | $10.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Sleeper Fantasy NFL Trending Players Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Sleeper through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/sleeper-fantasy-nfl-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that your lookback_hours is within 1 to 168 and your trend limit is at least 1. Sleeper may return fewer players than requested if there is not enough activity in that window.
Why are some players missing details like position or team?
Sleeper's trend endpoint returns player IDs, and the Actor enriches them from the player database. If a player is very new or has been removed, some fields may be blank.
Why did I get fewer players than maxItems?
maxItems is the maximum number of players to collect, but the actual count is limited by the trend limit and what Sleeper returns. Increase trend limit if you need more candidates.
Can I get historical trends?
No, the Actor only returns current trending data from Sleeper's live API. To track changes over time, schedule regular runs and store the results.
FAQ
| Question | Answer |
|---|---|
| Do I need a Sleeper API key or login? | No. The Actor reads Sleeper's public JSON endpoints, so no authentication is required. |
| What is the difference between add and drop trends? | Add returns the players most added to fantasy rosters in the lookback window. Drop returns the players most dropped. |
| What does lookback_hours control? | It sets the time window in hours used to rank the trend. For example, 24 ranks adds or drops over the last day, while 168 covers a full week. |
| How many players can I get per run? | You can set maxItems up to 1,000,000, but the actual number returned is limited by the trend limit and how many players Sleeper returns. |
| What player details are included? | Each row includes the player's name, position, team, and add or drop count, along with the trend type and lookback window used. |
| Can I get both add and drop trends in one run? | No, each run returns one trend type. Run the Actor twice with type set to add and then drop to get both. |
| Is this only for NFL? | Yes, this Actor is built for Sleeper NFL fantasy football. For basketball or other sports, use a different scraper. |
| What export formats are supported? | You can export the results to CSV, JSON, Excel, or XML from the Apify dataset. |
| How fresh is the data? | The Actor pulls live data from Sleeper's public API at the time of the run, so it reflects the current trending rankings. |
| Can I schedule this to run automatically? | Yes, you can set up a schedule in Apify to run the Actor at intervals, such as every hour or every day before waivers clear. |
Related actors
Browse the full ParseForge collection for more scrapers.
๐ Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
โ ๏ธ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Sleeper, Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
