> ## Documentation Index
> Fetch the complete documentation index at: https://doc.raliopay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

# Creating an Individual User — Field Values Reference

When you create an individual user (`POST /api/v1/account/individual-users`), several fields only accept a constrained set of values. This guide explains **where each value comes from** so your request doesn't get rejected with a validation error.

There are two kinds of constrained fields:

* **Fixed enums** — a closed list defined by the API. The valid values are shown in the request schema of the [Create individual user](/api-reference/individual-users/create-individual-user) endpoint, and listed here for convenience.
* **Dynamic catalogs** — values that live in a reference endpoint you must query first. You cannot hardcode these; always fetch the current list.

***

## Fixed enums

These values are part of the API contract. Send them exactly as written (uppercase, underscore-separated).

### `documentType`

| Value             | Description                |
| :---------------- | :------------------------- |
| `NATIONAL_ID`     | National identity document |
| `RESIDENCE_CARD`  | Residence permit / card    |
| `PASSPORT`        | Passport                   |
| `DRIVING_LICENSE` | Driving license            |

### `employmentStatus`

| Value           |
| :-------------- |
| `EMPLOYED`      |
| `SELF_EMPLOYED` |
| `UNEMPLOYED`    |
| `STUDENT`       |
| `RETIRED`       |

### `sourceOfFunds`

| Value                 |
| :-------------------- |
| `EMPLOYMENT`          |
| `SALARY`              |
| `SAVINGS`             |
| `INVESTMENT`          |
| `PENSION`             |
| `GOVERNMENT_BENEFITS` |
| `PROPERTY_SALES`      |
| `INHERITANCE`         |
| `COMBINATION`         |

***

## Dynamic catalogs

### `activity` — fetch from the Activities catalog

The `activity` field expects a **slug** from the activities catalog, not free text. Query the reference endpoint and use the `slug` value of the activity that best matches the user.

**Endpoint**

```text theme={null}
GET /api/v1/reference/activities
```

See [List active activities](/api-reference/activities/list-active-activities). The endpoint is paginated and supports `Accept-Language: es` for Spanish names.

**Example response item**

```json theme={null}
{
  "name": "Sales",
  "slug": "SALES_MANAGER"
}
```

> **Important:** Send the `slug` (e.g. `SALES_MANAGER`), not the `name`. The catalog can change over time, so fetch it dynamically instead of hardcoding values.

### Country fields — ISO 3166-1 alpha-2

`birthCountry`, `nationality`, `country`, `phoneNumberCountry`, `publicOfficeCountry` and `pepAssociateCountry` all expect a **2-letter ISO 3166-1 alpha-2 code** (e.g. `ES`, `US`, `FR`).

To get the list of countries Ralio supports, query:

```text theme={null}
GET /api/v1/reference/countries
```

See [List countries](/api-reference/countries/list-countries).

***

## Free-text fields

`professionalSector` is **not** an enum — it accepts free text describing the user's professional sector. There is no catalog to query for it.
