Get your API key

Sign up at igamingfinder.com and navigate to Account > API Keys. Copy your key -- it starts with client_.

$ help --topic=tip
Your 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, granted credits, used and reserved credits, and available balance. The cheapest way to confirm your key works.

GET /v1/account
Authorization
string
Example response200 
{
  "success": true,
  "data": {
    "plan": "starter",
    "credits_granted": 2500,
    "credits_used": 0,
    "credits_reserved": 0,
    "available_credits": 2500
  }
}

A Company is any operator, supplier, studio, or PSP. Before paying for rows, run the free preview to see how many Companies match and what it would cost. Tweak the filters and Send to try queries live:

GET /companies/search/preview

COST 0 credits / request

Free anti-surprise preview — total match count, counts per filter value, and cost estimates. No charge. See the full filter reference in /docs/filters.

GET /v1/companies/search/preview
Authorization
string
Query
string

Free-text query

string

License jurisdiction (mga, ukgc, curacao, anjouan)

string

Payment category (card, crypto, ewallet, bank_transfer, open_banking, local_apm)

When matches exist, the response includes a ready next_action.href. It preserves the preview filters, starts with at most 10 rows, and carries max_credits as the hard spending ceiling:

bash 
NEXT=$(curl -sG "https://api.igamingfinder.com/v1/companies/search/preview" \
  -H "X-API-Key: igf_demo_9457cf242d0c43404fb69b8273d7f4371716682a12c74e3c3274fd8957ebeae7" \
  --data-urlencode "jurisdiction=anjouan" \
  --data-urlencode "payment_category=crypto" | jq -r '.data.next_action.href')

[ "$NEXT" != "null" ] && curl "https://api.igamingfinder.com$NEXT" \
  -H "X-API-Key: igf_demo_9457cf242d0c43404fb69b8273d7f4371716682a12c74e3c3274fd8957ebeae7" \
  -H "Idempotency-Key: $(uuidgen)"

Pull ranked Company rows

$ help --topic=info
The preview above is free and uncharged — it returns the match count, counts per filter value, and a per-page_size cost estimate. Always size a query with /search/preview before pulling paid rows.

Happy with the preview? Pull the paid ranked rows. You are charged per row returned, capped by max_credits. Each row carries a stable company_ref you can pass to resolve for the full profile:

GET /companies/search

COST 1 credit / result returned

Paid ranked discovery rows — Companies with categories and counts. Charged per row returned, guarded by max_credits.

GET /v1/companies/search
Authorization
string
Query
string
string
string
integer

Rows per page (max 100). Charged per row returned.

integer

Hard cost ceiling for this pull.

Resolve a Company profile

Already know an identifier — a company_ref, license number, legal entity, or name? Resolve it straight to the authoritative nested profile (licenses, domains, payment methods, content suppliers):

GET /companies/resolve

COST 3 credits / profile returned

Resolve a name, license number, legal entity, or opaque company_ref to the Company profile. Charged per profile returned.

GET /v1/companies/resolve
Authorization
string
Query
string

Casino URL or host

integer

Hard cost ceiling. Rejected (402) before any data is returned if exceeded.

Export results

Export your filtered Domain dataset as CSV or JSON. JSON is one array. A non-empty CSV contains domain_normalized, company_name, status, and last_enriched_at; an empty CSV result currently produces a zero-byte file. fields[] affects JSON includes only. Exports stop at 10,000 rows, can complete partially when available credits run out, and expire after 24 hours.

POST /exports

COST Variable (number of results × the matching resolve price)

Start an export. Pick CSV or JSON and a filter set. Returns an export id that you poll until ready.

POST /v1/exports
Authorization
string
Query
string

csv | json

$ help --topic=warning
Never expose your API key in client-side code or public repositories.

Next steps