This page introduces the trade types that can be obtained via Bitget file and API.
| Trade type | File support | API support | API endpoint |
| Spot Trades | ✔ | ✔ | Bitget/Trades |
| USDT-M Futures | ✔ | ✔ | Bitget/Futures Record (UDDT-M) |
| USDC-M Futures | ✔ | ✔ | Bitget/Futures Record (USDC-M) |
| Coin-M Futures | ✔ | ✔ | Bitget/Futures Record (COIN-M) |
| Savings *1 | ✔ | ✔ | Bitget/Trades |
| Staking | ✔ | ✔ | Bitget/Trades |
| Convert Small Balance to BGB | ✔ | ✔ | Bitget/Trades |
| Others | × | × |
【Files】
- "Financial"・・・The history labeled as "Financial" in the file (distributed as "Financial" via API) has been confirmed to be used for multiple different transaction types on the Bitget side. Therefore, from the term "Financial," third parties cannot determine what kind of transaction the customer has conducted, and we handle it as "To confirm transactions" Consequently, customers need to select the correct transaction type on the screen themselves.
-
Numbers displayed as transaction type・・・Due to lack of sufficient details in the file, cryptact handle those transactions as "To confirm transactions" .
When the file is uploaded, a transaction type called "to confirm" is displayed -
"bonus_issue," "bonus_expired," "bonus_recycle"・・・Starting Thursday, September 12, 2024, "bonus_issue" will be treated as Bonus/BONUS and "bonus_expired" as Loss/LOSS. "bonus_recycle" will continue to be treated as Loss/LOSS.
Previously, "bonus_issue" was not reflected in the transaction list as it was considered a margin bonus that couldn’t be used until a loss occurred. Similarly, unused "bonus_expired" bonuses were not reflected. However, to avoid showing larger losses than actual, we’ve now updated how these transactions are processed.
【API】
- The history distributed as "Financial" via API has been confirmed to be used for multiple different transaction types on the Bitget side. Therefore, from the term "Financial," third parties cannot determine what kind of transaction the customer has conducted, and we handle it as "To confirm transactions" Consequently, customers need to select the correct transaction type on the screen themselves. Here is the method to handle transactions that require identification.
*1 In the API distribution, 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."
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. However, we have not collected enough sample files yet. If you have any files with the label "365," please send them to the support desk.