> For the complete documentation index, see [llms.txt](https://help.radiantsecurity.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.radiantsecurity.ai/radiant-connectors/endpoint/trend-micro/trend-vision-one/create-a-trend-micro-vision-one-api-token.md).

# Create a Trend Micro Vision One API Token

### Prerequisites

* [ ] Admin access to Trend Vision One

### **Obtain authentication tokens**

Generate authentication tokens in the Trend Vision One console to access the APIs.

1. On the Trend Micro Vision One console, go to **Administration** > **API Keys**.
2. Generate a new authentication token.
3. Click **Add API key**.
4. Specify the settings of the new API key**:**
   1. **Name**: Enter a meaningful name that can help you identify the API key (Example: `RadiantSecurity_API_Token`).
   2. **Role**: The user role assigned to the key. The assigned role must have the following permissions:

      | API Category               | App                        | Permissions              |
      | -------------------------- | -------------------------- | ------------------------ |
      | Alerts / Workbench         | Workbench                  | View, filter, and search |
      | Observed Attack Techniques | Observed Attack Techniques | View, filter, and search |
      | Search                     | Search                     | View, filter, and search |
   3. **Expiration time**: The time the API key remains valid. By default, authentication tokens expire one year after creation. However, a master administrator can delete and regenerate tokens at any time.
      1. **Status**: Provides information about whether the API key is enabled.
      2. **Details**: Provides additional information about the API key.
5. Click **Add**.
6. Copy and store the authentication token in a secure location.
7. Log into your Radiant account and go to **Settings** > **Credentials** > **+ Add Credential**

<figure><img src="/files/XPWTvbXBIHJzOmBGlTjK" alt=""><figcaption></figcaption></figure>

8. Select the credential of type **Secrets Sharing Credential.**
9. Click **Configure credential.**

<div align="left"><figure><img src="/files/RjyYJeYM34qyOJtHriKW" alt="" width="375"><figcaption></figcaption></figure></div>

10. Give it a descriptive name, and add the token in the **Free text** field.
11. Click **Add Credential**.

<div align="left"><figure><img src="/files/UtQ1gEiw0gv5M1SWliWH" alt="" width="375"><figcaption></figcaption></figure></div>


---

# 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://help.radiantsecurity.ai/radiant-connectors/endpoint/trend-micro/trend-vision-one/create-a-trend-micro-vision-one-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.