Learning Center
Master Flipr.Cloud's webhook automation language
Welcome to Flipr.Cloud
Flipr.Cloud allows you to automate trading on cryptocurrency exchanges using simple webhook messages from TradingView or any other platform, even custom home-made bots.
Our syntax is designed to be intuitive and powerful, allowing you to execute complex trading commands on both Spot and Futures markets with just a few lines of code.
BTCUSDT on My_API_Key
// Saved API key label for a compatible futures market
// Buy using 50% of total balance, without leverage multiplication
market long 50%
// Request protection for the long position, relative to its entry
sl-or-tp short 100%p sl off e2% tp off e5%
// Inspect every result: entry and protection can fail independently!! RecommendedPlan and Verify Your Exit Orders
Plan and Verify Your Exit Orders
When you send a command like market long 0.05 and later rely on a separate signal to close the position (e.g. pos 0 or close all), your exit depends on a chain of external systems working perfectly: TradingView must fire the alert, the internet must deliver it, and the execution layer must process it — all in real time.
If any link in that chain experiences a delay or interruption — a TradingView outage, a network hiccup, a DNS issue, a cloud provider glitch — an intended exit may not arrive. With high leverage, even a brief gap can mean liquidation.
Where supported, request sl and tp with your entry command, then verify that the exchange accepted the protections:
market long 0.05 sl off 2% tp off 5%Protection handling depends on the exchange and market. An accepted native protection can remain active without another alert, but trigger and execution rules still apply. A successful entry does not prove that both protections were accepted; inspect every result and the exchange orders.
On Binance Futures, you can also add a native trailing stop to a market entry:
market long 0.05 sl off 2% tp off 3% ts 2%/1.5%Quick Tips
New here? Start with the Quick Start guide and check the selected environment
Use the Signal Factory to prepare messages. Executing uses the environment of the selected key
Check Execution History to see exactly how your commands were processed
For testing, we recommend using your exchange's testnet API credentials and enabling Testnet for that key in API Keys, if supported by the exchange and market.