> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/api-tokens/create-an-api-access-token-as-a-brand.md).
# 作为品牌创建 API 访问令牌
*账户管理员* 和 *实施专员* 品牌账户成员可以启用 impact.com API 访问并查看账户凭据。按照以下步骤创建新的 API 令牌并配置该令牌的访问范围。阅读一些有关如何 [保护您的访问令牌安全](/other/zh/reference-documentation/api-access-tokens-and-changelog/keep-your-access-tokens-secure.md).
{% hint style="info" %}
**注意：** 访问 impact.com 的 [集成门户](https://integrations.impact.com/brand-api-reference) ，以查看 API 参考文档、集成指南等。
{% endhint %}
#### 创建访问令牌
1. 从顶部导航栏中，选择  **\[用户资料]** → **设置**.
2. 在左侧列中，滚动到 *技术*，然后选择 **API**.
3. 通过选择以下项来创建新令牌： **创建访问令牌** 页面右上角。
#### 创建令牌
1. 设置
* 在 **令牌名称** 文本字段中输入一个合适的名称。
* 添加一个 **说明** 用于描述令牌用途，以便将来参考。
* 指定 **API 版本** 该令牌将兼容的 API 版本。我们建议使用最新的 API 版本，这也是默认选项。
* 选择 **下一步**.
2. 联系信息
* 选择一个 **主要联系人** 从下拉菜单中选择。我们将就开发更新与主要联系人联系。
* 可选地，为应该了解与访问令牌相关更新的开发者添加电子邮件地址。在为不是账户用户的开发者创建令牌时，这很方便。
* 选择 **下一步**.
3. API 范围
* 先启用一个 API 类别，然后勾选左侧的复选框，选择要允许在 API 令牌上的访问范围。
* 你可以通过单击 **全部清除** 页面右上角附近的按钮来清除所有范围。
4. 选择创建
* 最后，选择 **创建** 页面右下角的。
---
# 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/account-administration/account-settings/api-tokens/create-an-api-access-token-as-a-brand.md?ask=&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.
