specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: BetSolutions
providerId: betsolutions
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Betting
  - Casinos
  - Gaming
  - Rate Limiting
description: 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.
notes: Reconcile with the operator integration runbook delivered by BetSolutions during onboarding. Do
  not invent throughput numbers.
sources:
  - https://docs.betsolutions.com/
responseCodes:
  throttled: 429
limits:
  - name: Per-operator throttle
    scope: operator/merchant
    metric: varies
    limit: 'see BetSolutions operator onboarding documentation'
    notes: Capacity scoped to the operator merchant ID; specific numbers are not public.
  - name: Seamless wallet callback rate
    scope: operator
    metric: varies
    limit: 'governed by operator infrastructure (BetSolutions calls operator endpoints in seamless mode)'
    notes: 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:
  - name: Backoff Strategy
    description: Use exponential backoff with jitter on throttled responses; honor Retry-After when present.
  - name: SHA-256 Hash Signing
    description: 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.
  - name: Mode-Dependent Capacity
    description: In transfer mode BetSolutions manages the wallet; in seamless mode the operator handles
      bet/win callbacks. Capacity tuning differs between modes.
  - name: Regulatory Constraints
    description: Operators must respect jurisdictional licensing; non-compliant traffic patterns can trigger
      shutoffs independent of API-level rate limits.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com