> 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/partner/zh/ni-xiang-liao-jie-shen-me/account-management/account-settings/api-tokens/manage-legacy-api-tokens-as-a-partner.md).
# 作为合作伙伴管理旧版 API 令牌
在 2025 年 4 月之前创建的任何 API 令牌都被视为旧版令牌。本文将帮助你查找并管理你的旧版 API 访问令牌。阅读一些关于如何 [保护你的访问令牌安全](/other/zh/reference-documentation/api-access-tokens-and-changelog/keep-your-access-tokens-secure.md).
{% hint style="success" %}
**注意：** 访问 impact.com 的 [集成门户](https://integrations.impact.com/) 以查看 API 参考文档、集成指南等。
{% endhint %}
## 管理访问令牌
1. 在顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在 *技术*下，选择 [**API**](https://app.impact.com/secure/mediapartner/api/fr/api-access-tokens-ui.ihtml).
3. 在右上角，选择 **启用旧版令牌**，如果你需要使用旧版 API 令牌。选择该按钮后，它将消失，并且会出现一个 *旧版账户令牌* 卡片。
4. 通过选择以下内容来管理旧版令牌：  **\[更多]** 令牌卡片上的图标，然后从下拉菜单中选择一个选项。请参阅 *菜单参考* 下面内容，了解可用管理选项的更多信息。
5. 你还可以选择令牌卡片来查看 API 令牌信息。
* 在 *概览* 页面，你可以查看令牌信息，并且可能可以通过选择 **API 版本** 下拉菜单。
* 在 *API 凭据* 页面，你可以查看并复制 **账户 SID** 和 **认证令牌** 读/写和只读令牌的值。
菜单参考
| 菜单项 | 描述 |
| ----------- | ------------------------------------------------------------------------ |
| **重置（读/写）** | 重置读/写令牌。将生成新的 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/partner/zh/ni-xiang-liao-jie-shen-me/account-management/account-settings/api-tokens/manage-legacy-api-tokens-as-a-partner.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.