For the /api/v1/users endpoint response, why are profile.firstName and profile.lastName documented as being nullable?

[jenip]

When adding a user, the following fields cannot be left blank :

However, as shown in List all users , profile.​firstName and profile.​lastName are documented as being nullable.

Thus, why are profile.​firstName and profile.​lastName documented as being nullable if they are both required when creating a user.

[vk-giri]

Hi,

First name and last name can be made optional if required, as mentioned here - Make the user profile first and last name optional | Okta Classic Engine

Hence, the documentation states that it can be null.