Documentation

These docs are organized around one rule: each page does one job. Start pages introduce the flow, task pages give you copy-ready patterns, reference pages define syntax, and troubleshooting pages diagnose failures.

Best path for new users Create one connection, send one simple command, verify the real result in Console, and only then move to more advanced patterns.

Most useful syntax and troubleshooting guides

TradingView webhook formatStart here for valid payload structure, wrappers, and first working examples.TradingView order syntaxUse this as the main command hub for market, limit, trailing, cancel, adjust, and wait.Webhook error codesUse this page first when a webhook arrives but validation or execution still fails.

Start here

Follow this path in order if you are new.

1. Create your first botCreate the saved connection, choose the bot name, and copy the webhook token.2. Send your first commandUse one minimal market command and validate the whole path end to end.3. Verify in ConsoleConfirm the correct connection, bot name, symbol, size, and final outcome.

Common tasks

When the first command works, move to task recipes instead of deep reference pages.

TradingView webhook examplesCopy-ready examples for entries, exits, target position, and multi-step flows.Open a longUse a direct market buy with a small fixed amount.Close full positionFlatten cleanly with position=0.Place a limit orderUse a passive entry with a simple offset.Cancel and replaceClear resting orders, wait briefly, then send the fresh setup.

Fastest practical page If you already have one working command, go straight to Common tasks.

Reference

Use reference pages only when you need exact terms or syntax.

Core conceptsConnection, token, bot name, symbol, amount, position, and sizing tokens.Payload grammar referenceThe exact wrapper, separators, and field forms used by the command language.Market commandImmediate entry, exit, reduction, or target-position behavior.Limit commandPassive orders using explicit prices or offsets.

Troubleshooting

When the result is wrong, diagnose in a fixed order instead of guessing.

1. ConnectionMake sure the token hit the saved connection you intended.

2. Bot nameVerify that the payload bot name matched that connection.

3. Symbol and sizeCheck that the symbol resolved and the final size was not zero.

4. Final outcomeCheck whether the provider accepted, warned, or rejected the instruction.

Do not trust the sender alone A sender returning success does not prove the command executed correctly. Use Console and errors to inspect the real execution path.