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.

What is Ticktock

Ticktock monitors HLTV matches in real time, tracks round-level events, generates betting market offers, and serves them to operators via REST, WebSocket, and AMQP. Stats — teams, players, tournaments, maps — come from the same API surface.

Getting Started

Onboard, get your API key, and make your first call.

Odds Feed

Round-level micro-markets with REST + WebSocket + AMQP delivery.

API Reference

Interactive endpoint documentation — try every call from the browser.

Client Portal

Self-service for API keys, AMQP credentials, and market access.

Platform overview

PropertyValue
Sport coverageCS2 (Counter-Strike 2). Additional titles roll out under their own /{sport}/v1/* namespaces.
Market scopeRound-level in-play micro-markets
Stats scopeMatches / teams / players / tournaments / maps
DeliveryREST (JSON or XML) · WebSocket · AMQP messaging feed (XML)
SettlementAutomatic, engine-driven, auditable
LatencyOdds within 1–2s of freeze; settled within 1–3s
Availability24/7 — matches tracked whenever live on HLTV

Core concepts

  • Match — a BO1/BO3/BO5 HLTV match.
  • Map — one map inside a match series.
  • Round — a single CS2 round with economy and event outcomes.
  • Market offer — single-outcome proposition with decimal odds.
  • Settlement — market result resolution at round end.
  • Scopecs2:{resource}:{action} permission token attached to 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.
Last modified on May 10, 2026