Native Exchange Webhooks and External Execution
Bybit restrictions
Bybit's native Webhook Signal Trading guide specifies one-way position mode and a separate webhook for each pair. Those restrictions describe that native product. They should not be generalized to every external connection using Bybit's API. [S13]
OKX message fields
OKX publishes its own Signal Bot specification, including instrument, action and timing fields. Its maxLag setting compares the timestamp supplied with the signal against reception time; the documented default is 60 seconds. This is a native bot rule, not a generic TradingView expiry mechanism. [S14]
AlgoWay routes
AlgoWay lists exchange connections alongside its broker and terminal routes. Choose the exact exchange connection and verify its supported product and position settings. A common place to manage routes does not make the destination exchanges' order rules identical. [S17]
Use a native webhook when the exchange product represents the signals and order behavior you need. An external execution route is useful when its documented capabilities solve a requirement outside that product. The comparison guide explains what to compare beyond the subscription headline.
Spot, Perpetuals and Inverse Contracts
| Product | First sizing question | First exit question |
|---|---|---|
| Spot | Is quantity base asset or quote-currency value? | Is enough of the asset available to sell? |
| Linear perpetual | Is quantity in coins, contracts or notional? | Will the instruction reduce the intended position? |
| Inverse contract | What is the denomination and multiplier? | Is the order addressed to the correct contract and side? |
| Crypto CFD in a terminal | What are the broker's lot specifications? | How does the account handle opposite trades? |
The last row belongs operationally to the MetaTrader guide. An instrument following Bitcoin's price is not necessarily a spot Bitcoin balance or an exchange perpetual position.
In a simple sizing example, a 100 USDT notional purchase at an assumed 50,000 USDT price corresponds to 0.002 BTC before fees and rounding. Sending 100 to a field interpreted as BTC is an entirely different instruction. Write the unit next to every configured quantity.
Position Modes and Order Quantities
One-way accounts represent net directional exposure. Hedge-mode workflows distinguish long and short positions, so a closing command must identify what it is reducing. A connector needs to express the destination's required side or position selection; a generic sell instruction does not explain that intent.
Minimum quantity, quantity increments and minimum order value are separate checks. A calculated partial exit can be mathematically correct but too small for the venue. Inspect the accepted size and remaining exposure in a test, especially after dividing a position among profit targets.
Strategy reversal sizing deserves another check. The reported order quantity can include closing the previous simulated position as well as opening the new one. An executor that interprets that value as new target exposure can oversize the reversal. See Pine alert semantics.
Stops, Partial Exits and Position Synchronization
Decide who owns protection: the exchange's native orders, the external service, or subsequent strategy alerts. A stop visible on the chart is not evidence of an accepted exchange order. Check its instrument, side, trigger price and covered quantity.
Consider a strategy that believes it is long while you have manually closed the exchange position. Its next sell may be an exit in the simulated strategy. At the account, rejection, no action or a new short are different possible outcomes, depending on the route's semantics. Establish the documented behavior and test it on a non-live route.
After a partial exit, inspect both remaining position and protective quantity. An old stop sized for the original exposure may need adjustment. A complete test follows the whole sequence rather than stopping at the first successful buy.
Signal Expiry and Rejected Orders
A late entry and a late close have different consequences. An expiry policy should specify which timestamp is used and what happens to the associated position. Do not paste an OKX native-schema field into another receiver and assume it enforces the same limit.
For a rejected order, keep the final substituted message and exchange error together. Compare product, symbol, position mode, quantity and available balance. A successful HTTP response proves neither exchange acceptance nor a fill. The execution guide separates these records.
Questions and Answers
Can an indicator use an exchange's native webhook bot?
Check the product's supported event and message format. Arbitrary indicator text is not automatically compatible with a bot designed around strategy events.
Why does hedge mode cause a rejection?
The route may require one-way mode or a side selector missing from the instruction. Bybit's cited native webhook product explicitly uses one-way mode. [S13]
What happens after I close the position manually?
The chart strategy may retain its simulated position. Compare it with the exchange account before resuming alerts, and establish how the receiver handles an exit with no matching exposure.
Is a native webhook the same as an API connector?
No. They are separate execution products with their own schemas, limitations and account requirements.
Sources & further reading
Official documentation supports the technical claims. Community discussions illustrate user questions, not verified product behavior. Rules and account terms can change.