HTTP 403 on /pub/v3/bets/place after rejected bets — request account review

[tuanna050709]

Hi Cloudbet team,

Lidya from support redirected me here for technical assistance with my Trading API account.

Problem

Every call to POST /pub/v3/bets/place returns HTTP 403 Forbidden (no JSON body, looks like a Cloudflare-level block). The same API key works fine for read endpoints — GET /pub/v1/account/currencies/USDT/balance returns 200 with the correct balance.

Root cause (my side)

I had a config bug in my betting bot: stakes were calculated as ~0.16–0.20 USDT each (instead of the intended 1.00 USDT). On 2026-05-03 between 07:19–07:36 UTC, the bot sent 12 bet placement requests, all of which were almost certainly rejected with STAKE_BELOW_MIN. After those 12 rejections (100% rejection rate), every subsequent /pub/v3/bets/place request returns 403.

I'm aware of the documented behavior:

"If the bet rejection rate on the betting API is too high (>75–80% on last 100 bets), your account will be flagged for abusive behavior."

That seems to match what happened to my account.

What I've fixed

• Stake is now flat 1.00 USDT per bet
• Added response-body logging so I'll see and handle STAKE_BELOW_MIN, STAKE_ABOVE_MAX, LIABILITY_LIMIT_EXCEEDED properly instead of blindly retrying
• Bot is stopped until the account is unflagged — no further requests will be sent

Account info

• Account email: tuanhoadat@gmail.com
• Funding: 35.65 USDT (deposited, KYC complete)
• Server IP: 159.89.202.50 (Singapore)
• API key: read endpoints OK, trading endpoint 403

Questions

1. Can you review and unflag my account? The 100% rejection rate was a one-time bug, not abusive intent.
2. What is the minimum stake for USDT on /pub/v3/bets/place? (so I can validate before sending)
3. Does the Trading API require IP whitelisting? I saw earlier discussions mentioning it.

Thanks for your help!