Building an FPL planner, a team rater or an AI assistant? Use the FPL Cat model's numbers instead of building and maintaining a model of your own. Every player, keyed by FPL's own element id, as JSON or CSV, refreshed whenever FPL posts team news.
What a Pro key lets you do
- Use it in your own models, scripts and apps, including apps other people use, while you have Pro.
- The one condition: wherever you publish the numbers (a website, an app or a post the public can open), show “Projections: FPL Cat model” with a normal link to fplcat.com (not hidden, not nofollow). A key used without it is revoked. Private use needs no credit: your own scripts, or showing a friend. When you make a key, you tell us where the numbers will appear.
- Keep your key to yourself and don't resell the raw data.
What you get
Projections, 6 gameweeks
GET /projections
Every player's projected points for each of the next 6 gameweeks, with expected minutes, chance of playing, return, haul and blank chances, a likely range and where the points come from.
Prediction record
GET /record
What the FPL Cat model projected for every player shortly before each deadline since GW6, frozen, next to FPL's own projection and the points scored. Grade it yourself before you rely on it.
Injury list
GET /injuries
Every player FPL flags, with FPL's return date or the FPL Cat return estimate from past injuries, plus reports FPL hasn't confirmed yet: possible injuries, return news, players reported fit.
Injury changes
GET /injuries/changes
What changed since your last call: flags set and removed, new reports, return news. Each item has a stable id and ready-to-show text, for alerts and notifications.
The next gameweek's projections are free for everyone without a key: the public API. The partner API is a superset of it.
Quick start
- Base URL:
https://fplcat.com/api/v1/partner - Every request sends your key:
Authorization: Bearer fplcat_live_…. Keys in query strings aren't accepted. - You create and revoke keys yourself on the API keys page (up to 2 at a time, e.g. production and testing). A key is shown once; we store only its hash.
- Server to server only: no CORS headers, so never put a key in a web page or a mobile app.
- Building with an AI coding tool (Claude Code, Codex, Cursor, Lovable)? Point it at https://fplcat.com/developers/api.md: the whole API in one Markdown file. The keys page has a ready prompt.
- OpenAPI 3.1 spec, to generate a client or tool definitions for your agent: https://fplcat.com/api/v1/partner/openapi.json
curl -H "Authorization: Bearer $FPLCAT_KEY" https://fplcat.com/api/v1/partner/projections
curl -H "Authorization: Bearer $FPLCAT_KEY" -o projections.csv "https://fplcat.com/api/v1/partner/projections?format=csv"Projections: GET /projections
Every player in FPL (about 670), highest 6-gameweek total first. Top level: gameweeks (the 6 gameweek numbers), deadline (the first one's, UTC), computed_at and players. ?format=csv: one row per player and gameweek.
- id, name, team, position, price, status
- Per player, as in the free API: FPL's element id, short name, club, GKP/DEF/MID/FWD, £m now, FPL's availability flag.
- gameweeks[]
- One entry per gameweek, in order, for the next 6:
- gameweek, fixtures, opponents
- The gameweek, its fixture count (0 blank, 2 double) and the opponents ({team, home}).
- xp
- Projected points, the FPL Cat model's expectation, summed over a double gameweek.
- expected_minutes, play_chance
- Expected minutes; chance he plays at all, 0-1 (summed over a double, so it can pass 1).
- p_return, p_haul, p_blank
- Chances of a goal or assist, 10+ points, and 3 or fewer points (null where the model has no simulation).
- xp_q10, xp_q90
- 10th and 90th percentile of his points that gameweek: the likely range (null where there's none).
- breakdown
- Where xp comes from: expected points from appearance, goals, assists, clean_sheet, goals_conceded, saves, bonus, defensive_contribution and cards. They add up to xp, give or take rounding; in CSV, columns xp_appearance … xp_cards.
Probabilities and the range are null only where the model has no simulation: treat null as unknown, not zero.
Prediction record: GET /record
Without gw: the graded gameweeks (recorded shortly before the deadline, and finished). With ?gw=10: every player recorded for that gameweek. ?format=csv works on both. Frozen entries are never rewritten.
- xp, expected_minutes, fixtures, p_*, xp_q10, xp_q90
- The FPL Cat model's projection as frozen shortly before the deadline.
- fpl_ep_next
- FPL's own predicted points at the same moment.
- minutes, points
- What happened (null if FPL has no stats row for him that gameweek).
- price, status
- His price (£m) and FPL flag when the projection was recorded.
- computed_at, recorded_at
- When the projection was computed, and when it was recorded (UTC).
Injuries: GET /injuries
The injury list as FPL Cat shows it on FPL Injuries, most-owned first, with two additions for apps: players reported fit while FPL's flag still stands, and every field as data. Top level: gameweek (the next one), generated_at, players.
- id, name, team, position, price, ownership
- FPL's element id, short name, club, GKP/DEF/MID/FWD, £m now and FPL's selected-by percent.
- status, kind
- FPL's flag (i, d, s) and the same in words: injured, doubtful, suspended. kind unconfirmed (status a): reports say he may be injured, FPL hasn't flagged him.
- chance_of_playing, news, news_added
- FPL's chance of playing next round (0-100 or null), its news text and when FPL last changed it (UTC).
- return
- When he's likely back. source fpl: FPL's own date, with its gameweek. source estimate: the FPL Cat return estimate from past injuries like his: median gameweek, earliest and latest (the middle half of past cases), the basis and how many cases. null when there's neither.
- severity
- 1 (minor) to 5 (long-term), from how long he's likely out; null for unconfirmed reports.
- last_played_gameweek
- His last gameweek with minutes this season.
- unconfirmed.injury
- { since }: when reports that he may be injured began (players FPL lists as available).
- unconfirmed.update, .returning, .fit
- { text, reported_at }: what reporters say about a flagged player that FPL hasn't confirmed: an absence or return time, close to a return, or fit. A player reported fit stays on the list with his FPL flag; the FPL Cat model already counts him as available.
{
"gameweek": 11,
"generated_at": "2026-11-18T09:30:00.000Z",
"players": [
{
"id": 165, "name": "João Pedro", "team": "CHE", "position": "FWD", "price": 7.6, "ownership": 31.2,
"status": "i", "kind": "injured", "chance_of_playing": 0,
"news": "Thigh injury - Unknown return date", "news_added": "2026-10-24T16:30:09.687Z",
"return": { "source": "estimate", "gameweek": 17, "earliest": 14, "latest": 21, "gameweeks_missed": 6,
"basis": "injuries with no return date, out 3-5 gameweeks already", "cases": 79 },
"severity": 4, "last_played_gameweek": 7,
"unconfirmed": { "injury": null, "update": null, "returning": null, "fit": null }
}
]
}Injury changes: GET /injuries/changes
What changed since ?since= (unix seconds or ISO 8601, e.g. 2026-11-18T09:00:00Z), up to 14 days back, newest first; without since, the whole 14 days. Store the newest at you've handled and pass it next time; skip ids you've seen.
- id
- Stable id: skip changes you've already handled.
- kind
- flagged (FPL flags him injured, doubtful or suspended), cleared (FPL removes the flag), reported (unconfirmed injury report), update, returning, recovered (unconfirmed news about a flagged player's absence, return or fitness).
- confirmed
- true for FPL's own flag changes (flagged, cleared); false for reports FPL hasn't confirmed.
- at, player
- When it happened (UTC) and { id, name, team }.
- title, description
- One line and a short paragraph, ready to show; unconfirmed items say so.
{
"since": "2026-11-17T09:00:00.000Z",
"generated_at": "2026-11-18T09:30:00.000Z",
"changes": [
{
"id": "fpl-cat-return-5", "kind": "update", "confirmed": false, "at": "2026-11-18T09:20:07.000Z",
"player": { "id": 469, "name": "N.Williams", "team": "NFO" },
"title": "Reporters say: N.Williams (Nott'm Forest), ruled out of Nations League vs Portugal",
"description": "Reporters say N.Williams: ruled out of Nations League vs Portugal. FPL still lists him as doubtful (Ankle injury - 75% chance of playing) and hasn't confirmed it."
}
]
}Unconfirmed items are reports FPL hasn't confirmed: show them as reports, never as facts. Texts are FPL Cat's own summaries; they don't quote or name anyone's posts.
Freshness and polling
- Projections are recomputed in full every day at 04:45 UTC, and again whenever FPL changes a player's status, chance of playing or news. FPL is checked about every 30 minutes, every 5 minutes in the last hour before a deadline. After a deadline, the 6 gameweeks move on.
- FPL's flags change with the same checks; injury reports are checked every few minutes through the day.
- Poll every 5 to 15 minutes, and cache what you get: serve your users from your own copy, never one API call per user request.
computed_attells you whether anything changed.
Errors and limits
- Errors are JSON:
{ "error": "<what went wrong and what to do>" }. - 400 a bad parameter; 401 a missing or unknown key; 403 a revoked key, or access revoked or ended (the message says which); 404 a gameweek that isn't graded.
- 429 over the safety cap of 2,000 requests per key per UTC day for a Pro key (5,000 for an organisation's), with
Retry-After. Fair use has no request limits beyond that: the cap only stops runaway retry loops. - 503 before the season's first model run, or a temporary problem: retry with backoff and keep your cached copy.
Attribution and versions
- Wherever the numbers, or insights built on them, are published: “Projections: FPL Cat model” with a link to fplcat.com (the condition above; an organisation's licence sets out the rest).
- This is v1: fields may be added, never renamed or removed. A breaking change would come as /api/v2 with notice.
- FPL Cat licenses only the FPL Cat model's own outputs. Player names, prices and statuses are FPL's data, as in any FPL tool. FPL Cat is an independent fan project, not affiliated with the Premier League.
Building for an organisation?
A Pro key covers your own models, scripts and apps. For a product run by a company or a team, the API is licensed per organisation: email [email protected] with what you're building.