Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ticktock.bet/llms.txt

Use this file to discover all available pages before exploring further.

​
Tenant API key

Every REST and WebSocket call carries a tenant API key issued from the Client Portal. The key is scoped — what fields you see depends on which scopes are attached.

​
REST

GET /cs2/v1/matches HTTP/1.1
Host: ticktock.bet
X-API-Key: <your-key>
Accept: application/json

​
WebSocket

Browsers can’t set custom headers on the WS upgrade, so the key rides as a query parameter: 
wss://ticktock.bet/cs2/v1/stream?api_key=<your-key>

​
AMQP

Provisioned per tenant on request — see the Messaging Feed page. 
amqp://op-<slug>:<password>@mq.ticktock.bet:5672/<slug>

​
Verify your key

The first call to make on any new key: 
curl -H "X-API-Key: <key>" https://ticktock.bet/v1/whoami

{
  "data": {
    "tenant_id": "…",
    "name": "Acme Sportsbook",
    "scopes": ["cs2:matches:list", "cs2:matches:read", "cs2:markets:read", "cs2:markets:settlements", "cs2:stream:matches", "cs2:stream:markets"],
    "sport_allowlist": ["cs2"],
    "rate_limit_rpm": 600
  }
}
If the scope list is shorter than expected, contact your account manager — your key may have been issued with a narrower bundle than your contract calls for.

​
Sport allowlist

Each key declares which sport namespaces it can access. Today only cs2. When future sports launch (Dota 2, soccer, …) at /{sport}/v1/*, only keys with that sport in their sport_allowlist reach those endpoints.

​
Error responses

StatusMeaning
401Missing X-API-Key header (REST) or api_key query param (WS)
403Key invalid, deactivated, lacks the required scope, or sport not in sport_allowlist
404Resource not found
406Accept header negotiation failed (neither JSON nor XML accepted)
429Rate limit exceeded
Error body (JSON): 
{ "detail": "Required scope 'cs2:markets:settlements' is not granted to this API key. Contact your account manager to extend the key's scopes." }

​
Rate limiting

Default 600 req/min per tenant key (configurable per contract). WebSocket connections aren’t rate-limited — the server still applies fairness on a per-tenant basis. When exceeded: 
HTTP/1.1 429 Too Many Requests
Retry-After: 30

​
Key rotation

Rotate from the Client Portal. Two modes:
  • Rotate — issue a fresh secret, keep the same scopes. Old key invalidated immediately.
  • Revoke — disable the key. No replacement issued.
Either way, the change takes effect within a second across all running services — no propagation delay.
Last modified on May 10, 2026