Support channel directory
| Channel | Use when | URL |
|---|---|---|
| Documentation first stop | You need limits, enums, lifecycle semantics, or recovery steps | docs.derivadex.com |
| AI tooling access | You need MCP or skill discovery endpoints for AI-assisted docs usage | Use DerivaDEX Docs with AI Tools |
| Community support | You need trading or integration help from the team/community | Discord |
| KYC support | You are blocked on Blockpass verification or status questions | Blockpass support |
Route before escalating
| If the question is… | Check this first |
|---|---|
| a docs mismatch or unclear statement | FAQ, Troubleshooting, then the exact page named in your report |
| an API integration or lifecycle interpretation issue | API Reference, Reference, and the relevant how-to guide |
| a trading-risk or liquidation question | Reference risk pages plus the relevant trading how-to guide |
| an AI-tooling or MCP-discovery question | Use DerivaDEX Docs with AI Tools |
| a Blockpass/KYC workflow problem | Blockpass support after confirming the docs route does not already answer it |
What to include in a support request
- Exact page URL and section heading where confusion occurred.
- Request and response identifiers for API issues.
- Symbol, strategy, and approximate timestamp for trading-state questions.
- Observed error class and safety-failure variant when applicable.
Request categories
| Category | Include |
|---|---|
| Documentation correction | page URL, expected statement, observed mismatch |
| API integration issue | endpoint/feed, payload shape, status/error class |
| Order lifecycle issue | request receipt, order identity, lifecycle events observed |
| Risk and liquidation question | symbol, margin context, mark-price movement, event timeline |
Before escalating
- Check FAQ.
- Run Troubleshooting.
- Confirm terminology in Glossary.