> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/settings/connections/crypto-exchanges/mexc.md).

# MEXC

{% hint style="success" %}
Starting with version 7.0, the Tiger.com terminal supports a connection to the MEXC exchange, providing access to spot instruments quoted in USDT that are enabled for API trading by the exchange.
{% endhint %}

{% hint style="info" %}
MEXC spot instruments enabled for API trading are marked in the exchange's documentation with the flag "isSpotTradingAllowed": true.
\
Instruments for which API trading is unavailable are marked with the flag "isSpotTradingAllowed": false. For such instruments, only the retrieval of historical and real-time market data will be available in the terminal, with no trading capability.

![](/files/0pL70Q8mUF4JS2IU1yvH)
{% endhint %}

{% stepper %}
{% step %}

### MEXC Account Registration

To get started, go to the MEXC website and create an account.

<figure><img src="/files/IYR8DQxC1kfX0CeYUi3S" alt=""><figcaption></figcaption></figure>

On this screen, select the email registration option, enter your email address, and click **"Continue".**

<figure><img src="/files/0YexsXv7MS0uNhWwz1Jw" alt=""><figcaption></figcaption></figure>

A code will be sent to your email during registration. To complete the process successfully, enter this 6-digit code into the Email Verification Code field.

<figure><img src="/files/5125KIj1xrGqjlsNaF9q" alt=""><figcaption></figcaption></figure>

Set a password, and you will be redirected to the verification page. You will already be logged into your account.
{% endstep %}

{% step %}

### Complete account verification

After registering your MEXC account, navigate to the Identity Verification section.

<figure><img src="/files/QVGJaf4wM5HKRKDTxAu9" alt=""><figcaption></figcaption></figure>

This screen displays the available verification levels: Basic and Advanced. To proceed, click **"Verify via Web"** (Advanced KYC verification is recommended).

The **"Advanced KYC"** window will then open. Here, you must select your country of residence and the type of identification document you wish to use. Next, you will reach the standard upload page for ID photos; upload the required images and click **"Continue".** This is followed by a **facial recognition** check. Your identity will be confirmed within a few minutes, completing the verification process.

<figure><img src="/files/8MIro5VW1UbblngFGPv8" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Enable two-factor authentication (2FA)

Before creating a MEXC API key, you must link Google Authenticator or a phone number. Otherwise, you will receive a warning about a low account security level when creating API keys.

Therefore, you need to go to the **Security** section, as shown in the screenshot:

<figure><img src="/files/nHMyllQY0YrrGxWXzr9e" alt=""><figcaption></figcaption></figure>

A "Security Reminder" window will appear. Select Google Authenticator.

<figure><img src="/files/e6TDOozf8D3j7C95dDVF" alt=""><figcaption></figcaption></figure>

At this stage, you need to download the Google Authenticator app to your phone. After installation, tap **Next.**

<figure><img src="/files/bXiY4LJXoTtOtVZPtJRu" alt=""><figcaption></figcaption></figure>

Here, you need to scan the QR code or save the key to add it to Google Authenticator. After adding it, click **Next.**

At this stage, MEXC will request:

* an email verification code;
* a Google Authenticator code.

Enter both codes and click **Confirm**. The authentication process is complete.

> Important: whenever you create a new API key, BingX will again require both the email code and the Google Authenticator code.
> {% endstep %}

{% step %}

### Creating API keys

Go to the API Management section.

<figure><img src="/files/Kr62Z0AtwWe9tdTo93W0" alt=""><figcaption></figcaption></figure>

In the window that opens, enable the necessary permissions for spot and futures trading as shown in the screenshot, enter a name of your choice for the API key in the **"Note"** section, agree to the exchange's terms, and click the **"Create"** button.

<figure><img src="/files/kyMlbQfbUmfVpEufIP1k" alt=""><figcaption></figcaption></figure>

Enter the confirmation codes (sent via email and 2FA) and click the **"Submit"** button to complete the API key creation process.

<figure><img src="/files/jBgruZvK0Cgpbg3xn7Mr" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Save the API Key and Secret Key

The API keys will appear on the page that opens; save them!

<figure><img src="/files/aPNZvXlHoIEbb5JIPasv" alt=""><figcaption></figcaption></figure>

This screen displays:

* **API Key;**
* **Secret Key.**

Copy them immediately and save them in a secure place.

> Please note: **The Secret Key is displayed only once** and will not be available again after you close the page.
> {% endstep %}

{% step %}

### Connect MEXC to Tiger.com

Now open the Tiger.com terminal and add a connection to BingX by going to **File → Connections → New Connection → Crypto Exchanges → MEXC**.

<figure><img src="/files/EsLAiEgkyvXsTOD72Wpy" alt=""><figcaption></figcaption></figure>

At this stage, you need to:

1. Specify a connection name, e.g., **BingX** (optional);
2. Optionally, **enable view-only mode** and skip entering API keys (note: trading will not be permitted in this mode);
3. Select the server: Spot or Futures;
4. If view-only mode is disabled, enter the API keys from step 5:
   1. API Key;
   2. API Secret.
5. Select **"Not used"** in the **Proxy** field (optional);
6. Click the **"Connect to BingX"** button.

> Important: The Spot server connects only via API keys. The Futures server supports connection via either API keys or UID (Web token). Instructions for obtaining the UID (Web token) are provided in step 8.

<figure><img src="/files/uiUZKZJfG8W4wVnmMMg3" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Completing the connection

Upon successful connection setup, you will see a corresponding message, a green icon next to the MEXC connection, and a pop-up connection notification in the bottom-right corner:

<figure><img src="/files/AUb3CLSknRlXr01QDWKK" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Connecting to the Futures Server via UID (Web Token)

To begin, log in to your MEXC exchange account, navigate to the **"Futures"** section, and follow these steps:

* Press F12 to open the **DevTools window**;
* Select the **"Network"** tab from the top panel;
* Click the search bar and enter: **/api/platform/futures/api/v1/private/account/assets**;
* Click on any of the results and locate the **"Authorization"** field.

The "Authorization" value is the required UID (Web token). **Save it!**

1. Next, follow the same path (File → Connections → New Connection → Crypto Exchanges → MEXC) to set up the MEXC connection;
2. Select "Futures" for the Server and "UID (Web token)" for the Connection Method;
3. Paste the copied token in full, and your connection will be established within a few seconds.

<figure><img src="/files/dwjMQCYBwPjvvAQAXYTq" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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://support.tiger.com/english/settings/connections/crypto-exchanges/mexc.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.