BetSolutions · Rate Limits
Betsolutions Rate Limits
The BetSolutions integration documentation does not publish public rate limits, throttle thresholds, or rate-limit response headers. Capacity is provisioned per operator and disclosed during technical onboarding. No numeric values are asserted here.
2 Limits
Throttle: 429
BettingCasinosGamingRate Limiting
Limits
Per-operator throttle operator/merchant
see BetSolutions operator onboarding documentation
Capacity scoped to the operator merchant ID; specific numbers are not public.
Seamless wallet callback rate operator
governed by operator infrastructure (BetSolutions calls operator endpoints in seamless mode)
In seamless mode BetSolutions makes outbound calls to the operator's wallet endpoints; the operator's own infrastructure capacity becomes the binding rate limit.
Policies
Backoff Strategy
Use exponential backoff with jitter on throttled responses; honor Retry-After when present.
SHA-256 Hash Signing
Every request is signed with a SHA-256 hash using the merchant secret; signature failures can mimic throttling and should be distinguished in client logs.
Mode-Dependent Capacity
In transfer mode BetSolutions manages the wallet; in seamless mode the operator handles bet/win callbacks. Capacity tuning differs between modes.
Regulatory Constraints
Operators must respect jurisdictional licensing; non-compliant traffic patterns can trigger shutoffs independent of API-level rate limits.