This page introduces the trade types that can be obtained via Bitget file and API.
Contents
1. Our Support Status for Bitget
| Trade type | File support | API support | API endpoint |
| Spot Trades | ✔ | ✔ | Bitget/Trades |
| USDT-M Futures | ✔ | ✔ | Bitget/Future Record (USDT-M) |
| USDC-M Futures | ✔ | ✔ | Bitget/Future Record (USDC-M) |
| Coin-M Futures | ✔ | ✔ | Bitget/Future Record (COIN-M) |
| Savings | ✔ | ✔ | Bitget/Trades |
| Staking | ✔ | ✔ | Bitget/Trades |
| Convert Small Balance to BGB | ✔ | ✔ | Bitget/Trades |
| Leverage/Margin | ✔ | × | |
| Copy Trade | ▲ | ▲ | Bitget/Trades |
| Dual Invest | × | × | |
| Bitget Onchain | × | × | |
| Others | × | × |
*Bitget Onchain: Since the exchange does not provide transaction history via API, automatic support is not available. Files that contain only Onchain history (unsupported by cryptact) include records that differ from the actual transaction details, so they are not supported. Although some Onchain history is included in the spot trading file, it lacks certain information and therefore will not be reflected upon upload. Please use a custom file to import your Onchain history.
2. Important Notes about the File
- Transaction type shown as "Financial"・・This label is used for various transaction types on Bitget, making it unclear what the actual transaction is. As a result, we treat it as "To confirm transactions", and customers are required to manually select the correct transaction type on the screen. When the file is uploaded, a transaction type called "to confirm" is displayed.
- Transaction type shown as a number — When the transaction type appears as a number (as seen with Rakuten Wallet, etc.), third parties cannot identify the actual transaction. Therefore, it is marked as "To confirm transactions". When the file is uploaded, a transaction type called "to confirm" is displayed.
-
Change in Processing of Bonus Transactions (Effective September 12, 2024)
As of September 12, 2024, the following transaction types are now handled as follows:
-
bonus_issue: Reflected as Bonus / BONUS
-
bonus_expired: Reflected as Loss / LOSS
-
bonus_recycle: Continues to be reflected as Loss / LOSS
Previously, bonus_issue was treated like a margin bonus that could not be used until a loss occurred, so it was not shown in the transaction list even if uploaded. Similarly, bonus_expired was not reflected if it expired unused.
However, to avoid situations where losses appear larger than they actually are due to missing bonus data, we have updated the processing method accordingly. -
Spot Trades:
-
"Buy" and "Sell"
In the exchange history file, "Buy" and "Sell" transactions are recorded as two separate lines. However, Cryptact has updated its specifications as of April 24, 2025, and now reflects them as a single line, categorized as either "Buy" or "Sell". -
"Gains" and "Consumption"
Similar to "Buy" and "Sell", these transactions are also now processed as a single combined line. -
Exchange income/Exchange spending, Sell/Buy, Gains/Consumption
Bitget files list transactions like "Exchange income," "Exchange spending," "Buy," and "Sell" across two lines for the same timestamp. For clarity, at cryptact, we treat "Exchange income" and "Buy" as "buy" transactions, and "Exchange spending" and "Sell" as "sell" transactions, even though the file may randomly list transaction types when multiple transactions occur simultaneously.
-
"Received from delivery" / "Deducted for delivery"
These appear to be pre-market transactions. However, since the timestamps do not match, they cannot be processed as a pair in the system and will not be reflected even if uploaded. Please use a custom file to enter these transactions manually.
USDT-M Futures/USDC-M Futures/Coin-M Futures:
- For futures trading funding fees, they occur every one to several hours for both file and API transactions. Each occurrence is reflected as either a "Bonus" or a "Loss" in the transaction history.
Savings:
- We have received information that, in the files, interest income from flexible savings has been labeled as "365" starting from May 30, 2024 (specific time unknown) in Japan time. Therefore, we have decided to reflect "365" on the file on Oct 31, 2024, as "Bonus."
Leverage/Margin:
- we have confirmed that in one of the customer's margin history files, the "Amount" column in column E contains the coin balance instead of the trade quantity. This may be a mistake on the exchange's side, so please check whether the correct trade quantity is recorded in the "Amount" column. If there is an error in the file, please contact the exchange and upload the corrected file to cryptact.
- Transactions related to borrowing (Borrow with a positive Amount) and repayment (Borrow with a negative Amount) are not currently supported automatically. Please upload them using a custom file.
Note: Trades made after borrowing (e.g., buy/sell) are supported automatically.
Repayment transactions often include interest, and since the file does not indicate how much of the amount is principal vs. interest, automatic processing is not possible.
Copy trade:
- Both API and file support "Copy Trade profit" and "Copy Trade expense" for spot trading.
If there are any other copy trade histories for spot trading that are not reflected, please contact support.
Additionally, as we are currently collecting samples for futures trade histories, they are not supported at this time.
Dual Invest:
- We have confirmed that dual investment transactions are labeled as "Financial" in the file. However, since "Financial" is used for various types of transactions, it cannot be identified by a third party and is therefore reflected as "To Confirm." Please select the correct transaction type manually. When the file is uploaded, a transaction type called "to confirm" is displayed
3. Important Notes about the API
USDT-M Futures"/ "USDC-M Futures"/ "Coin-M Futures:
- For futures trading funding fees, they occur every one to several hours for both file and API transactions. Each occurrence is reflected as either a "Bonus" or a "Loss" in the transaction history.
Savings:
- We confirmed that from May 30, 2024 (specific time unknown/Japan Standard Time), interest income from flexible savings is distributed as "FINANCIAL_BATCH_FUND_INVESTMENT_USER_IN" instead of "Financial." Therefore, we have decided to reflect "FINANCIAL_BATCH_FUND_INVESTMENT_USER_IN" distributed in the updated API on June 14, 2024, as "Bonus."
Copy trade:
Both API and file support "Copy Trade profit" and "Copy Trade expense" for spot trading.
If there are any other copy trade histories for spot trading that are not reflected, please contact support.
Additionally, as we are currently collecting samples for futures trade histories, they are not supported at this time.
4．Transactions Not Automatically Reflected via API or File
If you can identify the details of your transactions—such as by checking them on the exchange’s interface—please create a Custom File and enter the transactions yourself before uploading it.
Custom File for any other trades
How to upload a Custom File