# List genders

Returns all available gender options.
Gender codes are used when creating users or customers (e.g. `"m"`, `"f"`).
Some genders represent legal entities (companies) — check the `is_entity` flag.

Endpoint: GET /users/genders
Version: 1.6.0
Security: bearerAuth

## Security:

  - `bearerAuth` (unknown)
    http bearer opaque

## Response 200:

  - `200` (unknown)
    List of genders

## Response 200 fields (application/json):

  - `data` (array)

  - `data.id` (string)
    Gender code (used in create/update requests).
    Example: m

  - `data.description` (string)
    Full label.
    Example: Monsieur

  - `data.description_legal` (string | null)
    Legal form description.

  - `data.abbreviation` (string | null)
    Short abbreviation.
    Example: M.

  - `data.sexe` (string | null)
    Sexe indicator.

  - `data.is_entity` (boolean)
    Whether this gender represents a legal entity (company/société).
When true, the contact is a professional/company, not a person.

  - `data.private` (boolean)
    Whether this gender is for internal use only.

## Response 403:

  - `403` (unknown)
    Access denied. The error `code` is always `FORBIDDEN`; the `message` gives the cause:
- `You do not have permission to perform this action.`
 — the access does not

hold the API pack / right required by the endpoint.
- `Insufficient scope for this request.`
 — the resource targeted by the request

(user, customer, product, agency, transaction, ...) is outside the scope of

the authenticated access.
- `Access denied for this editor.`
 /
`Your IP address has been blocked.`
 —

editor or IP restriction.

## Response 403 fields (application/json):

  - `error` (object)

  - `error.code` (string, required)

  - `error.message` (string, required)

## Response 403 examples:

  - `Missing API pack / right` (unknown)

  - `Resource outside the scope of the access` (unknown)

