BetSolutions
BetSolutions provides a casino and gaming platform API offering a two-way HTTP API with JSON data format for implementing requests and responses for slots, single and multiplayer games, and other casino platform services. The platform supports transfer and seamless wallet integration modes, slot campaigns with freespins, table games, provably fair games, poker, and third-party sportsbook integrations. Authentication uses SHA-256 hash-based signing with merchant secret keys.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles BetSolutions the way a machine reads it — 92 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — BetSolutions scores 51.5/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile BetSolutions
Each block below is one kind of artifact we hold for BetSolutions. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BetSolutions Player API
Player information and data retrieval endpoints including player profile details, rake data by date range, and game list retrieval with product metadata.
BetSolutions Slots API
Slot game integration and campaign management including freespin campaign creation, deactivation, configuration retrieval, and player assignment for promotional campaigns.
BetSolutions Table Games API
Multiplayer table game integration supporting Backgammon, Bura, Okey, Domino, and Seka. Includes tournament management with types and statuses, and achievement systems for playe...
BetSolutions Provably Fair Games API
Provably fair game integration for Zeppelin, High Low, Dice, Mines, and Plinko. Provides jackpot history, multiplier history, and freebet creation for provably fair game mechanics.
BetSolutions Third-Party Integration API
Third-party sportsbook integration starting with BCBetting, providing bet retrieval, bonus management, and player-specific bonus operations.
BetSolutions Player API
Player information and game data retrieval
BetSolutions Transfer Wallet API
BetSolutions-managed wallet operations for transfer mode integration
Scroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Betsolutions Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Betsolutions Finops
FINOPSFeatures 11
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Transfer Wallet Mode
BetSolutions-managed wallet with deposit, withdraw, and balance operations for casino operators.
Seamless Wallet Mode
Operator-side wallet integration where BetSolutions calls the operator's server for bet, win, and balance operations.
SHA-256 Authentication
Secure request signing using SHA-256 hash algorithm with merchant secret keys and pipe-separated parameter concatenation.
Slot Games
Slot game integration with freespin campaign management, player assignment, and campaign configuration.
Table Games
Multiplayer table games including Backgammon, Bura, Okey, Domino, and Seka with tournament support.
Provably Fair Games
Cryptographically verifiable games including Zeppelin, High Low, Dice, Mines, and Plinko.
Poker
Poker integration with jackpot tracking and daily financial reporting.
Third-Party Sportsbook
Integration with BCBetting sportsbook platform for bet and bonus management.
SDK Packages
Official SDK packages available for .NET (NuGet), PHP (Composer), and Java (JAR) platforms.
Multi-Language Support
API supports 11 languages for international casino operator deployments.
Multi-Currency Support
ISO 4217 currency codes for international payment processing.
Scroll within the panel for all 11 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
BetSolutions API Rules
SPECTRALBetSolutions API Rules
SPECTRALJSON Schema 24
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AuthResponse
JSON SCHEMABalanceRequest
JSON SCHEMABalanceResponse
JSON SCHEMADepositRequest
JSON SCHEMAErrorResponse
JSON SCHEMAGame
JSON SCHEMAGameListRequest
JSON SCHEMAGameListResponse
JSON SCHEMAPlayerInfoRequest
JSON SCHEMAPlayerInfoResponse
JSON SCHEMAWalletTransactionResponse
JSON SCHEMAWithdrawRequest
JSON SCHEMAAuthResponse
JSON SCHEMABalanceRequest
JSON SCHEMABalanceResponse
JSON SCHEMADepositRequest
JSON SCHEMAErrorResponse
JSON SCHEMAGameListRequest
JSON SCHEMAGameListResponse
JSON SCHEMAGame
JSON SCHEMAPlayerInfoRequest
JSON SCHEMAPlayerInfoResponse
JSON SCHEMAWalletTransactionResponse
JSON SCHEMAWithdrawRequest
JSON SCHEMAScroll within the panel for all 24 ·
JSON Structure 13
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Betsolutions Structure
JSON STRUCTUREWallet Api Auth Response Structure
JSON STRUCTUREWallet Api Balance Request Structure
JSON STRUCTUREWallet Api Balance Response Structure
JSON STRUCTUREWallet Api Deposit Request Structure
JSON STRUCTUREWallet Api Error Response Structure
JSON STRUCTUREWallet Api Game List Request Structure
JSON STRUCTUREWallet Api Game List Response Structure
JSON STRUCTUREWallet Api Game Structure
JSON STRUCTUREWallet Api Player Info Request Structure
JSON STRUCTUREWallet Api Player Info Response Structure
JSON STRUCTUREWallet Api Wallet Transaction Response Structure
JSON STRUCTUREWallet Api Withdraw Request Structure
JSON STRUCTUREScroll within the panel for all 13 ·
Examples 18
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Wallet Api Game Example
EXAMPLEScroll within the panel for all 18 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Casino Platform Integration
Online casino operators integrate BetSolutions APIs to offer slots, table games, and card games to players.
Wallet Integration
Casino operators choose transfer or seamless wallet mode to manage player funds and game transactions.
Freespin Campaigns
Marketing teams create and manage freespin slot campaigns to acquire and retain players.
Tournament Management
Operators run tournaments for multiplayer table games with configurable types and prize structures.
Provably Fair Gaming
Platforms offering cryptographically verifiable game results using BetSolutions' provably fair API.
Sportsbook Integration
Operators add sports betting capabilities through the BCBetting third-party integration.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
BCBetting
Third-party sportsbook integration providing sports betting functionality for casino operators.
NuGet Package Manager
.NET SDK available via NuGet for easy integration in .NET casino platform backends.
Composer Package Manager
PHP SDK available via Composer for PHP-based casino platform implementations.
Java JAR
Java SDK available as a JAR package for Java-based casino platform implementations.
Resources
Every other property we hold for BetSolutions — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/betsolutions · machine-readable index on apis.io