What is Ticktock
Ticktock tracks live matches in real time, generates betting markets, and serves them to operators via REST, WebSocket, and AMQP — across multiple sports on one contract. Authentication, transport, status lifecycle, and settlement are identical from sport to sport; only the endpoints and market types differ. Integrate once, add sports without new plumbing.Sports
CS2
Counter-Strike 2 — round-level in-play micro-markets, stats, live WebSocket. Live.
Football
Soccer — matches, competitors, tournaments, full live lifecycle. Live (markets in development).
Dota 2
Rolling out now under
/dota2/v1/* on the same contract.Platform
The shared contract: auth, scopes, AMQP transport, lifecycle, settlement.
Start here
Quickstart
Onboard, get your API key, and make your first call.
The Feed Contract
REST + WebSocket + AMQP delivery, shared across every sport.
Authentication
One tenant key, scope- and sport-allowlist gated.
Client Portal
Self-service for API keys, AMQP credentials, and market access.
Platform overview
Core concepts
- Sport — top of the hierarchy (CS2, Soccer), served at
/{sport}/v1/*. - Category — a division under a sport: for CS2 the game itself; for football a country.
- Tournament — a competition under a category.
- Match — a single fixture (CS2 BO1/BO3/BO5, or a football match).
- Market offer — a betting proposition with decimal odds (CS2: single-outcome; football: multi-outcome).
- Settlement — market result resolution.
- Scope —
{sport}:{resource}:{action}permission token on your API key (e.g.cs2:matches:read). Decides which fields you receive. - Bundle — preset scope list at key-issuance time (
cs2.odds.basic,cs2.stats, …).
All endpoints live under one tenant API key — your account manager picks a bundle that matches your contract. Verify your scopes anytime with
GET /v1/whoami.