Source health API for bookmaker odds monitoring
Read coverageStatus, lastVerifiedAt and per-quote lastUpdatedAt so your product knows which bookmaker odds are verified and current before users rely on them.
- 01
Read coverageStatus, lastVerifiedAt and a scope note per bookmaker from /api/v1/bookmakers.
- 02
Use lastUpdatedAt on every outcome to apply your own freshness cutoff.
- 03
Limited or in-review sources stay out of broad lists instead of inflating aggregate coverage.
Best fit: Teams that need to monitor bookmaker feed readiness, latency, freshness, and production rollout risk.
Developer trust
Source health API for bookmaker odds monitoring
Source health is the strongest trust signal in the product. It lets teams separate verified, limited and in-review bookmakers, and current from outdated quotes, before users depend on bookmaker odds in production.
Quotes older than the server window are left out of responses instead of being flagged stale; the freshness docs explain the window and a sensible client-side cutoff.
coverageStatusVerification state per bookmaker, for example verified_rest_live or source_limited.
lastVerifiedAtDate of the last end-to-end verification of the source.
customerNotePlain-language scope note, for example which sports or markets are covered.
lastUpdatedAtPer-outcome timestamp of the latest source observation.
{
"slug": "tipico",
"displayName": "Tipico",
"coverage": {
"countries": [
"DE"
],
"coverageStatus": "disabled_until_review",
"sourceMode": "direct",
"restAvailable": false,
"liveAvailable": false,
"lastVerifiedAt": "2026-10-01"
}
}