> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/cregis-wallet-guide/zh-tw/deveoper-and-payment-engine/api-management.md).
# 團隊API
團隊 API 提供團隊級資源管理能力，支持開發者通過 API 查詢和管理團隊相關數據，包括團隊賬户、錢包、賬單等信息。與 WaaS API 不同，團隊 API 基於團隊 API Key進行身份認證，僅允許訪問當前團隊下具有權限的資源，無法訪問其他團隊的數據。開發者可通過團隊 API 將團隊管理能力集成到內部業務系統，實現自動化運營、財務對賬、資產管理等場景。
## **創建API**
點擊「管理 > API管理」頁面的「創建」按鈕
進入創建頁面後，完成API名稱、權限、IP白名單配置，點擊左下方「創建」按鈕。
完成身份驗證
創建成功
**注意：請複製您的 Secret Key 並妥善保管，後續將不再顯示完整內容。**
## **編輯API**
點擊「管理 > API管理」頁面的「編輯」按鈕
進入編輯頁面後，可對API名稱、權限、IP白名單進行編輯，完成後，點擊左下方「儲存」按鈕。
完成身份驗證，編輯成功
## **啓用/禁用API**
點擊「管理 > API管理」頁面的「啓用/禁用」按鈕
彈出提示彈窗，點擊「確定」按鈕
完成身份驗證，則啓用/禁用成功
## **查看API Key**
點擊「管理 > API管理」頁面的「更多 > 查看API Key」按鈕
完成身份驗證
可查看並複製 API Key 信息
**刪除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://support.cregis.com/cregis-wallet-guide/zh-tw/deveoper-and-payment-engine/api-management.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.
