# API Token 取得方法說明

### 🔐Token、Application 與 API 的授權關係說明

在 SuperiorAPIs 中，API 存取權限是透過 **Application → Token → API** 的階層授權機制進行控管的。這樣的機制讓 SuperiorAPIs 能更精細地管理 API 存取權限與資源安全性，並避免單一 Token 擁有過多權限而造成風險擴大。

> **Application, Token 以及 API 之間的關係請參考如下圖** 

{% @mermaid/diagram content="graph TD
A1\[Application: dev-agent]
A1 --> T1\[Token A]
A1 --> API1\[/API: url-reader/]

```
A2[Application: prod-agent]
A2 --> T2[Token B]
A2 --> API1
A2 --> API2[/API: text-classifier/]
```

" %}

#### ✅ 實際使用情境：

1. 你建立一個 Application，例如名稱為 `my-gpt-agent` ，建立後就會預設在 Application 底下生成一組 Token。
2. 在該 Application 下你選擇加入 API：`url-reader`、`text-classifier`。
3. 此 Token 就只能存取這兩個被授權的 API。
4. 若你要同時測試不同應用場景（如測試 vs 生產），就可以建立出多個 Application 。

### 🔎建立 Application Token 的示範流程

Application 清單[由此連結](https://superiorapis.cteam.com.tw/overview/application)

<figure><img src="/files/PP4ZLWlkVgjj8EeEb6lD" alt=""><figcaption><p>1.建立應用(Application)流程</p></figcaption></figure>

<figure><img src="/files/VFals2THeq3iroXCcLEZ" alt=""><figcaption><p>2.進入 Application 設定頁面可取得 Token</p></figcaption></figure>

如果要在 Application 加入 API ，可進一步參考以下的範例

<figure><img src="/files/GtK7zLlxiyPh0zMWOImf" alt=""><figcaption><p>3.示範將 API 加入 Appliction 清單當中</p></figcaption></figure>


---

# 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:

```
GET https://cteam-com.gitbook.io/superior/api-token-qu-de-fang-fa-shuo-ming.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.