What this page covers
Command syntax and examples for Telegram trading workflows with dry-runs and human confirmation.
Safe setup checklist
Keep credentials server-side, validate dry-runs first, confirm static IP and callback configuration, and avoid enabling live execution until readiness checks pass.
The user-facing state should distinguish dry-run readiness from live execution readiness. A missing setup item can still allow documentation and support review, but it should not quietly enable broker calls.
Implementation details
Command docs should define allowed commands, required fields, examples, dry-run behavior, confirmation behavior, and blocked states. The bot should reject ambiguous messages and unknown chats.
Vantaro handling
Vantaro treats setup issues as blockers for live execution while still allowing safe documentation and dry-run review where applicable.
Each blocker should create an audit event so support and users can review what happened without exposing tokens or sensitive account data.
Evidence and screenshots to add before final publication
FAQ
Can this page replace official broker docs?
No. Use it as a workflow guide and verify implementation details with official Dhan or Telegram documentation.