Quickstart
Start with GET /api/v1/markets.json. The catalogue returns stable market identifiers, canonical page URLs, Markdown companions, publication status, and event metadata. Fetch a complete record at GET /api/v1/markets/{marketId}.json.
The OpenAPI document defines unique operation identifiers, typed parameters, success schemas, and a consistent error model. Market records include editorial conclusions, proof points, recorded offers with timestamps, and source URLs.
Versioning and deprecation
Version 1 is the stable public contract. Oddly Likely may add backwards-compatible fields within v1. A breaking field, operation, or meaning change will use a new versioned path such as /api/v2/; existing v1 paths will not silently change semantics.
If a version must be retired, its OpenAPI operations will be marked deprecated and this page will publish the replacement and removal date at least 90 days in advance. Once response-header control is available, deprecation notices will also use the standard Deprecation and Sunset headers.
Errors, limits, and freshness
The documented error object contains a machine-readable code, message, HTTP status, and resolution hint. The API is intended for moderate, cache-friendly reading rather than high-frequency polling. Consumers should cache catalogue responses and follow any RateLimit or Retry-After headers returned by the service.
Prices are recorded snapshots, not live quotes. Preserve each offer's checkedAt value, check the operator before relying on availability, and cite the canonical HTML page when presenting Oddly Likely analysis.
Support
For schema questions, corrections, or responsible integration concerns, use the contact page. The API does not expose account creation, wagering, payments, personalisation, webhooks, or write operations.