GET/api/v1/players/abilities

List player ability ratings

Advanced data packageactivebetacoreAvailable

Description

Returns all player ability ratings, with incremental updates by timestamp.

1. First full sync: page through everything with the id parameter.
2. Afterwards: fetch what changed with the time parameter (suggested frequency: once a minute).

Access

Request: GET https://api.sports.csap.ai/api/v1/players/abilities
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 3

Parameter	Type	required	Example	Description
id	integer	optional	`6917`	Records with id greater than or equal to this value, ordered by id
time	integer	optional		Records updated at or after this time (timestamp), ordered by update time
limit	integer	optional	`2`	Maximum number of rows, default 100, maximum 100

Example request

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

Try it

Example response

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

{
  "code": 0,
  "data": [
    {
      "ability": [
        {
          "name": "attacking",
          "value": 61
        },
        {
          "name": "technical",
          "value": 54
        },
        {
          "name": "tactical",
          "value": 43
        }
      ],
      "ability_detail": [],
      "comprehensive": 47,
      "id": "39369"
    },
    {
      "ability": [
        {
          "name": "attacking",
          "value": 61
        },
        {
          "name": "technical",
          "value": 54
        },
        {
          "name": "tactical",
          "value": 43
        }
      ],
      "ability_detail": [],
      "comprehensive": 47,
      "id": "38218"
    }
  ],
  "message": "success",
  "success": true
}

Response fields 4

abilityarray<object>Ability rating· 2

ability_detailarrayAbility sub-ratings

comprehensiveintegerOverall abilityExample: 47

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

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