Platforms / Bitget
exchange
MiCA status unknown
Bitget
Bitget usually needs API and/or CSV; derivatives and earn products are common gap sources — export statements for those years.
1. Data access
Export / sync paths we track for tax-history reconstruction.
API key
- Bitget → API Management → create read-only key
- Connect in tax software as Bitget
spot some transfersderivatives earn copy-trading depending on product
CSV / statements
- Download spot + derivatives + earn history where available
- Import via software mappers or generic CSV
fills API gaps
Recommended together with API sync when available.
2. Known gaps
Where API or CSV usually fails.
| Activity | API | CSV | Notes |
|---|---|---|---|
| Spot | Yes | Yes | |
| Futures / copy trade | Partial | Often needed | |
| Earn | Partial | Often |
3. Tax software that can ingest Bitget
From the CryptoTax Digest integrations matrix.
| Software | Support | Sync | Notes |
|---|---|---|---|
| Awaken | api | automatic | Captured 2026-07-17 |
| Blockpit | api | automatic | Captured 2026-07-17 |
| Waltio | api | automatic | Bitget API + file — https://help.waltio.com/en/collections/15203367-bitget |
4. Regulatory snapshot (MiCA)
Linked legal entities when curated — never equate brand ≡ licence.
No curated MiCA entity join yet (unknown). That is not a non-compliant flag.
Caveats
- No safe MiCA entity join curated yet — status unknown (not ‘non-compliant’ by default)
- Waltio supports Bitget via API + file import — prefer both for derivatives/earn years
- Re-verify export paths each tax season
Educational — not tax, legal, or licence advice. Data-access grades are about reconstructable history, not solvency or security.