Odds Feed API Docs: 12 Questions Every Operator Must Ask
Before your team writes a line of code against an odds feed API, the documentation must answer 12 specific questions. WSGaming explains what complete odds feed API docs look like — and the gaps that cost integration time.
The Pre-Integration Documentation Checklist
Your odds feed solution documentation should answer all 12 of these questions before your developer writes a single line of code. Gaps become support tickets. Support tickets cost time. Time costs money.
Authentication (Questions 1–3)
- What authentication method is used — API key, OAuth, or mutual TLS?
- How are API keys rotated and what is the expiry policy?
- What happens to active WebSocket connections when an API key is rotated?
Market Structure (Questions 4–7)
- What is the exact JSON structure of a market discovery response, including all field names and types?
- How are Asian Handicap quarter-ball lines represented — separate market IDs or fields within a parent market?
- How are sport, league, and event IDs structured — and are they stable across the event lifetime?
- How much advance notice is given before a market becomes available pre-match?
Real-Time Updates and Settlement (Questions 8–12)
- What is the exact JSON structure of every WebSocket message type?
- How is the sequence number field used for deduplication and gap detection?
- What is the retry policy for settlement webhook delivery?
- How are voided markets communicated after initial settlement?
- How are amended settlements (result initially wrong, then corrected) handled?
Amended settlements — a result posted incorrectly and then corrected — happen regularly in live sportsbook operations. An odds feed provider without a documented amended settlement flow leaves you with no process when it occurs. Without one, you either overpay or underpay players with no audit trail.
What to Do When Docs Are Incomplete
If an Odds Feed Provider cannot answer all 12 questions in their documentation before you sign, require them to complete it as a pre-signing contractual obligation with a deadline — or do not sign. WSGaming’s odds feed solution documentation answers all 12, includes JSON schemas for every message type, and is provided in full before any contract is signed.
Key Takeaways
- Complete odds feed docs answer 12 questions across authentication, market structure, and settlement
- AH quarter-ball market representation must be explicitly documented — never assume the format
- Settlement webhook retry policy and amended settlement flows are the most commonly missing items
- Require incomplete documentation to be completed before signing — with a specific deadline
- WSGaming provides JSON schemas, OpenAPI spec, and amended settlement docs before any contract
Review WSGaming’s Complete Odds Feed Documentation
Available in full before signing — no commitment required.
Request Docs AccessView Odds Feed Solution