> For the complete documentation index, see [llms.txt](https://verify-doc.tiller-verify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verify-doc.tiller-verify.com/verify-api/endpoints/api-reference/authentication.md).

# Authentication

The Verify by Tiller API employs a secure authentication mechanism to ensure that only authorised users can access the API. This section covers everything you need to know about obtaining and using authentication tokens to interact with the Verify by Tiller API.

## Obtaining your Token

To obtain an authentication token, you will need to make a POST request to our authentication endpoint with your user credentials. 

:exclamation:It is important that the user credentials have been given the correct permissions. Please contact <support@tillertech.com> to request the API permissions be added to the user profile.

Here's a step-by-step guide:

1\) Ensure that your user credentials have API permissions. If you are unsure, contact <support@tillertech.com>.

2\) Send a POST request with your user credentials in the request body. Use 'password' in the grant type.

{% openapi src="/files/d3yB4cFl16j0xlR4QP71" path="/ext/authentications/token" method="post" %}
[TillerTechnologies-verify-api-v1-oas3.json](https://content.gitbook.com/content/0zS5rWXn6QhdPJuSHu9k/blobs/QIqANJoV2sVgHqFFWsfb/TillerTechnologies-verify-api-v1-oas3.json)
{% endopenapi %}

After successfully authenticating, you will receive a JSON response containing your '*access\_token'*. This token must be included in the Authorization header of your subsequent API requests. It should be included as a Bearer token.


---

# 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://verify-doc.tiller-verify.com/verify-api/endpoints/api-reference/authentication.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.