GenderAPI
Change language22
Sign inGet started
Menu

Error reference

Handle API errors with confidence

Identify failed GenderAPI requests by their stable errno value, then take the right corrective action.

Check firststatus: falseerrnoerrmsg

Response contract

Read the error object

When a request fails, the JSON response returns status as false. Use the numericerrno for application logic and keep errmsg for logs or human-readable diagnostics.

JSON · example error
{
  "status": false,
  "errno": 94,
  "errmsg": "invalid or missing key"
}
Implementation rule: Branch on errno, not the exact wording of errmsg. This keeps your integration predictable if explanatory text changes later.

Complete reference

GenderAPI error codes

The following values match the current public GenderAPI documentation. Correct the cause before repeating a request.

errno50
access denied

The request came from an unauthorized IP address or referrer.

Review the access restrictions assigned to the API key.
errno90
invalid country code

The country value is not a supported ISO 3166-1 alpha-2 code.

Validate and normalize the country code before retrying.
errno91
name not set || email not set || username not set

The request is missing its required name, email or username parameter.

Add the required input for the endpoint being called.
errno92
too many names || too many emails || too many usernames

The request exceeds the batch limit: 100 names, 50 emails or 50 usernames.

Split the input into smaller batches and submit them separately.
errno93
query limit reached

The API key has no credits remaining.

Pause lookup jobs and replenish the account balance.
errno94
invalid or missing key

The API key is missing or cannot be found.

Check credential injection and use a valid server-side key.
errno99
API key has expired

The package associated with the API key has expired.

Renew the package before sending another lookup.

Handling guidance

Fail safely and avoid blind retries

01

Validate first

Reject missing inputs, invalid country codes and oversized batches before they reach the API.

02

Protect credentials

Keep API keys on the server and redact them from application logs, browser output and support screenshots.

03

Retry selectively

These errors require correction or account action. Repeating the same request unchanged will not resolve them.

TypeScript · response guard
type GenderApiError = {
  status: false;
  errno: number;
  errmsg: string;
};

if (response.status === false) {
  handleGenderApiError(response.errno, response.errmsg);
}

Keep diagnostic details private

Log the error number with an internal request identifier, but never include the API key. Show users a concise, actionable message instead of exposing raw credentials or internal request data.

Documentation complete

Continue building with GenderAPI

Usage & quotaMonitor available credits →PricingCompare credit packages →