Toolkit v6 & SDK v7: Migrating to REST API

We’re excited to announce the release of Toolkit v6.0.0 and SDK v7.0.0!

These major updates bring a significant architectural change: we’re migrating from GraphQL feed to REST API for improved performance and reliability.

What’s New

Toolkit v6.0.0:

New Feed REST API utilities for fetching games and conditions that replace the deprecated and removed GraphQL feed queries:
- getConditionsByGameIds - replaces Conditions query
- getConditionsState - replaces ConditionsBatch query
- getGamesByFilters - replaces Games query
- getGamesByIds - replaces Game query and Games when you need to fetch multiple games by ID
- getNavigation - replaces Navigation and NavigationSport queries
- getSports - replaces Sports query
- searchGames - new one to search games by text query
New getBetsByBettor method for v3 bets history, including preparing orders
getBetCalculation replaces the deprecated getMaxBet (it now requires user account address for accuracy and returns minBet and maxBet).
Improved typing system
Extended enum GameState
Extended enum BetStatus to include pending bet orders
Renamed and extended enum BetState → BetOrderState
Helper getBetStatus now requires BetOrderState from bet entity (in case of bets fetched from graphql feed, pass null)
Fixed typo: calcMindOdds → calcMinOdds
Added field redeemedAt to legacy bets graphql doc
Removed Data Feed graphql documents and types

SDK v7.0.0:

New useSearchGames hook for enhanced game discovery
New useBetCalculation hook replaces useMaxBet
Full integration with Toolkit v6’s REST API methods
Removed deprecated useMaxBet hook
If used tanstack/query keys of sdk hooks, they are changed (primarily, because there was a graphql url in the key, now it’s chain id)
useBets is prepared to be used with REST API, that supports order history including preparing orders

To ensure a smooth transition, please follow our comprehensive migration guides:

These guides cover all breaking changes and provide step-by-step instructions for updating your integration.

If you encounter any issues during migration or have questions, reach out to us on Telegram.