iGaming Platform API Comparison

A complete webhook event set and delivery SLA across the modular APIs remain unresolved.

OddsMatrix supplies connector applications for Java, C#, JavaScript, and PHP. This product-specific connector set is not a suite-wide EveryMatrix SDK.

The available limit applies to the OddsMatrix feed only. Platform-wide request quota, burst allowance and throttling policy remain unresolved.

No API versioning, deprecation or backward-compatibility commitment is established across all modules.

Events are delivered to a dedicated Kafka cluster within five seconds.

IMS supports event-driven outbound integrations and real-time player actions; webhook contracts are product- and partner-specific.

Playtech provides an SDK for its native-first Casino app and content integration. This is product-specific, not one SDK catalogue covering every Playtech product.

Partner documentation is gated; quotas are product-, environment- and contract-specific across PAM+, Marketplace, sportsbook and data APIs.

Playtech manages interface changes through gated documentation, assurance and named technical teams; deprecation windows are contract-specific.

Operational reporting and integrations are supported. Full player, wallet, compliance, CRM, bonus and audit-history portability is contract-specific.

Affilka supports S2S postbacks; webhook coverage across other modules is partner-specific.

Endpoint-specific quotas and current rate limits remain partner-specific.

API changes are partner-managed. Deprecation calendar and minimum backward-compatibility window remain unresolved.

Event Streaming sends real-time platform events to external services; it is not the same as a prebuilt Snowflake or BigQuery connector.

Back office exports plus Event Streaming, which can feed real-time event data to external services for analytics.

Event-driven architecture does not by itself establish a customer-facing webhook catalogue.

A packaged self-service SDK is not established. Integration uses the API workspace; helper libraries may be supplied during implementation.

Production rate limits are environment- and contract-specific.

Core datasets are real-time; the universal transport remains unresolved.

Data Lake exposes fully documented table views (with data dictionary and lineage) and retains full historical data; operators can pipe it to their own analytics.

A cross-product webhook catalogue and event-delivery contract remain unresolved.

A combined-portfolio SDK language list remains unresolved.

Request quotas, burst limits and throttling policies are product- and contract-specific.

No API versioning, deprecation or backward-compatibility policy is established across all acquired product lines.

Real-time product insights are available; customer event-stream contracts and schemas remain product-specific.

Michigan provides customer-specified extraction; NeoCube exposes raw iLottery data. Other modules remain contract-specific.

An Altenar webhook specification and webhook capability remain unresolved.

Comprehensive SDKs and APIs are available for cross-platform delivery; the documentation is partner-gated.

API quotas, burst limits and rate-limit policy remain unresolved.

API versioning, deprecation and schema-stability policy remain unresolved.

Real-time internal product analytics and CRM triggers do not establish an operator-accessible external data stream.

Auditor-ready regulatory exports, open APIs, BI dashboards and configurable reporting are available. Complete player-level bulk export, formats, schemas, history depth and portability rights remain unresolved.

Real-time push/event delivery is part of Kambi integrations, including the Esports Push API; the exact callback inventory is partner-gated.

The Front End product is explicitly available as a Native SDK plus Embedded Web, alongside managed apps/web and custom development.

Limits are governed inside each partner integration; no universal quota applies across Turnkey, Odds Feed+, Front End and Esports APIs.

Kambi coordinates integration changes through dedicated technical and product partner managers; the formal deprecation window is contract-gated.

Real-time betting/odds data streams across the network and feeds analytics (OpenText warehouse); operator-facing streaming arrangements are per contract.

Data feeds and warehouse access are available to partners; exact formats are partner-gated.

Supported for event-driven integrations.

Partner integration SDK/tooling available.

Real-time reporting and integration feeds; raw event-stream access is contract-specific.

Yes — APIs, portal exports and reporting.

A general webhook event catalogue and delivery guarantee are not established. Wallet callbacks and transactional integration endpoints do not constitute a reusable webhook framework.

A downloadable operator SDK, package registry and supported-language matrix are not established. Ignite development tooling and partner documentation serve a different scope.

Request quotas, burst limits, concurrency allowances and throttling policy are partner-gated for Fusion/RGS APIs. Integration scale does not establish API rate limits.

Yes for game sessions, wallet events and tournament leaderboards; raw warehouse stream access is not established.

Partial — API and portal/report downloads; exact financial export formats are partner-gated.

The sports-data feed explicitly offers webhook delivery for settlement and risk events. This does not establish a universal webhook framework across every Centrivo module.

Sportsbook and casino integrations include APIs, documentation and sandboxes but no supported SDK package. A 2021 SportGenerate esports SDK belongs to a separate group-company scope and does not establish a current Digitain SDK.

Request, subscription and burst limits are partner- and contract-specific.

Sportsbook and feed products use WebSocket/push delivery; Centrivo dashboards and Paydrom reporting are real time.

APIs, feed archives and configurable reporting expose data, but complete bulk-file formats, database portability and warehouse delivery remain contract-specific.

Kafka and Segment event feeds are verified; webhook support is not.

An SDK package and supported-language matrix are not established.

Quota, throttling and burst policy remain unresolved.

API documentation is customer-gated; versioning and deprecation commitments remain unresolved.

Kafka and Segment carry a real-time player/event feed into integrated tools.

White Hat provides Kafka/Segment events, downloadable management reporting and no-charge export of all Customer Information at exit for operator-licensed PAM.

Sportsbook integrations support APIs and webhooks for backend synchronization.

No maintained client SDK is established; integration is API, WebSocket, iFrame and widget based.

Server-to-server Data API integrations use rate limiting and internal alerts at 90% of the limit. Exact quotas remain environment- and contract-specific.

The integration process and continuous release model imply managed versions; deprecation windows and compatibility guarantees remain contract-specific.

The event-driven architecture and real-time automation depend on event delivery to internal and external systems.

Partner APIs and integration documentation exist; self-service SDK access is not established.

DataX unifies low-latency player, payment, content, sportsbook and operational events.

A general webhook catalogue and delivery guarantee are not established. Real-time partner integrations and API callbacks do not establish a reusable webhook layer across Bragg products.

A general-purpose SDK is not established; integration is primarily API- and certification-led.

Request quotas, burst allowances, concurrency limits and throttling policy remain unresolved for Bragg partner APIs. Customer and content scale do not establish API rate limits.

Real-time behavioural and transaction data powers Fuze and monitoring; external stream access is contract-specific.

Yes for reporting, audit and operator analysis.

The customer webhook catalogue and event-delivery specification are unresolved.

The customer SDK language list and downloadable SDK are unresolved.

Quotas, burst limits and throttling policies are unresolved.

API versioning, deprecation and backward-compatibility policies remain unresolved.

The customer event-streaming interface, topic catalogue and delivery SLA are unresolved.

BI reports export to CSV and XLS.

Swarm provides WebSocket subscriptions and Partner API flows; a general outbound webhook framework remains unresolved.

Spring-JS-SDK is a JavaScript/AngularJS client for the Swarm API, MIT licensed on GitHub.

Swarm requires indexed queries, subscriptions and active unsubscription; the requests-per-second quota remains unresolved.

The current Swarm API guide is version 1.2.19. Numeric versioning exists; support windows and breaking-change notice periods remain unresolved.

Swarm WebSocket subscriptions push changing sportsbook, player-message and configuration data without repeated polling. This is an application stream, not an unrestricted warehouse firehose.

Operators can build custom reports and set them for automated delivery, and pull data through the platform's external APIs.

Transactional callbacks run through partner APIs for balance, bet and win requests; the complete webhook event set remains unresolved.

An SDK is not established.

Quotas are partner- and contract-specific.

A native operator data stream is not established. Real-time dashboards and provider data updates are available; Kafka-style, warehouse or event-stream delivery remains unresolved.

Report export and automated report generation are available; a separate BI data feed or API remains unresolved.

Real-time game events can trigger CRM workflows through webhooks. Callback coverage applies to that workflow, not universally across every module.

Payments explicitly provides SDKs.

Rate limits and paid-overage schedules remain unresolved.

Integration documentation is partner-gated; compatibility windows, semantic-versioning rules and breaking-change notice commitments are unresolved.

Near-real-time analytics, event triggers, alerts and message queues provide real-time data flows.