> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-api/smart-auth-api/available-resources/identity.md).

# Create identity

The identity creation process is necessary to enable authentication for a given user. Subsequent authentication attempts for this user will be compared against this created identity, based on the personId, while storing the user's context data. A clear selfie is required, used for facial validation.

Email and phone are optional for the API, but required if you intend to allow OTPs as a means of re-authenticating this user. In this case, in addition to enabling email or SMS in the authentication policy, users must have an email and phone number registered.

{% hint style="warning" %}
All calls to the API are authenticated and must have the token next to `Bearer` prefix in the `Authorization` header of the request. Calls with a missing or invalid access token will return status code **401** ("Unauthorized").
{% endhint %}

The token used to make requests to the API is the **access token** [generated according to these instructions.](/caf-api/smart-auth-api/authentication.md).

{% openapi src="/files/NJIVu1wueLBrpL5UQ6xu" path="/identities" method="post" %}
[create-identity.yaml](https://3218940882-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVxCOSyBojfSIE5fcpfH%2Fuploads%2Fgit-blob-1b7f76d1a0840ca62338f5d99a69ead811ad1958%2Fcreate-identity.yaml?alt=media)
{% endopenapi %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.caf.io/caf-api/smart-auth-api/available-resources/identity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.