Platform
API
Definition
The technical contract through which platforms, suppliers, and PSPs exchange data and trigger actions in real time. The currency of every B2B integration in iGaming.
Why it matters
Every commercial relationship in B2B iGaming eventually becomes an API integration: studios connect to platforms via RGS APIs, PSPs connect to cashiers via payment APIs, KYC providers connect to PAM via verification APIs, sports data feeds connect to sportsbooks via odds APIs. The quality, reliability, and documentation of these APIs is a material commercial factor in supplier selection.
API design choices have downstream consequences. Studio APIs that expose richer event data enable better operator analytics and CRM. Payment APIs with good failover logic improve deposit conversion. KYC APIs with synchronous verification reduce onboarding drop-off. Conversely, legacy APIs (often XML-based and request-response only) impose costs on every operator that integrates them. Modern stacks favor JSON over HTTPS with webhook callbacks for asynchronous events, and API-first platforms market this as a differentiator against legacy competitors.
Frequently asked questions
How long does a typical supplier integration take?
A clean studio integration through an aggregator can be days. A direct studio integration is typically two to six weeks including certification per market. A new PAM integration is months. The variation depends on API maturity, certification overhead, and the operator's internal engineering capacity.
What's the difference between an API and a webhook?
An API is what one system calls to request something from another (deposit funds, fetch a game, verify a player). A webhook is what the other system calls back asynchronously to notify of an event (deposit cleared, KYC complete, game round settled). Most modern integrations use both.