Bet Angel API / Guardian — Different refresh rates for displayed market versus other Guardian markets

[mateinone]

I'm investigating using the Bet Angel Professional API (`getMarketPrices`) to collect high-frequency market data from multiple markets simultaneously.

I've noticed a significant difference between the market displayed in the main Bet Angel window and the other markets loaded into Guardian.

**Test configuration:**
- Bet Angel Professional 1.61.1
- Six horse racing WIN markets loaded in Guardian
- Local JSON API polled every 20 ms using Python
- Two-minute tests (6,000 API requests each)
- No API errors

I ran two tests using different refresh settings:

| Market | Update setting | 20 ms setting |
|---|---:|---:|
| Market displayed in main Bet Angel window | 1,033 updates | 3,339 updates |
| Each of the other five Guardian markets | ~612 updates | ~657 updates |

These counts are based on changes to the `lastUpdated` timestamp returned by `getMarketPrices`, not necessarily actual price changes.

With the 20 ms setting, the displayed market produced approximately **28 timestamp updates per second**, while each other Guardian market produced only **5.5 per second**.

**My questions are:**

1. Does Bet Angel maintain a separate, higher-frequency data refresh for the market displayed in its main window compared with markets loaded only in Guardian?

2. When Guardian is configured to refresh at 20 ms, does this apply to each individual market, or does Guardian cycle through the markets sequentially, meaning the effective refresh interval per market increases as more markets are loaded?

3. Is there a way to obtain the same high-frequency updates for **all Guardian markets simultaneously** through the Bet Angel API, without displaying or switching between them in the main Bet Angel window?

4. Does `getMarketPrices` simply retrieve the most recently cached market data, or can requesting it cause markets to refresh?

My objective is read-only collection of market prices, available back/lay liquidity and traded volume across multiple simultaneous racing markets, including in-play.

Any clarification on how Guardian's refresh scheduling interacts with the API would be greatly appreciated.