# How should I handle GenderAPI error codes?

> V2 API errors use HTTP error statuses and RFC 9457 Problem Details with stable code and action fields. Read those fields rather than matching detail wording, and retain request_id for support. A successful unknown result is different from an error. Batch responses can contain item errors even with HTTP 200. A proxy may return a non-JSON error, and a lost or unreadable response does not establish that no charge occurred.

Canonical HTML: https://www.genderapi.io/frequently-asked-questions/api-error-codes

Last reviewed: 2026-09-26

## Answer

V2 API errors use HTTP error statuses and RFC 9457 Problem Details with stable code and action fields. Read those fields rather than matching detail wording, and retain request_id for support. A successful unknown result is different from an error. Batch responses can contain item errors even with HTTP 200. A proxy may return a non-JSON error, and a lost or unreadable response does not establish that no charge occurred.

## Related canonical guidance

- [Errors, limits and retries](https://www.genderapi.io/docs/v2/errors-and-retries)
- [Batch requests and partial failures](https://www.genderapi.io/docs/v2/batch)