How to get an API key for gate.io.

This page explains how to get an API key for gate.io's transaction history.

Through the API, only spot trading and futures trading history can be obtained.

*Please note that the acquisition history of points (POINT) usable for transaction fees, etc., on gate.io is not automatically supported. For acquisition histories that cannot be retrieved, please upload them separately in a custom file. You can download the format and instructions for the custom file here.

 

1.After logging in, click on the Profile icon and select "API Manegement".

スクリーンショット 2024-05-21 115441.png

 

2.Select"API Managements &APIs"in "Sub-accounts API"tub and click on"Create API Keys".

3.Create API Key Screen

Set the following parameters and click "Confirm":

  • API Key Remark:You can write anything here, but you must enter something for the "Confirm" button to be displayed.
  • IP Whitelist:52.69.115.51, 52.193.138.38, 18.179.74.94
  • API Key Type:API v4 Key
  • Account Type:Classic Account
  • Check all options except for "Enable trading pairs allowlist," and select "Read-Only" for all permissions.
  • Click on "Submit".

mceclip0.png

*IP addresses were made public on February 14, 2023. If you do not set the IP addresses, the API key will have a 90-day expiration period, and you will need to create a new key each time it expires.

 

4.Ensure to clear the fund password and 2FA.

mceclip1.png

5.API key and secret key creation is complete *Make sure to keep them.

mceclip2.png

Connect via gate.io API

Add API connectivity to gate.io by entering the generated API key and secret via Connect to your exchanges and click "Submit".

If you don't have sub-accounts, it's generally fine to leave it blank.

If you do have sub-accounts, please enter any sub-account name of your choice. In that case, transactions from sub-accounts will also be reflected separately as separate transactions.

Note that if you use the same API key with different sub-account names for API integration, it may be recognized as different API keys, causing duplicate entries.

 

Disclaimer

Please note that we will not be held responsible for any damages caused by unauthorized use or other accidents due to API connections. When connecting, please be sure to use the API key specified by us.