> 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/edit-api-access-tokens-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. 通过选择以下内容来编辑令牌： **令牌卡片**.
#### 编辑令牌
概览
* 您可以更新以下内容： **令牌名称** 或 **说明** 文本字段。
* 您还可以更新 **API 版本** ，如果访问令牌配置的 API 版本早于最新版本。
API 凭据
* 在此页面上，您可以选择其他 **主要联系人** ，如有需要，可从下拉菜单中选择。
* 可选地，您可以添加或移除应包含在与访问令牌相关更新中的开发人员电子邮件地址。
* 您可以选择 **复制** 以复制 *账户 SID*，这是该令牌唯一的 API 标识符。在某些应用程序中，这被用作 *用户名*.
* 选择 **复制** 以复制 *认证令牌*。在某些应用程序中，这被用作 *密码*.
* 您也可以选择 **重置令牌**，以重置 *认证令牌* 并撤销所有关联的令牌授权。如果您确定要执行此操作，请选择 **重置令牌** 在确认框中再次选择。
API 范围
* 打开或关闭，然后勾选或取消勾选左侧的复选框，以选择您希望允许给 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 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/edit-api-access-tokens-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.
