> 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/authentications.md).

# Authentications

An authentication process may encompass all the validations carried out according to the policy established when the SDK was initialized. These validations and their analyses can include data on the contexts in which the user was situated at the time of the request. Subsequently, based on the defined policy and validation rules, the status of the authentication is determined.

{% 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/H5dTTDnxZOlo66R8r7Ar" path="/authentications/{attemptId}" method="get" %}
[authentications-get-one.yaml](https://3218940882-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVxCOSyBojfSIE5fcpfH%2Fuploads%2Fgit-blob-67ff1c24e029cba9af68bcc0bea1fd260f525448%2Fauthentications-get-one.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/authentications.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.