API Keys
Every request to the iGaming Finder API requires an API key. Create and manage keys in your Account dashboard.
Keys use the client_ prefix:
text
client_7f3a2b1c9d4e...
Passing Your Key
Two methods are supported. Use whichever fits your stack.
Header (recommended):
bash
curl -H "X-API-Key: YOUR_API_KEY" \
https://api.igamingfinder.com/api/v1/igaming/domains
Bearer token:
bash
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.igamingfinder.com/api/v1/igaming/domains
Both methods are equivalent. If both are present, X-API-Key takes precedence.
Error Responses
Missing or invalid key returns 401 Unauthorized:
json
{
"success": false,
"message": "Unauthorized",
"errors": {},
"timestamp": "2026-05-03T10:30:00Z"
}
Rate Limits and Quotas
Each plan has a monthly credit quota. When you exceed it, API returns 429 Too Many Requests:
json
{
"success": false,
"error": {
"code": "quota_exceeded",
"message": "Monthly credit quota reached",
"details": {
"quota": 1000,
"used": 1000,
"reserved": 0
}
}
}
Check your remaining credits anytime:
bash
curl -H "X-API-Key: YOUR_API_KEY" \
https://api.igamingfinder.com/api/v1/igaming/account
Credit Costs
| Operation | Cost |
|---|---|
Search domains (GET /domains) |
0 credits / request |
Get domain profile (GET /domains/:domain) |
0 credits / request |
Enrich domain (POST /enrichments) |
10 credits (0 if cached) |
| Cached enrichment result | 0 credits / request |
Create export (POST /exports) |
Variable (based on result count) |
| All status/poll endpoints | 0 credits / request |
Get account info (GET /account) |
0 credits / request |
| Lobby monitor (on-demand run) | 10 credits / run |
$ help --topic=warningNever expose your API key in client-side code, public repositories, or browser requests. Keys grant full access to your account.
Key Rotation
To rotate a compromised key:
- Go to Account > API Keys
- Create a new key
- Update your integration with the new key
- Delete the old key
All requests are logged in Account > Usage with endpoint, credits billed, and timestamp.