Quota overview
Check capacity before processing
Use the remaining-credit endpoint from monitoring jobs, internal dashboards or batch workflows. It returns a compact response without performing a gender lookup.
Remaining-credit endpoint
Retrieve quota information
Append your API key as the key query parameter. Keep the request server-side so the credential is not exposed to visitors.
https://api.genderapi.io/api/remaining?key=YOUR_API_KEYcurl "https://api.genderapi.io/api/remaining?key=YOUR_API_KEY"Example response
Balance and expiration
{
"status": true,
"remaining": 9443,
"expiresAt": 1752651601
}Response fields
| Field | Type | Description |
|---|---|---|
status | boolean | true when the request succeeds and the API key is valid. |
remaining | integer | Number of API credits currently available. |
expiresAt | integer | Package expiration expressed as a UNIX timestamp in seconds. |
Operational guidance
Build quota monitoring that acts early
Show current capacity
Display the balance in an internal dashboard for operations and support teams.
Set warning thresholds
Alert before the balance reaches zero, allowing time to replenish credits.
Protect bulk workflows
Compare available credits with a planned batch size before starting the job.
Use thresholds that fit your traffic rather than one universal number.
- HealthyMore than 20% remaining
- Warning10–20% remaining
- CriticalBelow 10% remaining
Plan for quota exhaustion
Do not wait for an API error to discover a depleted balance. Monitor on a sensible schedule, avoid checking before every individual lookup, and define how your application should pause or retry work.
Next reference