> For the complete documentation index, see [llms.txt](https://docs.sigrex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sigrex.io/cex-signal-bot/exchange-api-key.md).

# Exchange API key

This page explains how to securely connect your centralized exchange API keys to Sigrex. This allows the platform to execute trades on your behalf based on signal payloads.

***

## 🌐 Supported CEX-es

<table><thead><tr><th width="130">Exchange</th><th width="124.6666259765625">Type</th><th width="81.6666259765625" data-type="checkbox">Spot</th><th width="101.6666259765625" data-type="checkbox">Futures</th><th width="126.333251953125">More</th><th width="183.6668701171875">API ID</th></tr></thead><tbody><tr><td><a href="https://alpaca.markets">Alpaca</a> </td><td>CEX</td><td>true</td><td>false</td><td>No Paper trading</td><td>Spot: <code>1</code></td></tr><tr><td><a href="https://www.binance.com">Binance</a></td><td>CEX</td><td>true</td><td>true</td><td>USD-M only</td><td><p>Spot: <code>2</code> </p><p>Futures: <code>3</code></p></td></tr><tr><td><a href="https://www.bitget.com/">Bitget </a></td><td>CEX</td><td>true</td><td>true</td><td>USD-M only</td><td><p>Spot: <code>13</code> </p><p>Futures: <code>14</code></p></td></tr><tr><td><a href="https://www.mexc.com">MEXC</a> </td><td>CEX</td><td>true</td><td>true</td><td>USD-M only</td><td><p>Spot: <code>4</code> </p><p>Futures: <code>16</code></p></td></tr><tr><td><a href="https://www.gate.io">Gate.io</a> </td><td>CEX</td><td>true</td><td>true</td><td>USD-M only</td><td><p>Spot: <code>8</code> </p><p>Futures: <code>9</code></p></td></tr><tr><td><a href="https://www.kraken.com">Kraken</a> </td><td>CEX</td><td>true</td><td>true</td><td></td><td><p>Spot: <code>6</code> </p><p>Futures: <code>7</code></p></td></tr><tr><td><a href="https://app.hyperliquid.xyz/trade/BTC">Hyperliquid </a></td><td>CEX</td><td>true</td><td>true</td><td>USDC only</td><td><p>Spot: <code>11</code> </p><p>Futures: <code>12</code></p></td></tr></tbody></table>

> 📌 *Only real/live trading accounts are supported for Alpaca. Paper trading keys are not allowed.*

{% hint style="info" %}
We are continuously working to expand Sigrex’s capabilities. **More exchange integrations are planned for the future**, including both centralized and decentralized platforms. Stay tuned!
{% endhint %}

***

## 🛠️ How to Connect an API Key

1. **Name (Optional):**\
   You can assign a name to your API key connection to help identify it later. If left blank, the system will handle it.
2. **Choose Exchange:**\
   Select which of the supported exchanges the API key is from.
3. **Enter Keys:**
   * **Public Key** (API key)
   * **Private Key** (Secret key)
   * **Extra** (if needed)
4. **Validation:**\
   After submission, Sigrex sends a test request to the selected exchange to validate the API credentials and ensure the connection is functional.

***

## ⚠️ Important Notes

* **Separate Connections for Spot & Futures:**\
  If you want to use the same exchange for both spot and futures trading, **create two separate API connections**—one for spot and one for futures.
* **Alpaca Restrictions:**\
  We do **not** support paper trading keys from Alpaca. Please ensure your account is live before connecting.
* **No Modification After Creation:**\
  After an API key connection is created, it **cannot be edited** for security reasons. If you need to change the keys or exchange:
  1. Disconnect it from all linked bots.
  2. Delete the connection.
  3. Create a new one with updated keys.

***

## 🔐 Security Notice

All API keys (public and private) are encrypted using strong server-side encryption and are **only decrypted at runtime**—when executing trades. Your keys are never exposed or stored in plaintext.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.sigrex.io/cex-signal-bot/exchange-api-key.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.