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.
Onboarding flow
Receive invite
Ticktock sends an email invite. Set your password, then log in to the Client Portal at
ticktock.bet/client/login.Generate an API key
In the portal: API Access → New API Key. Pick a bundle that matches your contract and optionally add extra granular scopes. Copy the key immediately — it is shown once.
Verify with /v1/whoami
First request you should make:Returns the tenant identity, granted scopes, sport allowlist, and rate limit.
Optional — request AMQP delivery
Email b2b@ticktock.bet to provision a dedicated RabbitMQ vhost + user for push delivery. Skip this if you only need REST + WebSocket.
Optional — IP allowlist
Attach an IP allowlist to your API key in the portal for additional security.
What your account manager needs
To issue your key, the account manager needs:| Field | Example |
|---|---|
| Company name | Acme Sportsbook |
| Contract bundle(s) | cs2.odds.basic + cs2.odds.scoreboard-addon |
| Owner email | integrations@acme.com (receives the portal invite) |
| Production website | https://acme.example.com |
| Rate limit | Default 600 req/min; adjust per contract |
| IP allowlist | Optional — restrict the key to specific IPs |
All credentials are self-service after the first invite — rotate keys, manage IP allowlists, and toggle market access from the Client Portal.