Troubleshooting
Fixing 401 and 403 errors
Authentication and authorization errors explained.
401 Unauthorized
A 401 means your request is missing authentication or the credentials are invalid.
Common causes
- Missing API key header
```bash # Wrong — no auth header curl -X POST https://predax.io/api/v1/check/ip \ -H "Content-Type: application/json" -d '{"ip": "8.8.8.8"}'
# Correct curl -X POST https://predax.io/api/v1/check/ip \ -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" \ -d '{"ip": "8.8.8.8"}' ```
- Typo in the API key — copy it again from Dashboard → API Keys
- Expired or revoked key — check if the key still appears as active in your dashboard
- Wrong header name — must be exactly
X-API-Key(case-sensitive)
403 Forbidden
A 403 means your key is valid but you don't have permission for this action.
Common causes
- Plan limit reached — your monthly quota may be exhausted. Check Dashboard → Stats
- Endpoint not available on your plan — some features require a paid plan
- IP allowlist — if you've configured an IP allowlist, the request may be coming from an unlisted IP
Still stuck?
- Check the Audit Log for failed authentication events
- Try generating a new API key
- Contact support with the full error response
