Skip to Content
Developer HubAPIGraph APIOverview

The Graph API

Azuro Protocol uses The Graph service to index and organize data from its smart contracts, making it efficient and intuitive to query blockchain data.

Overview

The Graph API is a critical component of the Azuro Protocol ecosystem, providing access to historical data, bet information, game details, and current odds. In V3, Azuro uses multiple subgraphs to organize different types of data:

  1. Client Subgraphs - For bet history and transaction-related data
  2. Data-Feed Subgraphs deprecated - For current odds, game information, and condition states. Use the Backend API instead.
⚠️

IMPORTANT: All feed data (games, conditions, outcomes with current odds) should now be fetched from the Backend API. The client API graph should only be used for bet history and other transaction-related data. Never query the API graph for feed data as it no longer contains this information.

Data-feed REST API Swagger 

Client Subgraphs

Client subgraphs contain bet history and transaction-related data. In V3, they include new V3_* entities that unify prematch and live bets.

Development Endpoints

Production Endpoints

Data-Feed Subgraphs deprecated

Data-feed subgraphs contain current odds, game information, and condition states. In V3, all feed data was moved to these subgraphs.

🚨

IMPORTANT: The data-feed subgraphs are deprecated and should no longer be used for querying feed data. Existing apps should migrate to the data-feed Backend API instead.

Data-feed REST API Swagger 

Development Endpoints

Production Endpoints

Last updated on