> For the complete documentation index, see [llms.txt](https://sitasys-ag.gitbook.io/evalink-talos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitasys-ag.gitbook.io/evalink-talos/get-started/create-an-api-token.md).

# 5. Create your first API Token in evalink talos

To authenticate against the evalink talos API in Postman, one of the first steps you need to do is create an API Token in evalink talos.

Log in to talos.evalink.io with your credentials:

{% embed url="<https://talos.evalink.io/>" %}

Once you are logged into your evalink talos account,&#x20;

From the main menu, click on “**Company**”.&#x20;

Click on the tab “**Integrations**” .

Click on the button “**Manage Tokens**”.

To create an API Token, click on the button “**Create Token**”.

Give the API token a name. After that, select the required permissions.

**Note:** If you are going to use the API token for testing purposes, we recommend selecting **all** the permissions.

Just above the **API Token**, you will also find your **Company ID**.

**Please note down both the API Token and the Company ID as they are very important for your interactions with the evalink talos API.**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sitasys-ag.gitbook.io/evalink-talos/get-started/create-an-api-token.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
