# How are API versions and breaking changes handled?

> Use V2 for new integrations and keep existing V1 clients on their documented paths until you choose to migrate them. Both versions share API keys and credits, but use different request fields, response structures and error formats. Follow the migration guide, test successful, unknown and error outcomes, and update your parser before switching endpoints. The V1 reference remains available for existing integrations.

Canonical HTML: https://www.genderapi.io/frequently-asked-questions/api-versioning-and-breaking-changes

Last reviewed: 2026-09-26

## Answer

Use V2 for new integrations and keep existing V1 clients on their documented paths until you choose to migrate them. Both versions share API keys and credits, but use different request fields, response structures and error formats. Follow the migration guide, test successful, unknown and error outcomes, and update your parser before switching endpoints. The V1 reference remains available for existing integrations.

## Related canonical guidance

- [V1 to V2 migration](https://www.genderapi.io/docs/v2/migration)
- [V2 documentation](https://www.genderapi.io/api-documentation)
- [V1 documentation](https://www.genderapi.io/api-documentation/v1)