How to fetch markets by a particular sport?

[druspencer]

Originally asked by @GitBolt in #116

I'm not sure if I could find about it in the documentaiton. But I want to be able to fetch all open markets for a particular sport, is there a list of all sports that are on the protocol? How do we fetch/filter them? Would appreciate a small code example in JS/TS.

Thanks!

[druspencer]

Thanks for the Q!

So the protocol is agnostic to sport/event/competition, it has no concept of these. The only thing that would link it to an event is the eventPk on the market.

The eventPk is a concept that will eventually link to the protocol events service - this will contain the information you require - however the event service is not yet in use by any operators. We will be working with them to get this up and running soon, with a full batch of docs and examples to help you out.

For now, your best solution is to check out the BetDEX API #87 this returns a list of all of the markets that BetDEX are offering, it's a simple JSON format so a little formatting should give you all the info you need about currently live and recently settled markets.

Once the event service is in use we'll drop a post and I'll update this Q&A with a more sustainable answer for you.

[GitBolt]

Hey Dru. I'm using events from BetDex API now, however, why is it that using getMarketPrices returns no data in a lot of cases? For example, picking one of the address: AsMXPBCxWZSTjEXLMJUCRKcrXnzVRFH9R4u9Ka54d6cD.
This is returned in the BetDex API for Cricket but fetching marketPrices for it returns nothing. Is it possible to filter the ones that will return nothing before-hand? Because fetching marketPrices individually for each event is time consuming

[GitBolt]

@druspencer in case you missed ^

[druspencer]

Hey @GitBolt sorry for missing this,

getMarketPrices is indeed time consuming, it is not best suited to market analysis at scale. Additionally, we can't really do much about altering the basic BetDEX API.

The best approach is to, instead of using getMarketPrices - which relies on fetching unmatched orders to then calculate prices to then get the market matching pools (old endpoint we should deprecate this or refactor) - to instead query for the market matching pools directly. This query is relatively new compared to getMarketPrices, and gives you everything you need to understand the current price action on a market.

There's an example of it in use in the SDK - https://github.com/MonacoProtocol/sdk/blob/main/examples/cli/src/markets/get_market_matching_pools.ts

If there's no prices your response should be pretty fast as the query furst checks publicKeys and if there are none, it's job is done. If there are prices then you have everything you need to know to form a picture of the market - prices for/against, liquidity on prices, trades amounts on prices.

We're working on making this much easier, and teams such as shyft are also working on abstracting a lot of the data work away into graphQL calls - https://x.com/Shyft_to/status/1726949275723301242?s=20 - so there's potentially a huge unlock there for everyone

[GitBolt]

Correct me if I'm wrong, but it means I should directly run getAllMarketMatchingPools and if returns success, then I should run getMarketPrices?

[druspencer]

Better to use getAllMarketMatchingPools instead of getMarketPrices for a more timely response