# Aster

### Aster注册交易所

邀请码：`399131`

邀请链接：

{% embed url="<https://www.asterdex.com/en/referral/399131>" %}

### 交易所创建 API

1. 进入Aster API设置页面：<https://www.asterdex.com/en/api-management>，点击“ **创建 API** ”

2. 输入名称，例如 “**Hibot**” ，点击“**创建**”

   <figure><img src="/files/RMIxpcIbNvG0acC7lJqk" alt=""><figcaption><p>创建API图示 - 1</p></figcaption></figure>

3. 成功创建的API信息窗口，可见该 API 的：

* “**API 密钥**” - 对应添加时填写的 API Key
* “**API** **秘密密钥**” -对应添加时填写的 API 密钥

<figure><img src="/files/5xIKlmUX0W5YiuCZROiT" alt=""><figcaption><p>创建API图示 - 2</p></figcaption></figure>

{% hint style="warning" %} <mark style="color:orange;">请妥善保存API信息</mark>
{% endhint %}

***

#### 将 API 添加到 Hibot <a href="#jiang-api-tian-jia-dao-hibot" id="jiang-api-tian-jia-dao-hibot"></a>

1. 在 Hibot 的套利API管理页面，点击“**新增 API**”

   1. 选择 “ASTER”
   2. 填写上一个步骤中的 “**API 密钥**”
   3. 填写上一个步骤中的 “**API** **秘密密钥**”

   点击“**提交**”

<figure><img src="/files/iEA6Pabg3HCP4tVTmXBr" alt=""><figcaption><p>添加API图示 - 1</p></figcaption></figure>

2. 添加成功后可在列表中查看该 API
   1. 点击“**测试** / ***Test***”按钮，如出现 “<mark style="color:green;">**Ok**</mark>” 字样即表示该API信息填写正确<mark style="color:green;">连接成功</mark>，若出现 “<mark style="color:red;">N/A</mark>” 字样即表示输入的 API 信息有误，请删除再重新添加
   2. 点击 “***Ping***” 按钮可测试连接交易所的延迟

<figure><img src="/files/zNYAxfwihAcKBimTOgB6" alt=""><figcaption><p>添加API图示 - 2</p></figcaption></figure>

{% hint style="info" %}
关于 API 延迟，请参考[API连接延迟](/hibot-docs/others/api-delay.md)文档。
{% endhint %}


---

# Agent Instructions: 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://hibot-docs.gitbook.io/hibot-docs/arbitrage/exchange-api-settings/aster.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.