Skip to content

Primary indexed operator

Operators

B2C casinos and sportsbooks indexed by license issuer, payment rail, provider stack, and geography. Every other dataset is derived from observations attached to operator profiles — operators are the data spine of the iGaming Finder API.

API reference → Request access →

What's inside an operator profile

License issuers

Active gambling licenses with issuer, jurisdiction, status, and last-seen date.

Provider stack

Game studios observed on the lobby — counts, categories, vertical mix.

Payment methods

Deposit and withdrawal rails observed on the operator's payment page.

Geo coverage

Inferred geography from language selectors, currency support, and hreflang.

Lobby snapshots

Periodic snapshots of available games and new-game rotation signals.

Change feed

Events when licenses, payment methods, or providers appear / disappear.

API surface

GET  /api/v1/igaming/companies/search             discovery faceted by license, payment, provider, geo; returns company_ref
GET  /api/v1/igaming/companies/resolve            authoritative profile by company_ref or signal (domain, name, license)
GET  /api/v1/igaming/companies/:company_ref/people  decision-maker contacts for a resolved Company

Base URL on api.igamingfinder.com. Authentication via X-API-Key header.

Derived datasets and API use cases

Game Providers

Studio footprints across the operator universe.

View dataset →

Affiliates

Affiliate-program intel from operator-side observations.

View dataset →

iGaming License & Domain Compliance API

License and domain verdict workflow for compliance review queues.

View API use case →

Start with the operator universe

Browse the API or request an integration kickoff with sample queries for your ICP.

Request access →