Verify in Console
Console is your first proof that the command worked. A sender saying “success” only proves the webhook was sent, not that the correct connection or exchange action happened.
Use this order every time Check connection, bot name, symbol, size, and final outcome in that sequence.
Quick checklist
Section titled “Quick checklist”| Check | What you want to see |
|---|---|
| Connection | the token resolved the saved connection you intended |
| Bot name | the payload bot name matched that connection |
| Symbol | the symbol was parsed and resolved correctly |
| Command | the command started with the fields you expected |
| Size | the resolved amount or position was not zero |
| Outcome | success, warning, or error with a concrete result |
The minimum good path
Section titled “The minimum good path”- request accepted
- correct connection
- correct bot name
- correct symbol
- command started
- final outcome recorded
When to stop and fix the setup
Section titled “When to stop and fix the setup”Stop and fix the setup before trying new commands if:
- the token belongs to the wrong saved connection
- the bot name in the payload does not match
- the symbol does not resolve as expected
- the size resolves to zero
- the exchange rejects the order
Good testing habit
Section titled “Good testing habit”- keep the first size small
- send one command at a time
- keep Console open while testing
- only move to sequences after the simple command is verified
After the first pass If the command worked, move to Common tasks. If it did not, move to Console and errors.