What's new in the Orbistats API
Every endpoint addition, schema change, deprecation and fix — dated, categorized and linked back to the exact resource it touches.
The four most recent changes
The full, filterable history is below.
Tennis live odds
Live in-play odds now available across all four majors.
WebSocket API — GA
Persistent streaming connection moved out of beta.
Cricket history backfilled
Ball-by-ball history now available back to 2015.
Odds schema field added
Non-breaking: added closing_line to odds responses.
Versioning
We version the API, not just the docs. Additions — new endpoints, new optional fields, new enum values — ship inside the current version and are always non-breaking. A field or behavior is only ever removed or renamed on a new version prefix, so /v1/ keeps working exactly as documented for every existing integration, even after /v2/ ships.
| Change type | Ships on | Notice given |
|---|---|---|
| Addition | Current version, immediately | Changelog entry only |
| Non-breaking fix | Current version, immediately | Changelog entry only |
| Deprecation | Current version, with warning header | 90 days minimum before removal |
| Breaking change | New version prefix only (e.g. /v2/) | Migration guide published with the new version |
Deprecation policy
When a field or endpoint is marked Deprecated below, it keeps working for a minimum 180-day overlap window. Responses that touch a deprecated field include a Deprecation and Sunset header so you can find every call site programmatically instead of hunting through code by hand.
Get notified
Pick whichever fits your workflow — all three cover the same entries you see on this page.
Every entry, dated
Filter by change type. All entries stay in the page — filtering just highlights the ones you're looking for.
Tennis live odds
Live in-play odds are now available across all four Grand Slams, alongside the existing pre-match tennis markets.
Standings tie-break ordering corrected for basketball
Head-to-head tie-break was applied after goal/point differential instead of before it for a small number of NBA divisional ties. Historical standings snapshots have been recalculated.
WebSocket API — general availability
The persistent streaming connection has moved out of beta. Rate limits are now enforced per plan (see the reference), and the beta stream-beta.orbistats.com host is deprecated in favor of stream.orbistats.com.
Lineups & events for American football
/fixtures/{fixture_id}/lineups and /events are now populated for NFL and NCAA fixtures, matching the existing football and basketball coverage.
Cricket historical data backfilled to 2015
Ball-by-ball historical match data for international and major domestic cricket competitions now extends back to the 2015 season, up from 2020 previously.
Webhook payload signing upgraded to HMAC-SHA256
All webhook payloads are now signed with HMAC-SHA256 instead of SHA1. The old signature header remains alongside the new one until Oct 30, 2026 for a smooth migration.
Odds schema — closing_line field added
Non-breaking: a closing_line field was added to odds responses, capturing the final pre-match price. Existing fields are unchanged.
fixtures.referee field deprecated
The top-level referee string on fixture responses is deprecated in favor of the structured officials array, which supports multiple officials per fixture. referee remains available until Aug 06, 2026.
Esports fixtures, live scores and standings
Esports joined the core resource model with fixtures, live scores and standings for major League of Legends and CS titles.
Pagination cursor stability fix
Cursors for /history/matches could occasionally skip a page under high write volume. Cursors are now stable across concurrent writes.
v1 launched; v0 sunset
The current /v1/ API launched with the consistent resource model documented in the reference. The legacy /v0/ endpoints were retired after a 180-day overlap window.
Common questions
What developers usually ask before wiring the changelog into their release process.
How do I get notified when the Orbistats API changes?
Subscribe to the changelog RSS feed, watch the GitHub changelog repository, or turn on changelog email alerts from your dashboard notification settings. Breaking changes are also announced at least 90 days ahead on the deprecations page.
Will a change in the changelog break my existing integration?
Not unless it's explicitly labeled Breaking. Additions, new optional fields and new endpoints are always non-breaking and ship inside the current version. Breaking changes only ever ship on a new version prefix, such as /v2/, so /v1/ keeps working during the overlap window.
How long does Orbistats support a deprecated endpoint or field?
Deprecated fields and endpoints stay available for a minimum 180-day overlap window from the date they're marked Deprecated, with usage warnings returned in the response headers so you can find and fix call sites before the sunset date.
Where can I see if an incident affected the data in a changelog entry?
Cross-check the entry date against the status and incident history page, which lists uptime and any data-quality incidents separately from planned API changes.
Related pages
Explore more of the developer platform.
Status
Live uptime and incident history.
API Reference
Every endpoint, sport by sport.
Documentation
The full developer documentation hub.
SDKs
Client libraries, versioned alongside the API.
Data Dictionary
Every field, ID and enum, kept current with each release.
Quickstart
Make your first request in five minutes.
Start free. Upgrade when you need enterprise SLAs.
Self-serve API keys for developers today — dedicated infrastructure, custom feeds and SLAs when you're ready.