GET/api/v1/matches/lineup/intelligences

Lineup intelligence (injured / unavailable players)

Lineup intelligencebetabetacoreAvailable (scoped)

Description

The same data as matches/intelligences, seen from the lineup side: injuries and absences that affect who can play. Coverage is being extended.

Access

Request: GET https://api.sports.csap.ai/api/v1/matches/lineup/intelligences
Auth: Header X-API-Key: <your key> (Authorization: Bearer <key> also works; ?key= is still accepted but discouraged, because the key ends up in URLs and logs)
External keys: Available (scoped)External keys can call it, but only data inside the open scope is returned.
Rate limits: 3000 per minute · 200000 per day · Set per key (rate_per_min and quota_daily returned by /api/v1/account are authoritative; the numbers above are a trial key's). Beyond them the answer is 429. In addition, heavy requests such as whole-table snapshots and statistics lists without a match id are processed 2 at a time for the whole platform; a request that cannot get a slot receives 429 with Retry-After. Responses do not carry X-RateLimit-* headers for now. See the general guide

Request parameters 3

Parameter	Type	required	Example	Description
id	integer	optional	`5179`	Cursor: rows with id (= uid) >= this value
time	integer	optional		Incremental: rows updated at or after this Unix time (seconds)
limit	integer	optional	`2`	Maximum number of rows, default 1000, maximum 1000

Example request

curl "https://api.sports.csap.ai/api/v1/matches/lineup/intelligences?limit=2" \
  -H "X-API-Key: YOUR_API_KEY"

Try it

Example response

Real response with an external key at 09/11/2026, 14:28 UTC: HTTP 200, 2 rows, 115 ms (data cut to 2 rows)

{
  "code": 0,
  "data": [
    {
      "competition": "england-championship",
      "kind": "injuries",
      "player_zh": null,
      "return_date": null,
      "source": "S13",
      "status": "doubtful",
      "team": "Birmingham",
      "uid": 1,
      "updated_at": "2026-11-05T14:13:32.855393Z",
      "player": "Marc Leonard"
    },
    {
      "competition": "england-championship",
      "kind": "injuries",
      "player_zh": null,
      "return_date": "2026-11-15",
      "source": "S13",
      "status": "injured",
      "team": "Blackburn",
      "uid": 2,
      "updated_at": "2026-11-05T14:13:32.860344Z",
      "player": "Lewis Miller"
    }
  ],
  "message": "success",
  "success": true
}

Response fields 10

competitionstringCompetitionExample: "england-championship"

kindstringKindExample: "injuries"

player_enstringPlayer's English nameExample: "Marc Leonard"

player_zhnullnullablePlayer's Chinese name

return_datestringnullableExpected return dateExample: "2026-11-15"

sourcestringSource code (S1, S2…)Example: "S13"

statusstringMatch statusExample: "doubtful"

teamstringTeam nameExample: "Birmingham"

uidintegerUnique cursor id of the recordExample: 1

updated_atstringLast update time (UTC, ISO 8601; incremental sync with the time parameter goes by it)Example: "2026-11-05T14:13:32.855393Z"

Errors

HTTP	message	When
401	`missing API key / unauthorized`	No X-API-Key, or the key is invalid or disabled
400	`bad param …`	Malformed parameter (e.g. id is neither a number nor u<uid>)
301	`match merged into <gmid>`	Queried by an old match id that has been merged into a new gmid: Location points to the new address and the body carries moved_to
404	`not found`	The match / team / competition does not exist, or is outside what this key can see (external keys see only matches inside the open coverage)
429	`rate limit exceeded / daily quota exceeded`	The key's per-minute rate or daily quota is exceeded
429	`server busy, retry later`	The server's concurrency slots are full (only 2 heavy requests at a time); retry after Retry-After seconds
500	`query error`	The query failed on the server; you may retry