Request: GET https://api.sports.csap.ai/api/v1/matches/odds/bookmakers
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 0

This endpoint takes no request parameters.

Example request

curl "https://api.sports.csap.ai/api/v1/matches/odds/bookmakers" \
  -H "X-API-Key: YOUR_API_KEY"

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

{
  "code": 0,
  "data": [],
  "message": "success",
  "success": true
}

No field reference available for this endpoint.

HTTP	message	When
401	`missing API key / unauthorized`	No X-API-Key, or the key is invalid or disabled
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