GET/api/v1/intelligences/detail

Get a match's intelligence

World Cup packageactivebetacoreAvailable

Description

Returns the intelligence for the given match id (suggested rate: up to 60 requests/min)

Access

Request: GET https://api.sports.csap.ai/api/v1/intelligences/detail
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: AvailableAny valid API key can call this endpoint.
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 1

Parameter	Type	required	Example	Description
ids	string	required		Several ids, comma separated, 200 at most

Example request

curl "https://api.sports.csap.ai/api/v1/intelligences/detail" \
  -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, 1000 rows, 382 ms (data cut to 2 rows)

{
  "code": 0,
  "data": [
    {
      "belong": null,
      "competition": "england-championship",
      "content": null,
      "id": 1,
      "intelligence": null,
      "kind": "injuries",
      "player_zh": null,
      "pub_time": null,
      "return_date": null,
      "source": "S13",
      "star": null,
      "status": "doubtful",
      "tag": null,
      "team": "Birmingham",
      "title": null,
      "type": null,
      "updated_at": 1793888012855,
      "player": "Marc Leonard"
    },
    {
      "belong": null,
      "competition": "england-championship",
      "content": null,
      "id": 2,
      "intelligence": null,
      "kind": "injuries",
      "player_zh": null,
      "pub_time": null,
      "return_date": "2026-11-15",
      "source": "S13",
      "star": null,
      "status": "injured",
      "tag": null,
      "team": "Blackburn",
      "title": null,
      "type": null,
      "updated_at": 1793888012860,
      "player": "Lewis Miller"
    }
  ],
  "message": "success",
  "success": true
}

Response fields 18

belongnullnullableSide: 0 none, 1 home, 2 away

competitionstringCompetitionExample: "england-championship"

contentnullnullableBody text

idintegerRecord id; paging cursor (the id parameter returns records >= this value). In match endpoints it is the platform match id (gmid)Example: 1

intelligencenullnullableIntelligence

kindstringKindExample: "injuries"

player_enstringPlayer's English nameExample: "Marc Leonard"

player_zhnullnullablePlayer's Chinese name

pub_timenullnullablePublication time

return_datestringnullableExpected return dateExample: "2026-11-15"

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

starnullnullableImportance of the intelligence (1-5), higher is more important

statusstringMatch statusExample: "doubtful"

tagnullnullableTag: 1 scoop, 2 major, 3 breaking, 4 news, 5 lineup, 6 injuries, 7 form, 8 transfers, 9 coaching change, 10 player, 11 off the pitch, 12 referee, 13 history, 14 data, 15 ranking

teamstringTeam nameExample: "Birmingham"

titlenullnullableTitle

typenullnullableType

updated_atintegerLast update time (UTC, ISO 8601; incremental sync with the time parameter goes by it)Example: 1793888012855

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