Gender API
Sign Up Free
Language expand_more

How should I handle API errors?

schedule Last updated: September 29, 2026
API v2 uses standard HTTP status codes and returns every error as a JSON problem-details response with a type and a descriptive message. 200 means success, 400 means the request is invalid (for example a missing or invalid API key, an invalid parameter or too many names in one call), 401 with the type "limit-exceeded" means your account has no requests left, and 404 means the endpoint does not exist. API v1 returns an errno and an errmsg field in the JSON response; errno 30 means your request limit is reached. If your requests are used up, buy a new package or wait for the monthly recharge – retrying will not help. For persistent errors, check our API documentation or contact support.

label Related Keywords

error handling HTTP status codes API errors error messages debugging troubleshooting

Was this article helpful?

Chat