Trading API access, sports coverage, sandbox funds, and automation rules

[meister47]

Hi Cloudbet API team,

We are evaluating Cloudbet as a possible API provider for a sports/esports analytics workflow, with a responsible path from read-only analysis first and, only if permitted and technically reliable, automated betting later.

Cloudbet support kindly directed us here for deeper API questions. We have read the public docs and GitHub discussions, but we want to confirm a few details before creating any account/deposit/API integration.

Questions:

1. Is Trading API access currently available for regular retail users, including users located in Russia, assuming the account passes normal Cloudbet rules and KYC requirements?
2. Is automated betting via the Trading API permitted for retail users if we respect your API limits and account rules?
3. Which sports are currently available through the Trading API, specifically: CS2, Dota 2, League of Legends, Valorant, and Tennis?
4. During the current API rebuild, should we expect website-vs-API market coverage differences? If yes, is there any public status page or recommended way to check which sports/markets are API-supported right now?
5. How can a user enable or request test funds / PLAY_EUR access for Trading API validation before using real funds?
6. What are the current practical rate limits for Feed API and Trading API usage?
7. Are min/max stake limits, rejection reasons, and bet status/reconciliation fields documented anywhere beyond the basic API docs?
8. Are there known restrictions for API usage from VPS/cloud infrastructure, Cloudflare challenge/403 behavior, geo restrictions, or IP whitelisting requirements?

Our intended use is narrow: first validate market availability, odds ingestion, order lifecycle, rejection handling, and settlement reconciliation. We are not trying to bypass any limits or compliance controls.

Thanks in advance for clarifying.