API Keys
FunBypass uses API keys for authentication. Your key is passed in the request body as the clientKey field — there are no headers or bearer tokens required.
Key Types
| Prefix | Type | Description |
|---|
FUN- | Balance-based | Pay-per-solve at $0.75/1,000 solves. Balance is deducted per task. |
PKG- | Package-based | Subscription packages with daily/hourly quotas or unlimited solves. |
Getting Your API Key
- Sign up at app.funbypass.com
- Navigate to Dashboard → Settings
- Copy your API key
Keep your API key secret. Do not expose it in client-side code or public repositories.
Authentication Flow
Every API request requires your clientKey in the request body:
{
"clientKey": "FUN-your-api-key-here",
"task": { ... }
}
- Key existence — The key must be registered
- Account status — Account must not be suspended
- Package validity — For
PKG- keys, the package must be active and not expired
- Balance/Quota — Sufficient balance or remaining quota for the request
Balance-Based Keys (FUN-)
- Cost: 0.75per1,000solves(0.00075 per solve)
- Balance is deducted when a task starts processing
- If the task fails, the balance is automatically refunded
- Check your balance via the
POST /getBalance endpoint
Package-Based Keys (PKG-)
Packages come in several types:
| Type | Description |
|---|
unlimited | No solve limit during the subscription period |
daily | Fixed number of solves per day, resets daily |
hourly | Fixed number of solves per hour, resets hourly |
active, paused, or expired. Only active packages can create tasks.
Error Responses
If authentication fails, you’ll receive one of these errors:
| Error Code | Description |
|---|
ERROR_KEY_DOES_NOT_EXIST | API key not found |
ERROR_ACCOUNT_SUSPENDED | Account has been suspended |
ERROR_PACKAGE_PAUSED | Package is currently paused |
ERROR_PACKAGE_EXPIRED | Package subscription has expired |
ERROR_ZERO_BALANCE | Insufficient balance (balance-based keys) |
ERROR_RATE_LIMIT_EXCEEDED | Daily or hourly quota exceeded (package keys) |
Next Steps
