Live Bet Slip Tracking API
On this page
Start live tracking for SportyBet, Football.com, or Betway
Use POST /v1/track to start live match tracking and score updates for SportyBet, Football.com, and Betway bet slips. A track start costs 1 API credit, only these 3 bookmakers support tracking, and mode: ticket fails fast on a cut while mode: game tracks to the end.
POST /v1/track
{"code": "7B9A2F", "bookmaker": "sportybet",
"mode": "ticket", "label": "Friday acca",
"webhook_url": "https://example.com/hooks/mbc"}{
"id": "trk_...",
"status": "active",
"bookmaker": {"key": "sportybet", "name": "SportyBet"},
"code": "7B9A2F",
"mode": "ticket",
"label": "Friday acca",
"created_at": "...",
"updated_at": "...",
"selections": [],
"billing": {"action": "track_start", "price": 1, "credits_used": 15,
"credits_limit": 5000, "credits_reset": "2026-12-01T00:00:00Z"}
}Only SportyBet, Football.com, and Betway support tracking. Use mode: ticket to fail fast on a cut. Use mode: game to track to the end.
A cut ticket can return pending_choice. This status means the ticket waits for a ticket or game choice. The start response and the track list use the same pending_choice value.
How to read, list, and stop a track
A Manage Bet Codes track costs 1 API credit at the start and the plan's concurrent track limit applies: Developer allows 5 tracks, Scale allows 20, and Business allows 50. Read one track with GET /v1/track/{id}, stop it with DELETE /v1/track/{id}, list tracks with GET /v1/tracks, and expect 404 track_not_found for a track outside the key owner.
| Route | Purpose |
|---|---|
GET /v1/track/{id} | Read the current state. |
DELETE /v1/track/{id} | Stop the track. |
GET /v1/tracks?status=active|finished | List tracks. |
A track costs 1 credit at the start. The plan's concurrent track limit applies. A track that does not belong to the key owner returns 404 track_not_found.
How signed tracking webhooks work
Tracking webhooks send track.started, track.updated, track.finished, and track.cut events as HTTPS POST calls signed with X-MBC-Signature: sha256=<hex>. Webhooks retry 5 times with delays of 1, 5, 30, 120, and 600 seconds, time out after 10 seconds, and disable after 20 consecutive failures.
| Item | Rule |
|---|---|
| Events | track.started, track.updated, track.finished, track.cut |
| Signature | X-MBC-Signature: sha256=<hex> |
| HMAC key | The webhook secret. It shows one time. |
| Retries | 5 retries. Delays: 1, 5, 30, 120, 600 seconds. |
| Timeout | 10 seconds |
| Transport | HTTPS only. No redirects. |
| Ports | 443 and 8443 only. |
| Host checks | Reject private, loopback, and link-local hosts. |
| Disable rule | Disable after 20 consecutive failures. |
X-MBC-Signature: sha256=6f3c...