Your First Webhook

BY THE END OF THIS PAGE, YOU'LL KNOW HOW TO:

Before you can send webhooks, you need to add an API key from your exchange (Binance, ByBit, OKX, or any supported exchange). Create one in your exchange's API management settings, then add it here:

The API Keys page shows the required IP whitelist for each exchange. Use Bybit Demo or a supported exchange Testnet with matching credentials. Signal Factory executes on the selected account; it is not a simulator.

This is the simplest webhook possible. It buys BTC using 50% of your balance:

BTCUSDT on MyApiKey
market long 50%

Never trade without protection. Add sl off 2% directly on the same line:

BTCUSDT on MyApiKey
market long 50% sl off 2%

This requests a stop loss 2% below the entry reference. Fill price, supported order types and protection placement depend on the exchange; inspect the execution result.

Same idea. Add tp off 5% to lock in profits:

BTCUSDT on MyApiKey
market long 50% sl off 2% tp off 5%

Now you have a complete trade: entry + stop loss + take profit, all in 2 lines.

Go to the Signal Factory, paste your webhook, and hit Execute. You'll see the result in real-time.

Inline vs separate lines

What you wrote above uses inline SL/TP (everything on the market line). You can also write them on separate lines:

BTCUSDT on MyApiKey
market long 50%
stoploss off 2%
takeprofit 50%p off 5%

When to use which?

BTCUSDT on MyApiKey
// For an existing long position; quantities are read at placement
if posLong continue
stoploss off e2%
// Two limit exits and one trigger exit, where supported
takeprofit-limit 50%p off e2%
takeprofit-limit 30%p rr2
takeprofit 20%p off e6%
smart-oco sell

OCO: cancel one when the other fills

With separate stoploss and takeprofit, both orders exist independently. If one fills, the other stays open.

Use sl-or-tp to make them cancel each other automatically (OCO = One Cancels Other):

BTCUSDT on MyApiKey
market long 50%
sl-or-tp short 100%p sl off 2% tp off 5%

short 100%p = sell 100% of position. Native linkage or the standard OCO monitor handles cleanup where supported. Cancellation is not an atomic or instantaneous guarantee.

Price offsets always need a prefix keyword. Here's what works and what doesn't:

Webhook structure

Every webhook follows the same format:

SYMBOL on ApiKeyLabel
command1 parameters
command2 parameters

Amount & offset cheat sheet

Keep learning