If you configure an exchange that is not officially supported, MagicTradeBot will stop execution during startup and display a clear error message indicating that the selected exchange is not supported.
What exactly happens?
- During initialization, MagicTradeBot validates the configured exchange name
If the exchange is not found in the supported exchange registry, the bot:
- Immediately exits
- Prints a clear message such as: “Selected exchange is not yet supported.”
- No trading logic, market data processing, or order execution is started
This behavior is intentional and designed to prevent:
- Unexpected behavior
- Invalid API calls
- Misconfigured order execution
- Potential trading risks
Why does MagicTradeBot exit instead of continuing?
MagicTradeBot follows a fail-fast design principle:
- It refuses to run on unknown or partially compatible exchanges
- It avoids making assumptions about unsupported APIs
- It ensures your capital is never exposed to untested or unsafe exchange integrations
This guarantees stability and protects users from silent misconfiguration errors.
What should I do if my exchange is not supported?
If your preferred exchange is not listed:
- Double-check the exchange name in
application.yamlfor typos or casing issues - Confirm the exchange is not already supported under a different identifier
- Contact the MagicTradeBot team to request support for the exchange
To be eligible for integration, the exchange must:
- Support futures trading via API
- Provide stable order, position, and leverage endpoints
- Offer sufficient market and symbol metadata
Thanks to MagicTradeBot’s modular exchange layer, adding new exchanges is typically straightforward once requirements are met.
Key takeaway
- ❌ Unsupported exchange → bot will not start
- ✅ Supported exchange → bot runs safely and predictably
- 🛡️ Early exit ensures reliability and risk protection