If you use TradingView webhooks or custom webhooks to trade on Bitget, you must update your pair symbols to the new v2 format.
What Is Changing
Old Bitget API v1 used pair names like:
BTCUSDT_UMCBLETHUSDT_UMCBL
After the migration to v2, 3Commas will expect the new pair format in webhooks:
BTCUSDTETHUSDT
So:
Old format:
BTCUSDT_UMCBLNew format:
BTCUSDT
In addition, some symbols are renamed when moving from v1 to v2.
Old pair (v1) | New pair (v2) |
$DEGENUSDT | DEGENUSDT |
ACNNEWUSDT | ACNUSDT |
APPSTOCKUSDT | APPUSDT |
EDENNEWUSDT | EDENUSDT |
GMESTOCKUSDT | GMEUSDT |
KLAYUSDT | KAIAUSDT |
LABNEWUSDT | LABUSDT |
LUNA2USDT | LUNAUSDT |
MONNEWUSDT | MONUSDT |
MSTRRWAUSDT | MSTRUSDT |
NOMERC20USDT | NOMUSDT |
OPENNEWUSDT | OPENUSDT |
PUMPFUNUSDT | PUMPUSDT |
PUMPNEWUSDT | PUMPBTCUSDT |
REDNEWUSDT | REDUSDT |
SOONNEWUSDT | SOONUSDT |
SOPHNEWUSDT | SOPHUSDT |
THENAUSDT | THEUSDT |
TKOUSDT | TAIKOUSDT |
VELO1USDT | VELOUSDT |
ZKSYNCUSDT | ZKUSDT |
3Commas will support both the old and new pair formats in webhooks from 28 November 2025 until 31 December 2025. After that, legacy v1 pair handling will be removed and any webhook that still uses v1 style pair names will stop working.
FAQ
Do I need to reconnect my Bitget API keys?
No. The migration affects pair symbols in webhooks only, not your exchange connection.
Will my existing bots stop working?
Bots that do not rely on external webhooks will continue as usual. Only bots or Signal bots that receive Bitget pairs from webhooks must be updated.
What happens if I do nothing?
Once legacy v1 pair handling is removed, any webhook that still uses v1 style pairs will fail and trades will not be created.
When will this change take effect and how long will v1 pairs still work?
Support for Bitget API v2 pair format in webhooks is available on 28 November 2025 onwards. 3Commas will continue to accept v1 style pairs in webhooks until 31 December 2025. After that, any webhook that still uses v1 pair names will fail and trades will not be created.