Error format, status codes, and troubleshooting guide.
All errors follow a consistent JSON format:
| Code | Meaning | Common Cause |
|---|---|---|
| 200 | Success | Request completed successfully |
| 400 | Bad Request | Invalid request body or missing required fields |
| 401 | Unauthorized | Missing or invalid API key |
| 403 | Forbidden | Insufficient credits or subscription expired |
| 404 | Not Found | Resource does not exist |
| 409 | Conflict | Resource already exists (e.g., duplicate keyword) |
| 500 | Internal Error | Server-side issue. Contact support if persistent. |
401 Unauthorized
Verify your API key is correct and not revoked. Ensure the Authorization header follows the format: Bearer YOUR_KEY
403 Forbidden
Check your credit balance via GET /usage. Verify your subscription is active.
404 Not Found
Ensure the resource ID is correct and belongs to your account. Check the endpoint path for typos.
409 Conflict
The resource you are trying to create already exists. Use GET to fetch the existing resource first, then update or delete it before creating a new one.