← Back to API docs

POST/api/v1/realtime/ticket

Get a WebSocket ticket (60 seconds, single use)
Realtime pushactivebetacoreAvailable

Access

Request
POST https://api.sports.csap.ai/api/v1/realtime/ticket
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 0

This endpoint takes no request parameters.

Example request

curl -X POST "https://api.sports.csap.ai/api/v1/realtime/ticket" \
  -H "X-API-Key: YOUR_API_KEY"

Try it

Example response

An example response is being added; send a request in Try it above to see a real one.

Response fields 3

expires_ininteger
ticketstringWebSocket ticket (60 seconds, single use; connect to /ws?ticket=<ticket>)
ws_urlstring

Errors

HTTPmessageWhen
401missing API key / unauthorizedNo X-API-Key, or the key is invalid or disabled
429rate limit exceeded / daily quota exceededThe key's per-minute rate or daily quota is exceeded
429server busy, retry laterThe server's concurrency slots are full (only 2 heavy requests at a time); retry after Retry-After seconds
500query errorThe query failed on the server; you may retry