Get your API key
Sign up at igamingfinder.com and navigate to Account > API Keys. Copy your key -- it starts with client_.
$ help --topic=tipYour API key is shown once on creation. Store it securely.
Make your first request
Verify your key works by checking your account. Paste your key into the X-API-Key field (no Bearer prefix — just the raw client_… value) and hit Send:
GET /account
COST 0 credits / request
Returns your current plan, monthly credit quota, used and reserved credits, and available balance. The cheapest way to confirm your key works.
/api/v1/igaming/account
Authorization
Example response200
{
"success": true,
"data": {
"plan": "starter",
"credits_granted": 2500,
"credits_used": 0,
"credits_reserved": 0,
"available_credits": 2500
}
}
Search operators
Find licensed operators by jurisdiction, payment method, or game provider. Tweak the filters and Send to try queries live:
GET /domains
COST 0 credits / request
Filter operators by jurisdiction, payment category, game provider, and more. See the full filter reference in /docs/filters.
/api/v1/igaming/domains
Authorization
Query
License jurisdiction (mga, ukgc, curacao, anjouan)
Payment category (card, crypto, ewallet, bank_transfer, open_banking, local_apm)
Enrich a domain
Trigger a deep enrichment run to extract payments, providers, geos, and affiliates:
POST /enrichments
COST 10 credits (0 if cached)
Start a domain enrichment run. Returns cached data if a recent enrichment exists, otherwise begins a new run and returns a poll URL.
/api/v1/igaming/enrichments
Authorization
Query
Domain to enrich (no scheme, no path)
Enrichment strategy
$ help --topic=infoEnrichment costs <!-- cost: enrich_domain --> and takes 30-120 seconds. Poll the returnedpoll_urlfor status.
Export results
Export your filtered dataset as CSV or JSONL:
POST /exports
COST Variable (based on result count)
Queue an export job. Pick CSV or JSONL and a filter set. Returns an export id that you poll until ready.
/api/v1/igaming/exports
Authorization
Query
csv | jsonl
$ help --topic=warningNever expose your API key in client-side code or public repositories.
Next steps
- Authentication -- API key details and rotation
- API Reference -- Full endpoint documentation
- CLI Reference -- Terminal-first workflows
- MCP Setup -- Connect to Claude Desktop or Cursor
- Filters -- Advanced domain filtering